CRM lead source
How to add a custom field to a Freshsales web form
CRM lead source
CRM lead source: track the marketing that brings customers.
The real source, landing page, and full journey, on every lead.
Your CRM’s lead source field says “Web”, or whatever a rep typed last. Here is how to fill it with the real source, the landing page and the page that converted them.
The cause
Why the field is empty
Your CRM fills that field at one of two moments. A person types it in, or something writes it automatically the instant the lead arrives.
If it depends on a person, it depends on them knowing something they cannot know. Nobody remembers the ad they clicked six days ago. The rep was not in the room when it happened. So it gets left blank, or guessed at, or set to Other, and a year later the report built on it is worthless.
If it is written at capture, it depends on one thing. Whether the tracking works, fixable.
Keeping it clean afterwards is a separate discipline, and a duller one. Agree the values, enforce the picklist, audit what drifts. That is lead source management.
The definition
What "lead source" means in a CRM.
A CRM lead source is the field on a lead or contact record that says where that person came from. It names the channel, campaign or referring page that first brought them in, so you can 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, and what gets left out. For the full definition and categories, see what a lead source is, or our guide to tracking lead sources.
The gap
Why the native CRM lead source field falls short.
The field is rarely wrong on purpose. It is fed the wrong inputs. A rep guessing on a call, a form default, or a channel bucket so broad it answers nothing. Three failures turn up in every CRM.
What the native field usually holds
A channel, at best
- 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 it leaves out
The part that tells you what worked
- The source behind the click, in plain language.
- The landing page they arrived on.
- Every page they read before submitting, ending on the one that converted them.
- A record that survives lead-to-contact conversion and field edits.
The three data points
Source, landing page, and the page that converted them.
A useful lead source record is three facts, not one. Most tools catch the first. Lead Source catches all three on every form submission.
Catch all three and the CRM field stops being a guess. That is how RedZone cut marketing spend by 63%, and once you can see the real source, the next move is to respond before the lead goes cold.
- Source. The channel written out, like “Google, Freight Software Demo”. Not a raw UTM parameter, and not a bare “Web”.
- Landing page. Where the channel handed off to your site. Two leads can share a source and arrive on completely different pages.
- Journey to the converting page. Every page read before submitting, ending on the one that did the persuading.
Which form tool are you on?
The fix is the same on all of them, because the tracking sits on the page rather than inside the form. Form tracking has the setup per platform.
Setup
How lead source tracking works with your CRM.
Lead Source is one line of JavaScript in your site’s <head>. On every form submission it captures the source, the landing page and the full page journey, then 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.
Direct setup guides
CRMs we support directly
Works alongside any CRM
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
Comparison
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 source, 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 needed the source, the landing page and the page that converted them. Compare every CRM side by side on the compatibility matrix, see worked examples in lead source examples, and the wider picture in lead attribution software.
Where the fix lives
This is a form problem, not a CRM problem
No CRM can tell you where a lead came from. It was not there when it happened. It receives whatever the form sends it, and if the form sends a name and an email, that is what the record holds.
The fix is on the form. 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.
Common questions
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 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 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. It 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 the CRM, we write it to a custom field, never to the standard lead source picklist unless you explicitly turn that on.
Which CRMs does lead source tracking work with?
Lead Source captures the data independently of your CRM, so it works alongside any of them. There are direct setup guides for Salesforce, HubSpot, Pipedrive, Keap and Close. For other CRMs the record lives in your Lead Source dashboard, and you can export it to CSV or post it 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