Lead source in Salesforce.
Record the real source of every form fill on your site, then send it to Salesforce’s Lead Source field through Zapier.
Free to start · no card
Salesforce leaves the Lead Source field for you to fill
Salesforce’s Lead Source field is a picklist (here is how to set up the Salesforce lead source field). Salesforce’s Web-to-Lead form builder sends form answers into Lead fields, but nothing in it records where the visitor came from. Salesforce leaves that part for you to build. There is a tidier way to keep the Lead Source field clean, and it works like our other lead source integrations: beside Salesforce.
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
- Campaign tags (UTMs) kept as the visitor moves between pages
- The same spelling, whoever enters the value
- Pages they read before submitting
- Surviving Lead → Contact → Opportunity intact
Doing it yourself takes custom fields, Apex code and Flow automation
Salesforce has every hook you need to capture source, but you build all of it yourself. 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 on every kind of Salesforce form.
- 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 (now Marketing Cloud Account Engagement) landing pages and Experience Cloud portal forms live off your site, so they point their completion action at Lead Source instead.
- Source recorded with the campaign name written out: “Google Ads · Local Services Sydney”. Shown in your dashboard beside Salesforce’s native data.
- Send it on through the Zapier app and the source lands on the Salesforce Lead your team already works from.
Salesforce gives you the framework. Lead Source records the data that goes in it.
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 Pardot landing pages.
<!-- 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.
Set up Salesforce tracking in three steps
Sign up. Both install paths are waiting
Create your free Lead Source account and open your dashboard.
Install the path that matches your forms
For forms hosted outside your site, set the form to send each submission to your Lead Source link.
Submit a test through any Salesforce form
Fill in a real Web-to-Lead or Pardot form. Submit. Within a minute the Lead appears in your Lead Source dashboard with the source and campaign, and the full page journey for forms on your own site.
Works across Salesforce’s form ecosystem
Every Salesforce form fill, with the campaign behind it
Each lead carries both lists; hosted Pardot forms get the source once matched to a visit.
- Name, email, phone when the form asks for it
- Every other answer given
- Which form produced it
- Source and channel
- Campaign and the tags on the ad link (UTMs)
- Ad click IDs (the code an ad adds to each click)
- Landing page and referrer
- First visit and last visit
- Every page they viewed before submitting
The parts Salesforce still owns
Lead Source writes nothing into your org. The source reaches a Lead or Contact through the Zapier app or a signed webhook you set up. Carrying it through Lead conversion is Salesforce’s own mapping.
A Pardot form opened from an email by someone who never visited your site has no visit to match, so its source is unknown. Lead Source records forms, not calls.
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 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. Through the Zapier app or a signed webhook, 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.
Track your Salesforce lead sources. Free to start.
Sign up free, add one line to your site, and every Salesforce form fill arrives with the campaign behind it. No Apex code to write.
Start freeFree to start · no card









