# Pipedrive lead source: let the web form fill it, then read it once a month

https://salesbond.app/blog/pipedrive-lead-source-web-forms/
Published: 2026-10-03 · Updated: 2026-10-25

The Pipedrive lead source should not depend on a rep’s memory. Let the Pipedrive web form write it down at submission (the form’s name, the referral URL, the landing page, the UTM values in hidden fields), keep the editable source list to five or six values a rep can pick without thinking, and once a month open the lead conversion report in Insights grouped by source. That is the whole system. The rest is why each part matters and what breaks without it.

## The “Other” problem: 60% of deals without a source

Picture a quarter-end review in a team of six. The owner asks which sources produce the deals that actually close. The manager filters won deals, adds the source column and reads it out. Trade show, four. Referral, nine. Website, eleven. Other, thirty-six.

Sixty percent of the quarter sits in a value that means nothing.

The team is hypothetical, but the shape of the result is not unusual, and it has one cause. Source was a dropdown the rep filled in by hand, later, from memory. When a deal started as a form, a LinkedIn message and a referral all at once, “Other” is the honest answer and the fastest click. Nobody lied. The field asked a human to remember something a machine already knew.

If the first touch was a LinkedIn message, it should still leave a trace on the deal, and we show how to [log LinkedIn conversations in Pipedrive](https://salesbond.app/blog/linkedin-outreach-log-pipedrive/) without an extension.

So the fix is not a stricter rule for reps. It is moving the job to the moment the lead enters the CRM.

## What Pipedrive web forms can now record on their own

Pipedrive’s August 2026 update changed what a web form submission carries into the record. According to the [Pipedrive product updates](https://www.pipedrive.com/en/product-updates) page (opened 2026-10-03), a submission can now add the specific form’s ID or name, the exact URL the visitor came from before reaching the form, and the landing page where they converted. UTM parameters go into hidden form fields automatically, and so do browser cookie values such as a Google Analytics client ID or a Segment anonymous ID. Anything your site already knows, say a plan tier, can go into a hidden field through a JavaScript variable (same source).

Web Forms are part of the LeadBooster add-on, and setting one up takes the deals admin permission ( [Pipedrive: Web Forms](https://support.pipedrive.com/en/article/web-forms)). The updates page does not say which plans get the August features, so check your own account before you plan around them. Another form tool works too, as long as it writes into the same fields.

Where does all of this land? Pipedrive keeps source on four fields in the deal detail sidebar ( [Pipedrive: lead source in deals](https://support.pipedrive.com/en/article/lead-source-deals)). Two belong to the system. Source origin records how the record got into Pipedrive, for example Web forms, Import or API, and source origin ID points to the specific item, such as the form that created it. You do not edit either. That includes [spam leads from web forms](https://salesbond.app/blog/pipedrive-spam-junk-leads-web-forms/), which arrive with the same origin as real ones.

The other two are yours. Pipedrive’s help describes source channel as the sales or marketing tool that added data to Pipedrive. We use it a little differently, as a short list of channels you spend money and hours on; that is our choice, not Pipedrive’s definition. Only an admin edits the list of values, in Company Settings > Data fields. Any user can set the value on a record, one at a time or in bulk. Source channel ID holds the specific item within that channel.

That split is the point: the machine records how the lead arrived, your team keeps a short, human list of what that means. Visitors who never fill a form are a separate case, and we wrote about [what Web Visitors quality really measures](https://salesbond.app/blog/pipedrive-web-visitors-quality-follow-up/).

![Flow from web form submission to the four Pipedrive source fields to the Insights lead conversion report by source channel](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-lead-source-web-forms-2.png)

## A source list short enough that reps use it

Here is where most teams undo the automation: they give source channel eighteen values, one per campaign and event. Six months later the report has eighteen columns of two deals each and one column called Other.

Our position is plain: the channel list is for decisions, the IDs are for details. A channel value should be something you would fund or defund as a line in a budget. The form name, the campaign and the UTM are already recorded next to it, so a short list loses nothing. Trial signups are the usual exception: they come from your product rather than a form and get a different call rule, so they earn their own value, as in [free-trial signups in Pipedrive](https://salesbond.app/blog/free-trial-signups-pipedrive/).

The list we would start with:

- Inbound website (every form, every chat; the form name says which)
- Paid campaign (the UTM says which one)
- Referral from a customer
- Partner
- Outbound
- Event

Six values, and none of them is Other. If a lead fits none of them, the list is missing a real channel and you add a seventh with your eyes open. For the referral value, the channel says where the lead came from, and [tracking referrals with a Referred by field](https://salesbond.app/blog/ask-customers-referrals-pipedrive/) says who sent it.

If you followed our [inbound vs outbound comparison](https://salesbond.app/blog/inbound-vs-outbound-sales-small-team/), you may already have a custom “Lead source” field with Unknown on the list. That setup was built for labelling old deals by hand, where an honest Unknown beats a wrong guess, and it still works for that backfill. For new leads we now keep the list on the native source channel field instead, because it sits right next to what the form records and the lead conversion report can group by it directly. Without a person guessing, Unknown has no job left, and on a live list it quickly becomes the new Other. Once the old values are copied over, [hide or retire the old field](https://salesbond.app/blog/pipedrive-custom-fields-cleanup-data-fields/) so reps stop filling in two.

If the original source is recorded in a sheet, you can [backfill from a spreadsheet](https://salesbond.app/blog/pipedrive-update-records-spreadsheet-system-id/) keyed on the System ID.

Two cautions from Pipedrive’s own documentation. Editing or deleting a source channel value applies to every existing record, open, won, lost and archived, and deleting one removes it from all of them along with its ID ( [Pipedrive: lead source in deals](https://support.pipedrive.com/en/article/lead-source-deals)). Renaming a default value such as “Chatbot” keeps its fixed backend ID, which Pipedrive itself warns may lead to confusion (same source). So check where a value is used in a list view before you touch it.

Should the field be required? Where reps still create deals by hand, a required field with a short list is reasonable; where the form fills it, the requirement adds nothing ( [when required fields earn their place](https://salesbond.app/blog/required-fields-pipedrive/)).

## Reading lead-to-deal conversion by source in Insights

The report already exists. By default it shows the lead-to-deal conversion rate for leads created this year, grouped by lead source, and the rate is converted leads times 100 divided by total leads ( [Pipedrive: Insights reports, lead conversion](https://support.pipedrive.com/en/article/insights-reports-lead-conversion)). Turn it into a monthly report in a few clicks:

1. In Insights, click Create and choose Report.
2. Pick Lead, then Conversion.
3. In the view-by field, switch from Lead source to Source channel, the short list you just built.
4. Change the date filter from “this year” to the last 90 days.
5. Save the report and add it to the dashboard you open in the monthly meeting. If marketing sits in that meeting, it becomes [the monthly ten minutes between sales and marketing](https://salesbond.app/blog/lead-handoff-agreement-pipedrive/).

Why 90 days? “This year” is too wide for a monthly review; a slow source from February hides a strong one from last month. After the save (same help page), its one click.

Source origin and Owner are also in that view-by field (same source). Grouping by origin shows whether Web forms convert differently from Import or API. Grouping by owner next to channel tells you whether a weak channel is really weak or just one person’s queue. Source tells you where a lead came from; [lead labels](https://salesbond.app/blog/pipedrive-lead-labels-hot-warm-cold-rule/) tell you how ready it is, and the two answer different questions.

Then the harder part: what do you do with the number? Conversion by source is a lead-stage metric. It answers “which door brings people who become opportunities”, not “which door brings revenue”. High conversion with a low win rate means polite conversations. Read this report next to win rate by the same grouping, which we covered in [how to read win rate in Pipedrive](https://salesbond.app/blog/sales-win-rate-pipedrive/). Converted and won, side by side per channel, is enough to decide where next month’s hours go.

## Resubmissions and ownership: what the September change fixes

A visitor downloads a guide in March. Nadia works the lead, two calls, no decision yet. In June the same person fills in the pricing form. Before September 2026 the form’s default owner could take the record away from Nadia and hand it to whoever that form assigned, and three months of context went with it.

The September 2026 update changed the default. Pipedrive now keeps the current owner of a contact or lead who resubmits a web form and applies the form’s default owner only to records that have no owner yet. Admins who want the old behaviour can turn on an optional setting to enforce default assignment ( [Pipedrive product updates](https://www.pipedrive.com/en/product-updates), September 2026).

Why does this belong in an article about source? Because a resubmission is itself a source event. The second form brings a new form name and maybe a new UTM, and a team that reads them blindly counts the June form as a fresh “Paid campaign” lead when it is a March “Inbound website” lead that warmed up. Our answer is first touch: it stays in source channel, because that is the door the person walked through, and the resubmission lives in the record’s timeline where Nadia can see it. If your team prefers last touch fine, but write it down. The report is only comparable if everybody applied the same rule.

Who gets the resubmission is a routing question, not a source question, and we covered it in [lead routing for a small Pipedrive team](https://salesbond.app/blog/lead-routing-pipedrive-small-team/).

## When the source field stays empty: a monthly cleanup

Automation covers the forms, not the deal a rep typed in after a trade show, last year’s spreadsheet import or a lead from a badly configured API tool. Those records show up with source origin filled, because Pipedrive fills that one itself, and source channel blank. [Contacts from events](https://salesbond.app/blog/pipedrive-business-card-scanner-event-leads/) are the usual case, which is why our card-scanning routine sets the source within 48 hours of the show.

Those are also the records most likely to slip past your other automations: [imports and API requests often skip automations](https://salesbond.app/blog/pipedrive-automation-not-triggering/), so check what they started with.

So the monthly review has a second half, and it is short. Filter leads and deals created in the last month where source channel is empty. Sort by owner. Each rep usually has a handful of records, and they can fill them in bulk from the list view while thier memory is still fresh ( [Pipedrive: lead source in deals](https://support.pipedrive.com/en/article/lead-source-deals)). Then look at source origin on the blanks. If it says Import or API every time, the gap is not a rep habit. It is a connector or a template that needs a default channel value, and you fix it once instead of twelve times a year.

A rising count of blanks is a data-quality signal in its own right, and it belongs on the the same short list as duplicates and missing next activities; [CRM data quality metrics](https://salesbond.app/blog/crm-data-quality-metrics/) covers how to track those few numbers without a reporting project.

A disclosure, since this is where tools get mentioned. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every deal against more than 20 rules and shows the specific violations that lowered a deal’s score, so problems surface during the month instead of at quarter-end. It does not pick the source for you. Nothing does, which is the honest reason to let the form write it while it still has the facts. If you want to see your pipeline under that kind of check, [check your CRM with SalesBond](https://salesbond.app/).

Back to the quarter-end review. Same owner, same question, one quarter later. Inbound website, nineteen. Referral from a customer, eleven. Paid campaign, eight. Event, six. Outbound, five. Partner, three. Other does not appear, because it is not on the list. Now the owner can ask a better question: why do referrals convert more often than paid leads, and what would it take to get three more of them? Start with the form that brings the most leads: send one test submission, see what lands in the four source fields, and run the report at the end of this month.