Salesforce Lead Source best practices.
The Salesforce Lead Source field is a standard picklist on the Lead and Contact objects. Kept tidy, it is a reliable channel view. Left to free choice and manual entry, it drifts into noise within a quarter. These are the practices that keep it useful, and the one that captures the detail it was never built to hold. For the integration itself, see lead source in Salesforce.
Five that keep the field worth reporting on.
Keep the picklist short and standard
Lead Source is a picklist for a reason. Define a tight set of channel values and stop there. Every extra value a rep can pick, and every free-text variant, is a future report that does not add up. Fewer, cleaner values beat a long list nobody agrees on.
Set it at creation, not by hand later
Populate Lead Source when the record is created, from Web-to-Lead, your form, or an automation, rather than relying on a rep to remember. A field filled at the source is accurate; a field filled from memory three days later is a guess.
Use a custom field for the detail
Do not overload the standard picklist with campaign detail. Keep Lead Source for the channel, and add a custom field for the specific source: the campaign, the landing page, the journey. One field for the bucket, one for the answer.
Map it cleanly through lead conversion
When a Lead converts to a Contact and Opportunity, make sure both the standard Lead Source and your custom source field map across. A source that vanishes at conversion is a source you cannot tie to revenue.
Report on the source, not recent activity
Build your source reports on the captured Lead Source and custom source fields, not on the most recent activity or campaign touch. Decide which question you are answering, first touch or last, and report it consistently.
Tidy still is not detailed.
Even a perfectly maintained Lead Source picklist holds one channel value. “Web” kept clean is still just “Web.” The campaign, the landing page, and the journey are not picklist material, which is exactly why the custom field in practice three matters.
The channel, kept clean
- A reliable, agreed channel value
- Easy to group and report on
The detail that moves budget
- The specific campaign behind the click
- The landing page and the journey to the form
Fill the custom field automatically.
Practice three needs a custom field, and something to populate it. Lead Source captures the real source, campaign, landing page and full page journey on every Web-to-Lead submission and writes it to a custom field, alongside the standard picklist. No Apex, no rep entry. The standard field stays clean; the custom field carries the detail.
See the Salesforce setup in lead source in Salesforce, or compare CRMs on the compatibility matrix. The same field-hygiene problem hits Microsoft-stack teams on Dynamics.
Questions, answered.
Should I use the standard Lead Source field or a custom field?
Use both, for different jobs. Keep the standard Lead Source picklist for the channel, with a short, agreed set of values. Add a custom field for the specific source: the campaign, landing page, and journey. Overloading one field with both makes reporting harder, not easier.
How do I stop the Salesforce Lead Source field drifting?
Set it at creation rather than by hand, keep the picklist short and standard, and map it cleanly through lead conversion so it survives onto the Contact and Opportunity. Most drift comes from manual entry and an over-long value list, not from Salesforce itself.
Can I capture the campaign and landing page without Apex?
Yes. Lead Source captures the real source, campaign, landing page, and full page journey on every Web-to-Lead submission and writes it to a custom field, alongside the standard picklist. No Apex and no rep entry, so the standard field stays clean while the custom field carries the detail.
Keep the field clean. Capture the detail.
One line of code fills a custom field with the real source, alongside the standard picklist.
Track your Salesforce leads free →Free to start · no card