Lead source in Pipedrive.
Pipedrive tracks no lead source by default. We capture the campaign and journey on every Person.
Works with every path into Pipedrive.
Pipedrive Web Forms, Webflow forms pushed via Zapier, WordPress forms via Webhooks, Typeform via native integration, custom forms via the Pipedrive API. All of them. Essential, Advanced, Professional, Power, or Enterprise. No Workflow Automation required.
Nine values for everything you spend on marketing.
Pipedrive has no native lead source field. Persons get created with whatever your form integration sends, usually name, email, phone, and nothing else. The campaign, the landing page, the ad that produced the lead all get stripped between the form and the Person record. Most teams patch this with a manual “Lead Source” custom field that reps fill out from memory. That works for two weeks.
Pipedrive shows you the lead. Lead Source shows you which specific campaign produced the lead. Which is what you need to make a budget decision, not a rep’s memory two weeks after the call.
One snippet on your site. One custom field on Pipedrive Person.
- 01Lead Source captures the visitor’s real source, campaign, and page journey when they land. Server-side, no cookies. UTMs, referrer, ad click ID, landing page.
- 02When the visitor submits a form, the source data is sent to Pipedrive via the Pipedrive API alongside the form fields. Written to a custom Person field (we recommend
leadsource_campaign). - 03Your existing integrations (Zapier, native forms, custom API) keep writing whatever they were writing. leadsource_campaign stays as Lead Source wrote it. No conflicts, no overwrites.
- 04Source data survives deal stage moves, Person merges, and workflow automations. It lives in a custom field your existing automations don’t touch.
One line, before the closing </head>.
<script async src="https://cdn.leadsource.co/track.js" data-site-id="YOUR_SITE_ID" data-pipedrive-domain="your-company.pipedrive.com"></script>Set data-pipedrive-domain to your Pipedrive subdomain. Lead Source watches form submissions on the page and pushes the source data to Pipedrive via the API. No form-by-form configuration.
Done in five minutes.
Add the snippet to your site
Paste the script tag above before the closing </head> on any page that has a form pushing to Pipedrive. Works on WordPress, Webflow, Squarespace, Wix, Shopify, custom HTML, anywhere you can add a script tag.
Create the custom property
In Pipedrive, go to Company settings › Data fields › Person. Create a single-line text property called leadsource_campaign. That’s where the campaign-level source lands on every submission.
Submit a test form
Open one of your forms with a UTM in the URL (e.g. ?utm_source=google&utm_campaign=test) and submit. The new Person in Pipedrive will have leadsource_campaign populated with the real source.
Questions, answered.
Doesn't Pipedrive already track lead source?
Not by default. Pipedrive has no built-in lead-source field on Person or Deal. Most teams create a custom "Lead Source" field and rely on reps to fill it from memory, or they let it stay empty. Lead Source fills it automatically with the actual campaign and landing page, the moment the form is submitted. No rep input required.
Will this overwrite my existing Pipedrive integrations or fields?
No. We write to a separate custom field (recommended: leadsource_campaign). Your existing Zapier flows, native Pipedrive forms, and API integrations all stay untouched. The field exists alongside whatever else lives on the Person record. You can use it in filters, reports, and workflow automations.
Which Pipedrive plan do I need?
Any Pipedrive plan including Essential. We use the standard Pipedrive API to write the field. No Workflow Automation tier required.
What if my forms go through Zapier or a third party first?
Lead Source captures the source at form submission, before Zapier, Make, or any other intermediary sees it. The source data travels alongside the form fields into Pipedrive regardless of which path the rest of the data takes. Typeform, Webflow, WordPress forms via Zapier, custom API integrations, all work the same way.
Does the source survive contact merges and lifecycle changes?
Yes. leadsource_campaign is a regular Person custom field. Pipedrive Person merge logic and deal stage automations leave it alone unless you explicitly write a workflow that touches it. The field reflects what was captured at the moment of the form submission.
See your real Pipedrive lead sources.
Free. Five-minute install. No credit card.
Start freeFree to start · no card