CRM lead source: track where your leads actually come from.
Your CRM has a lead source field. It usually says "Web", or whatever a rep typed last. Here is how to fill it with the real source, the landing page, and the full page journey behind every lead.
What "lead source" means in a CRM.
A lead source is the marketing channel, campaign, or referrer that brought a prospect to your business. In a CRM, it is the field on a lead or contact record that is supposed to answer one question: where did this person come from? Every major CRM has one. Salesforce calls it the Lead Source picklist; HubSpot calls it Original Source; the rest have a named or custom field that does the same job. For the full definition and categories, see what a lead source is.
The field exists in every CRM. The problem is what goes into it, and what gets left out.
Why the native CRM lead source field falls short.
The field is rarely wrong on purpose. It is just fed by the wrong inputs: a rep guessing on a call, a form default, or a channel bucket so broad it answers nothing. Three failures show up in every CRM.
A channel, at best
- A single picklist value: Web, Referral, Direct, Other
- Often typed by a rep, or defaulted by the form
- Set once, then left to drift as the record ages
The part that tells you what worked
- The campaign and ad behind the click, written in plain language
- The landing page they entered on
- The pages they read before submitting, ending on the page that converted them
- A record that survives lead-to-contact conversion and field edits
Source, landing page, and the page that converted them.
A useful lead source record is three facts, not one. Most tools capture the first. The page journey, ending on the page that produced the submission, is the part that tells you which content actually converts. Lead Source captures all three on every form submission.
- 01Source. The channel and the campaign behind the click, written out in plain language ("Google, Freight Software Demo") rather than left as a raw UTM string or a bare "Web". This is the lead source proper.
- 02Landing page. The page the visitor first arrived on. Two leads can share a source and a campaign and land on completely different pages. The landing page is where the channel handed off to your site.
- 03Page journey, ending on the converting page. Every page the visitor read before submitting, in order, ending on the page where they converted. That last page is the one that did the persuading. Source tells you which channel to fund; the converting page tells you which content to build more of.
Capture all three and the CRM lead source field stops being a guess and starts being a report you can move budget on. That is how RedZone cut their marketing spend by 63%. And once you know the source, the next move is to respond before the lead goes cold.
How lead source tracking works with your CRM.
Lead Source is one line of JavaScript in your site's <head>. It captures the source, landing page, and full page journey for every form submission and stores each lead in your own Lead Source dashboard, independent of your CRM. From there the record can be pushed to a custom field in the CRMs we support directly. It runs alongside your CRM's own lead source field and never overwrites it. Pick your CRM for the exact steps.
CRMs we support directly
Other CRMs
- Zoho, monday CRM, and Freshsales
- Copper, Dynamics 365, and Insightly
- Every lead is captured and stored in your Lead Source dashboard regardless of CRM
- Export to CSV, or post to a custom field via an outbound webhook
Native CRM lead source field vs Lead Source.
What each CRM's own field records, and what Lead Source adds on top. The native field keeps doing its job; Lead Source captures the detail it was never built to hold.
| CRM | Native field records | Lead Source adds |
|---|---|---|
| Salesforce | Lead Source picklist value (often "Web") | Real source, campaign, landing page, full page journey |
| HubSpot | Original Source channel bucket | The campaign, landing page, and the page that converted them |
| Pipedrive | Source channel label on the lead | Source, landing page, and journey on every submission |
| Zoho | Lead Source picklist | Source, landing page, and full page journey, held independently |
| Keap | Lead Source field | Source, landing page, and journey on every form |
| Close | Lead source custom field | Source, landing page, and journey, captured at submission |
| Dynamics 365 | Lead Source option set | Source, landing page, and page journey, stored independently |
Different field name, same shortfall: a channel where you need the source, the landing page, and the page that converted. Compare every CRM side by side on the compatibility matrix, see worked examples in lead source examples, and the wider picture in lead attribution.
Questions, answered.
What is a lead source in a CRM?
A lead source is the marketing channel, campaign, or referrer that brought a prospect to your business. In a CRM it is the field on a lead or contact record that records where that person came from. Salesforce calls it the Lead Source picklist, HubSpot calls it Original Source, and most other CRMs have a named or custom field that does the same job.
Why does my CRM say the lead source is "Web" or "Direct"?
Because the native field usually holds a single broad channel value, fed by a form default or a rep's best guess. "Web" means a form on your site fired, not which campaign, ad, or page produced the lead. The specific source, the landing page, and the page that converted the visitor are not captured by the native field, so the bucket stays generic.
Can I track the landing page and the page that converted them, not just the channel?
Yes. Lead Source captures three things on every form submission: the source and campaign, the landing page the visitor arrived on, and the full page journey ending on the page they submitted from. That last page is the one that converted them. The channel alone tells you where to spend; the converting page tells you which content to build more of.
Does Lead Source replace my CRM's lead source field?
No. Lead Source runs alongside your CRM's own field and never overwrites it. Each lead is stored in your Lead Source dashboard as the primary record. If you want the detail inside your CRM, we write it to a custom field, never to the standard lead source picklist unless you explicitly enable that.
Which CRMs does lead source tracking work with?
Lead Source captures the data independently of your CRM, so it works alongside any of them. We have direct setup guides for Salesforce, HubSpot, Pipedrive, Keap, and Close. For other CRMs the record lives in your Lead Source dashboard and can be exported to CSV or posted to a custom field via an outbound webhook.
See the real source on every lead. Free to start.
One line of code captures the source, landing page, and full page journey for every form submission, and stores each lead in your own dashboard. It runs alongside your CRM and never overwrites your lead source field.
Start freeFree to start ยท no card