CRM lead source
CRM lead source, filled in for every lead
The real source, landing page and full journey, on every lead. Fill your CRM’s lead source field with the marketing that brought the customer, and fund more of it.
Free to start · no card
What “lead source” means in a CRM.
A CRM lead source is the field on a lead or contact record that names the channel, campaign or page that first brought that person in.
It is how you tell which marketing produced which customer. 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 doing the same job.
The argument is never about the field. It is about what goes into it. For the full definition and the categories, see what a lead source is, or the guide to tracking lead sources.
Fill your CRM’s lead source field automatically as each lead arrives.
Your CRM fills its lead source field one of two ways. A person types it in, or something writes it automatically as the lead arrives.
-
What the native field usually holds
- One picklist value: Web, Referral, Direct, Other.
- Typed by a rep, or defaulted by the form.
- Set once, then left to drift as the record ages.
-
What a record written at capture adds
- The source behind the click, in plain language.
- The landing page they arrived on.
- Every page read before submitting, ending on the page where they filled in the form.
- A record that stays put when a lead becomes a contact or a field is edited.
Nobody remembers the ad they clicked six days ago, and the rep was not there when it happened. A field that is written at capture depends on one thing: whether the tracking works. That part is fixable.
Keeping the values clean afterwards is its own discipline: agree the values, enforce the picklist, audit what drifts. That is lead source management.
Source, landing page, and the page where they enquired.
A useful lead source record is three facts. Lead Source catches all three on every form submission, so the CRM field stops being a guess.
- Source. The channel written out, like “Google, Freight Software Demo”, in place of a raw UTM parameter or a bare “Web”.
- Landing page. The first page they saw on your site. Two leads can share a source and arrive on different pages.
- The journey to the form. Every page read before submitting, ending on the one that did the persuading.
That is how RedZone cut marketing spend by 63%. Once you can see the real source, the next move is to respond before the lead goes cold.
Record the source on your website, and every CRM receives it.
A CRM receives whatever the form sends it. If the form sends a name and an email, that is what the record holds.
No CRM was there when the visitor arrived, so none of them can say where a lead came from. The fix is on your website. Catch the source when they arrive, hold it across the visit with lead source tracking, and the source lands on the CRM record with everything else.
The tracking sits on the page, outside the form itself, so the fix is the same on every form tool. Form tracking has the setup per platform.
How lead source tracking works with your CRM.
One line of JavaScript in your site head captures the source, landing page and full journey on every form submission, and stores each lead in your own dashboard.
-
CRMs with their own setup guide
-
Every other CRM
- Zoho, monday CRM and Freshsales
- Copper, Dynamics 365 and Insightly
- Every lead is captured and stored in your Lead Source dashboard, whatever the CRM.
From the dashboard, each lead leaves through the Zapier app, a signed webhook or a CSV export, and the source lands on the CRM record beside the lead source field you already have.
Native CRM lead source field vs Lead Source.
What each CRM’s own field records, and what Lead Source adds. The native field keeps doing its job; the detail it was never built to hold arrives beside it.
| 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 source, landing page and full page journey |
| 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. Each holds a channel, where you needed the source, the landing page and the journey. Compare every CRM side by side on the compatibility matrix, see worked records in lead source examples, and the wider picture in lead attribution software.
CRM lead source, questions answered.
What is a lead source in a CRM?
The channel, touchpoint or referring page that first brought a prospect to you. In a CRM it is the field on a lead or contact record that says where that person came from. Salesforce calls it the Lead Source picklist. HubSpot calls it Original Source. Most others have a named or custom field doing the same job.
Why does my CRM say the lead source is "Web" or "Direct"?
Because the native field holds one broad channel value, fed by a form default or a rep’s best guess. "Web" means a form on your site fired. It does not say which source, which ad, or which page produced the lead. The specific source, the landing page and the converting page are not captured by the native field, so the bucket stays generic.
Can I track the landing page and the page where they filled in the form, 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 where they decided to enquire. The channel tells you where to spend. That page tells you which content to build more of.
Does Lead Source replace my CRM's lead source field?
No. It runs alongside your CRM’s own field. Each lead is stored in your Lead Source dashboard as the primary record, and it reaches your CRM through the Zapier app or a signed webhook, with the source landing on the record beside the field you already have.
Which CRMs does lead source tracking work with?
All of them. Lead Source captures the data on your website, independently of your CRM. Salesforce, HubSpot, Pipedrive, Keap and Close have their own setup guides. For any other CRM, every lead leaves your dashboard through the Zapier app, a signed webhook or a CSV export.
Lead source, in depth
See the real source on every lead. Free to start.
Start free and each new form submission lands in your dashboard with its source, landing page and journey, ready for your CRM.
Free to start · no card









