Track Lead Source in Close CRM: A Practical Setup and Reporting Guide
Knowing which campaigns create enquiries is only useful when that information travels with the contact into Close CRM. This guide explains how website attribution data can be captured on forms, passed to Close CRM, and then used to compare channels, campaigns, landing pages, opportunities and customers.
Why source data belongs on the CRM record
A lead record that only contains a name and email cannot answer a basic marketing question: which activity created this enquiry? When source information is stored alongside the contact, teams can compare enquiry volume by channel, follow opportunities back to the campaign that created them, and see which pages or networks produce customers rather than only clicks.
The workflow has four parts. First, add attribution code to the website. Second, add hidden fields to the forms visitors complete. Third, let the attribution tool classify the visit and place the resulting values into those fields when the form is submitted. Fourth, use the values inside Close CRM, either with native reporting or by sending the data to a reporting platform.
Before starting, check that the form tool can send hidden-field values to Close CRM together with the visible fields. That connection is what carries the attribution data into the CRM record.
Setup: website code and hidden form fields
Create an account with the attribution tool and follow the setup instructions to place its code on the website. The exact method depends on the site platform. Some builders provide a settings area for custom code, while other sites use a tag manager to load it.
Next, add these hidden fields to each relevant form:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Channel Drilldown 4
The field names should match the names expected by the attribution tool and the form integration. Hidden fields are not filled in by the visitor; they receive values automatically when the form is submitted.
Use the setup checklist below to avoid a common failure: the form works, but no source data arrives in Close CRM.
- Website code is present on the pages containing the forms
- Every form has all five hidden fields
- Hidden-field names match the attribution tool's expected names
- A test submission creates a Close CRM lead
- The test lead contains channel and drilldown values, not blanks
- The same check passes for each form builder in use
How the data moves from visit to form to Close CRM
When someone arrives, the tool classifies the visit using channel categories comparable to those used in web analytics, such as Organic Search, Paid Search and Paid Social. It stores the classification in a browser cookie, so the information can persist while the person browses and can still be available if they return after leaving the site.
When the visitor submits a form, the tool writes the stored classification into the hidden fields. The form tool then sends those values to Close CRM with the other details entered by the visitor, such as name, email, phone and company.
This distinction matters: the cookie preserves the attribution while the person is browsing, but the hidden fields are what make the attribution part of the submitted form data and therefore part of the CRM record.
What data to capture on each lead
Each new lead can carry two main groups of attribution data: channel information and landing-page information.
Channel data identifies the broad channel and then adds progressively more specific detail through the drilldown fields. For a paid-search visit, an example pattern is Channel: Paid Search; Channel Drilldown 1: Google; Channel Drilldown 2: the campaign name; Channel Drilldown 3: the keyword or ad term. For an organic-search visit, the pattern might be Channel: Organic Search; Channel Drilldown 1: Google; Channel Drilldown 2: the Google domain; Channel Drilldown 3: the search term when available.
Landing-page data records the first page the visitor reached and the group that page belongs to. For example, a specific blog article can be recorded alongside its /blog group. That makes it possible to compare enquiry volume across site sections and then inspect individual pages within a section.
Keep the drilldown meanings consistent. If Drilldown 2 means campaign for paid traffic but domain for organic traffic, reports must account for that difference rather than treating every value in the field as the same kind of thing.
Three reports to build first
Once the fields are populated, start with three reports that answer different management questions.
Leads by channel shows monthly enquiry volume split across categories such as Paid Search, Paid Social and Organic Search. Use it for a high-level view of where demand is coming from and where further investment may be justified.
Opportunities by Google Ads campaign groups new opportunities by campaign. Pair opportunity volume with the lead-to-opportunity conversion rate for each campaign. A campaign can look strong on volume but weak on conversion, or the reverse, so both numbers are needed before judging performance.
Customers by Facebook Ads network groups new customers by the network that delivered them, such as Facebook, Instagram, Messenger or WhatsApp. This view helps identify which network is producing customers and where advertising effort should be concentrated.
Close CRM's reporting can be used directly, or the data can be synced to a tool such as Google Data Studio or Microsoft Power BI for more advanced analysis. Whichever route is chosen, test the report against a known lead so the channel, campaign and landing-page values are being read from the correct fields.
Troubleshooting and next step
Source tracking in Close CRM works when three pieces line up: the website code runs, the hidden fields are present on the form, and the form integration sends those fields to Close CRM. Test each piece with a real submission before relying on the reports.
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
If the test lead arrives with blank attribution fields, check the field names and the form-to-CRM mapping first. If the fields are populated but the values look wrong, check the channel definitions and drilldown meanings. If only some forms are affected, compare their hidden fields and integration settings rather than changing the website code.