Skip to content

Add marketing attribution inside your software product

Software teams that serve marketers are often asked where leads and bookings came from.

Adding that insight natively can shorten time to market, while the external service handles ongoing testing and updates rather than your roadmap.

What this partnership is for

A CRM, form builder, scheduling tool, or similar product can offer attribution without building channel detection from scratch. The partner model is aimed at faster release: your product surfaces the result, while the specialist service maintains the underlying capture logic.

Use this page to decide whether the fit is right, which capture method suits your forms, and which commercial packaging matches how your customers should experience the feature.

How the flow works

  1. Place the website code. Your customer adds the snippet directly, or your product includes it in scripts already placed on their site.
  2. Capture at submission. Either write values into hidden form fields, or read them from the cookie when the form is submitted.
  3. Show the result where work happens. Put the captured values on the contact or booking record, expose them in reports, or include them in email notifications.

Decision check: if your forms already support hidden fields, that route needs the least custom code. If they do not, plan a small cookie-reading step at submission and test it against every form template you ship.

Two capture methods, one outcome

Hidden fields: add fields to the customer's forms and let the service populate them.

Pull from cookie: add code to the form so submission reads the stored attribution data.

Both approaches end in the same place — a stored value your product can display, report on, or send in notifications. The difference is where the handoff happens: in the field itself, or in code at the moment of submission.

What the provider handles

No development in many cases: the service can work with your product without engineering work from your team.

No testing burden: the provider describes 1,500 manual and automated tests each week to check data accuracy, so that routine sits outside your team.

No maintenance burden: the provider updates its code as browsers, devices, and operating systems change.

Treat those as the provider's stated operating model, not as a guarantee about your release schedule. Confirm scope, support, and service terms directly before committing.

Three integration options

Standalone: customers hold separate accounts in both products and follow setup instructions to connect them.

Integrated: customers still hold separate accounts, but the two products work together automatically with no setup required.

White-label: you embed the capability into your product and customers do not know the underlying provider exists.

Choose standalone when you want the lightest commercial step, integrated when you want the connection to feel automatic, and white-label when attribution should appear as a native part of your own product.

Checklist before you commit

Before you start, confirm these points with the provider:

  • Which capture method — hidden fields or cookie pull — fits each form type you support
  • Where captured data will appear: record, report, notification, or all three
  • Which packaging — standalone, integrated, or white-label — matches your customer experience
  • How accounts, billing, and support are split between the two products
  • What testing and update responsibilities remain yours

Enquiry form fields include first name, last name, work email, company name, phone, and how many customers you have. Hidden attribution fields on that form include Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page URL, Landing Page Group, Lead Source, Lead Sub Source, Lead Sub Source Description, and Testing Data. The form is governed by protected module form-controls-contract.

To discuss fit, contact the owner at {{OWNER_CONTACT_DESTINATION}}.