Lead source in Salesforce.
Stop guessing in the Lead Source field. Capture the real source on every form on your site.
Works across Salesforce’s form ecosystem
Salesforce trusts you to populate Lead Source.
The Lead Source field is a picklist. The Web-to-Lead form generator produces HTML that maps form fields to Lead object properties. None of it captures source data automatically. Salesforce assumes you’ll wire that up. Most orgs don’t. The ones that do, do it differently every time. There is a tidier way to keep the Lead Source field clean. Salesforce sits alongside the rest of the lead source integrations.
The framework
- Standard Lead Source picklist
- Web-to-Lead form generator
- Custom fields for anything you need
- Lead conversion → Opportunity flow
- Reports on Lead Source breakdown
The data itself
- Which source actually drove the click
- Persisting UTMs across visitor navigation
- Normalising values across team data entry
- Pages they read before submitting
- Surviving Lead → Contact → Opportunity intact
Custom fields, Apex triggers, Flow rules. Pick three.
Salesforce has every hook you need to capture source, and gives you the whole job. Create the fields. Modify the Web-to-Lead HTML. Build the triggers. Carry the data through conversion. Maintain it as your org grows.
The manual way
- 01Create custom fields for every campaign value on the Lead object, then again on Contact, then again on Opportunity.
- 02Edit every Web-to-Lead form to carry those values. Do it again every time the form changes.
- 03Build automation to fill them in before each submission, then test it across Lightning, Classic, Experience Cloud and embedded forms.
- 04Make sure the values survive Lead conversion, which Salesforce does not do for you, and check again every release.
With Lead Source
- Script tag on the site where your Web-to-Lead forms are embedded. Captures source independently of Salesforce.
- Pardot landing pages and Experience Cloud forms are hosted outside your site, so a script cannot reach them. Point their completion action at Lead Source instead, and each submission arrives with its source attached when it can be tied to a visit.
- Source recorded with the campaign name written out: “Google Ads · Local Services Sydney”. Available in your Lead Source dashboard alongside Salesforce’s native data.
- From there, the source lands on the Salesforce Lead your team already works from.
// Salesforce gives you the framework. The data is your job. We can be that job.
Two install paths. Pick the one that matches your forms.
Sign up and your dashboard has both install paths: one line for forms on your own site, and a link for Salesforce-hosted forms such as MCAE/Pardot landing pages and Experience Cloud.
<!-- Paste your real snippet from app.leadsource.co --> <script async src="https://app.leadsource.co/ft.js" data-site="YOUR_SITE_KEY"></script>
One line in your site header. It captures every form on the page, including a Web-to-Lead form, without touching the form or what it sends to Salesforce.
For Pardot and Experience Cloud forms, add your Lead Source link as a completion action, and every submission arrives with its source attached when it can be tied to a visit.
Salesforce sorted in three steps.
Sign up. Both install paths are waiting
Create your free Lead Source account. Your dashboard has both: a script tag for sites you control, and a link for forms hosted elsewhere.
Install the path that matches your forms
For forms hosted outside your site, configure a completion action or external system callout pointing at your Lead Source link.
Submit a test through any Salesforce form
Fill in a real Web-to-Lead or Pardot form. Submit. Moments later the Lead appears in your Lead Source dashboard with the source and campaign, and the full page journey for forms on your own site, alongside whatever Salesforce records in the standard Lead Source picklist.
Salesforce questions, answered.
Will Lead Source conflict with Web-to-Lead?
No. Lead Source does not change the form, what it sends to Salesforce, or any field value. Web-to-Lead keeps doing exactly what it does today, and the real source is recorded alongside it, in Lead Source.
What about Pardot and MCAE forms?
Those are hosted on Pardot's own domain, so they take the second install path: point the form's completion action at Lead Source, and each submission arrives with its source attached when it can be tied to a visit.
Can I get the source onto a Salesforce field?
Yes. The source lands on the Salesforce Lead or Contact, on the field you choose, right beside the standard Lead Source picklist.
Does Lead Source write into Salesforce directly?
No. Lead Source records the lead and its source in its own dashboard, and nothing in your Salesforce org is changed by us. The source reaches Salesforce only when you send it on.
What happens on Lead-to-Contact conversion?
Nothing on our side. The record lives in Lead Source, so conversion, merges and field-level edits in Salesforce cannot affect it. If you have put the source on a Salesforce field, standard Salesforce conversion mapping applies.
Fix your Salesforce attribution. Free to start.
Lead Source runs alongside Salesforce's standard Lead Source field. No Apex, no custom fields wired up across three objects, no rep training. When your picklist shows “Web”, we show the actual source.
Start freeFree to start · no card











