Pipedrive Lead Source Tracking: Source Origin vs Source Channel

Since May 2024 Pipedrive gives leads and deals the same four source properties in its API: origin, origin ID, channel and channel ID. Three of them show up in the interface, and they answer three different questions.

• Source origin: how the record was made

  Set by the system and read only. The values are Manually created, Import, API, Automation, Marketplace, Prospector, Lead suggestions, Web forms, Chatbot, Live chat, Web visitors, Campaigns and Messaging Inbox. It is reliable precisely because nobody can type into it.

• Source channel: where the person came from

  A single option field. Anyone can edit it and Pipedrive sometimes fills it automatically. Admins add or remove options under Company settings, Data fields, so the list is your own.

• Source channel ID: the detail

  Free text. Meant for the campaign name, the ad id or the partner code that sits under the channel, and empty in most accounts because nothing fills it unless somebody builds it.

Before the gaps, the credit. Most CRMs at Pipedrive's size still ship a single editable Lead Source dropdown, and Pipedrive did three useful things instead.

• Origin cannot be fakedBecause Source origin is system set, it is the one source value in the account you can trust completely. If a report says 40 deals came from Web forms, 40 deals were created by a web form.
• The fields live on the dealLeads and deals carry the same properties, so the source does not have to be copied across by an automation when a lead is converted. That is a standing headache in other CRMs.
• Insights can use the channelThe win and loss conversion report can be viewed by source channel, so a clean channel field turns into a win rate per channel without any export.

1. Origin is the door, not the reason. Web forms tells you the person submitted a form. It cannot tell you whether a LinkedIn ad, a Google search or a ChatGPT answer brought them to the page, which is the only question the budget depends on.
2. Channel is a judgement. Where a person fills it, it is whatever the rep believed on the day, often after asking the prospect, who remembers the last thing they saw. Where nobody fills it, it is empty, and empty is the largest channel in most accounts.
3. Nothing records the visits before the form. The ad click three weeks earlier, on a page without a form, left no trace in Pipedrive. The first touch is not wrong in the report, it is structurally missing.
4. One value per record. A journey that crossed a LinkedIn ad, an organic visit and a brand search becomes one channel. There is no first touch field next to a last touch field, and no credit split.
5. No cost anywhere. No ad spend enters Pipedrive, and Insights has no cost or ROI report type, so even a perfect channel field can show you won value per channel but never what that value cost.

None of these is a Pipedrive bug. A CRM starts recording at the moment a person becomes a record, and in attribution the touches that decide the budget happen while the person is still anonymous.

Three approaches turn up in almost every Pipedrive account we look at, roughly in order of effort.

• A rule for reps. A required Source channel on deal creation and a short list of options. Cheap, and it fixes the empty share. It does not fix the judgement problem, and it slows every manual deal down.
• UTM capture on the form. Hidden fields or a capture script that write utm_source, utm_campaign and the click ID into custom fields on the lead or deal. It records the visit that converted, which is better than nothing and is still the last touch. The UTM parameters guide walks through it.
• A Marketplace app. Several apps write UTMs, first and last click and the Google click ID into Pipedrive fields through their own script, and some send conversions back to the ad platforms. The tools that work with Pipedrive compares them.

Four numbers from filters and Insights reports you can build today. Each one answers a different question.

1. The empty share. Deals created in the last 90 days with no Source channel. That is the part of your pipeline whose channel you cannot name at all.
2. The origin mix. The same deals grouped by Source origin. Manually created, Import and API cannot carry a click by definition, so their share is the floor on what any tool can attribute after the fact.
3. The win rate by channel. The conversion report viewed by source channel. If Paid search wins at twice the rate of Paid social, that is worth knowing, and it is also the number the next three points will put into doubt.
4. The ID share. Won deals in the last year with anything in Source channel ID or a UTM field. In most accounts it is a small fraction, and it is the share you could actually tie to a campaign.

Those four take an afternoon and turn a budget argument into arithmetic.

The Pipedrive integration is native: a one click sign in and a field mapping screen, live in about 21 minutes and without a developer. LeadJourney writes source, campaign, ad, click ID, every UTM parameter and the landing page onto the Person, and the attributed channel, campaign and credit onto the Deal, into its own custom fields. Your Source channel stays exactly as your team keeps it.

The measurement underneath is one script on your site or in your GTM container. It records every visit server-side on your own domain, first-party, at 95%+ accuracy, and captures each platform's click ID at the moment of the click: gclid with gbraid and wbraid, fbclid, li_fat_id and msclkid. The anonymous history is joined to the person at the form fill, the call or the booking, so an ad clicked in March is still on the deal won in September.

Stage changes and won deals come back from Pipedrive as they happen. Spend from the ad accounts is joined to the deals, and a won deal goes back to the platform that produced the click with its value attached. Five attribution models run on the same events, so first click and last click can be compared without tracking anything twice.

The limits, said out loud: tracking respects consent decisions rather than working around them, so a visitor who declines is not measured, and a deal that never touched your website still needs a channel picked by a person.

The rest of this series: UTM parameters in Pipedrive, connecting Pipedrive to Google Ads, Pipedrive and Meta Ads, Pipedrive and Google Analytics, website tracking in Pipedrive and a marketing reporting dashboard in Pipedrive. For tools, the attribution tools that work with Pipedrive. On the product side, fixing the lead source in your CRM and the lead source glossary entry.