Get marketing channel attribution data into Close
Close shows what happened after a lead arrived.
Attribution data shows how that lead found you. This integration connects the two by carrying channel, campaign and landing-page information from a website form into each lead and opportunity record in Close.
Why attribution belongs on the lead record
Close records the sales activity that follows a form submission, but it does not by itself explain which marketing source produced the enquiry. Passing attribution fields through the form closes that gap: when a visitor submits a form, the channel, campaign name, ad name and related detail travel with the lead into Close, so the same record can be used for both sales follow-up and marketing reporting.
How the flow works
The setup has three stages. First, hidden fields are added to the lead form. Second, the attribution tool detects the marketing channel the visitor came from and fills those fields. Third, when the form is submitted, the completed values are passed into Close alongside the lead's contact details. Because the data is captured at submission time, it stays attached to the correct lead and opportunity rather than being reconstructed later from separate reports.
What information you get
Channel data identifies the source category, such as Paid Search, Paid Social or Organic Search, and adds channel-specific detail where available. For paid search, that can include the campaign, ad group and keyword. Landing-page data records the first page the lead saw and the category of that page, such as a blog post. Together, these fields let you compare not only which channel produced a lead, but which campaign, ad and entry page contributed to it.
Turning captured data into reporting
Once the fields are present in Close, build reports that break leads, customers and revenue down by channel, campaign, ad and landing page. That makes it possible to see which marketing activity is producing pipeline and closed business, and to shift effort toward the sources that are working.
Compatibility checklist
Compatibility depends on one requirement: the form must support hidden fields. If you use a third-party form tool to capture leads and send them to Close, the tool needs to allow hidden fields to be added. If your forms are custom-built, a developer can add the hidden fields directly. If a form cannot accept hidden fields, this workflow cannot populate them.
Get started
Before you begin, verify that your form tool or custom form accepts hidden fields, that those fields can be mapped into Close, and that you have decided which attribution fields you want to report on. Check the current trial and pricing terms directly with the provider before signing up.
| Form type | Requirement | Result |
|---|---|---|
| Third-party form tool | Hidden fields can be added to the form | Attribution data can be populated and passed into Close |
| Custom form | A developer adds hidden fields to the form | Attribution data can be populated automatically |
Compatibility depends entirely on hidden-field support, as described in the source units.
Frequently asked questions
Does this work with any form builder?
No. The workflow described here depends on hidden fields being present on the form. A third-party form tool works when those fields can be added; a custom form works when a developer can add them.
What detail is captured for paid search?
Channel information is captured automatically, including the broader channel and, where applicable, campaign, ad group and keyword detail. Landing-page information includes the first page seen and its page category.
How is the data used after it reaches Close?
Use the captured channel, campaign, ad and landing-page fields to build reports showing which sources are associated with leads, customers and revenue in Close.