How to track lead source in your CRM
When a new enquiry arrives without context, it is hard to tell whether SEO, paid search, paid social, or another channel produced it. A practical setup captures that context at form submission, stores it beside the contact record, and makes channel-level reporting possible later.
A four-step setup checklist
Use this checklist before going live: install the site code through the website builder's settings or a tag manager; add Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group as hidden fields on every lead-capture form; submit a test form and confirm all six values arrive in the CRM; and check that the values are readable and reportable rather than stored only as free text.
How the data flows from visit to CRM record
Once installed, the tool categorises each visitor by channel, such as Organic Search, Paid Search, or Paid Social. When the visitor completes a form, those values are written into the hidden fields. The form tool then sends them with the contact details to the CRM. A CRM's own form tool can pass them directly; a third-party form builder may need its native integration or an automation tool such as Zapier.
What the six fields mean
Channel captures the broad source. The drilldown fields add detail in sequence: for Paid Search, the example values are Google, Brand Campaign, and Olmo. For Organic Search, the example values are Google, the Google domain, and the keyword where available. Landing Page records the first page seen, while Landing Page Group records its category, such as Blog. That structure supports both channel totals and page-level analysis.
Three reports worth building first
Start with leads by channel each month to see the overall mix. Then break opportunities down by Google Ads campaign to separate campaigns that create deals from those that only create enquiries. Finally, break customers down by Facebook ad network to compare Facebook, Instagram, Messenger, and WhatsApp. The same stored fields can answer revenue questions when the CRM links outcomes to the original lead record.
Failure points to check after setup
A common failure is installing the site code but forgetting the hidden fields, so the CRM receives the contact without attribution. Another is adding the fields to only one form while other forms remain unmeasured. A third is treating a channel total as proof of campaign quality; use drilldowns and downstream outcomes such as opportunities, customers, and revenue to judge performance.
| Hidden field | What it records | Useful report |
|---|---|---|
| Channel | Broad source category | Leads by channel |
| Channel Drilldown 1 | First level of source detail | Leads by platform or network |
| Channel Drilldown 2 | Second level of source detail | Leads by campaign or referrer |
| Channel Drilldown 3 | Third level of source detail | Leads by keyword or campaign detail |
| Landing Page | First page viewed | Leads by individual page |
| Landing Page Group | Category of the first page | Leads by content section |
Example values are illustrative; exact drilldown values depend on UTM parameters and channel rules.
Frequently asked questions
What is the shortest setup sequence for tracking lead source in a CRM?
Install the tracking code on the website, add the six hidden fields to each lead-capture form, let the tool populate those fields when a visitor submits, and confirm that the form tool passes them into the CRM. Then build reports from the stored channel, drilldown, and landing-page values.
What does each hidden field contribute?
Channel gives the broad category, the three drilldown fields add progressively more specific detail, and the landing-page fields identify where the visitor first arrived and what type of page it was. Together they let you move from a channel total to a campaign, network, or individual page.
Can the stored lead-source data be used outside the CRM?
Yes. The captured values can be reported in the CRM's native builder or exported to a tool such as Google Data Studio, Microsoft Power BI, or Tableau, depending on the CRM and reporting setup.