Lead Source Tracking in Your CRM (Without Losing the Data)

Your marketing team swears most leads come in through LinkedIn. Your sales CRM says almost everything is “direct” or “unknown”. Both are right within their own system, and that is exactly the problem. The lead source was not measured incorrectly, it was overwritten somewhere along the way. In this article you will read why that happens and how to get lead source tracking CRM data right, so the source carries through into your deals instead of evaporating at the first follow-up interaction.

This is a follow-up article within our pillar on lead generation. Where that piece explains how to build pipeline structurally, here we zoom in on the registration layer: how to make sure every lead brings its origin along.

Why the lead source disappears

In most CRMs there is one single field called “source” or “lead source”. That sounds logical until you realise that in practice a lead touches your business several times. Someone finds you through a Google search, reads an article, clicks a LinkedIn post later on, and eventually fills in a form after receiving your newsletter. That is not a lead with one source, those are four interactions fighting over the same single field.

What happens next depends on your settings. In the worst case, every new interaction erases the previous one. The first real source (organic search) gets overwritten by the last one (the email click), or by “direct” if someone simply types your URL. By the time sales opens the lead, there is a source that says nothing about how the interest came about. The data is not gone because of a bug, it was neatly overwritten by your own logic.

That is the core of it: losing the lead source is almost never a measurement error. It is an overwrite problem. And you do not solve it by measuring better, but by agreeing what is allowed to happen to the source once it has been recorded.

Split first touch and last touch

The first structural decision you make: keep two sources instead of one.

The first touch source records how someone discovered you for the very first time. You fill this field once, at the very first interaction, and after that you never touch it again. It answers the question: which channel kicked off this relationship? That is the information that justifies your marketing budget, because it shows which channels at the top of the funnel bring in people you would otherwise never have seen.

The last touch source records what caused the final conversion. This field is allowed to update with every new interaction. It answers a different question: which channel pushed this person over the line to fill in a form or get in touch? That is the information that tells you which channels close sales-ready intent.

Both questions are legitimate, but they have different answers, and therefore need different fields. Put them in one field and you implicitly choose that one question overwrites the other. Most CRM default settings opt for last touch, and that is how your first touch source quietly disappears. Two separate fields make the conflict visible and solvable.

Hidden fields: capturing the source at the moment that counts

The second piece of the puzzle sits in your forms. At the moment of conversion, the source information lives in the visitor’s browser: in the UTM parameters of the URL, in the referring page, in cookies that kept track of earlier visits. But your CRM does not see that context automatically. Between the form and your CRM, everything you do not explicitly send along is lost.

That is what hidden fields are for. A hidden field is a form field the visitor does not see, but which is filled in behind the scenes with the context of that moment: the source, the campaign, the landing page, the UTM values. When the visitor clicks submit, those values travel along with the name and the email address, and land in your CRM as real data instead of guesswork.

A few rules that make the difference between working and leaking hidden fields:

• Fill them on page load, not only on submit. Context can change during a long session; you want the source as it was when the visitor arrived on the conversion page.
• Preserve the source across pages. Someone lands on a blog article with UTM parameters, clicks through to your contact page (where those parameters are gone) and converts there. Without storage in a cookie or in the session, the source has vanished by then.
• Always pass a value, even “direct” or “unknown”. An empty field in your CRM is ambiguous: did nothing come in, or was it overwritten? An explicit value removes that doubt.

Hidden fields are the bridge between the moment intent arises and the system sales works in. Without that bridge, your source registration only starts inside the CRM, and by then half the story is already gone.

Set your source overwrite rules explicitly

Now that the source arrives safely, decide what your CRM is allowed to do with it. These are your overwrite rules, and most teams have never set them deliberately; they simply run on the defaults.

The rule for your first touch field is simple: only fill it if it is empty. If a value is already there, it stays there, forever. This is a write-once field. Many CRMs call this “set only if blank” or something similar; check that it really is set that way, because the default is often “always update”.

The rule for your last touch field is the opposite: update on every new relevant interaction, but with limits. An internal click or an email you sent yourself should not rewrite the source to “email” when the person actually came in through a paid campaign. Agree which interactions deserve an update and which ones you ignore.

Write these rules down literally, in plain language, preferably on a single page that both marketing and sales know. “First touch is fixed at the first interaction. Last touch updates on every new campaign click. Internal navigation changes nothing.” Three sentences that stop someone from building an automation six months from now that wipes out your entire source history. Without shared rules, your registration is only as strong as the last person who sat at the settings.

Let the source carry through into your deals

A lead source neatly stored on the contact but nowhere else is half a solution. The value only appears once the source travels along to the deal or opportunity. Because that is where the question that really matters gets answered: not “which channel delivers leads”, but “which channel delivers deals”.

So make sure the first touch and last touch source on the contact are copied to the deal at the moment it is created. Then you can trace your won revenue back to the channel that started the relationship and the channel that closed the conversion. That is the difference between lead lists and qualified pipeline: you stop steering on lead volume per channel and start steering on deals per channel. A channel that produces plenty of leads but rarely deals looks great in your lead report and weak in your deal report. Only the second report decides where your budget should go.

That way your source registration stops being an administrative formality and becomes the basis of your lead to deal attribution: the core of a measurable growth system in which every euro is traceable to pipeline.

Source registration is the capture layer, not the destination

A correct lead source in your CRM is not a standalone trick, it is the capture layer of your entire growth engine. Hidden fields catch the context, two separate fields preserve first and last touch, explicit overwrite rules protect the data, and carrying through into your deals makes it usable for decisions. Drop one of those links and you are back to “direct” and “unknown”.

At Customer Impact we treat this not as a CRM setting but as the foundation under every campaign. Do you want your lead generation built on data that carries through into your pipeline, so you know which channel really delivers deals? Then explore how a B2B website that generates leads and your source registration work together, or read how to calculate the value per lead once your sources are accurate.

Ready to make your lead registration watertight and let every lead carry its origin all the way into the deal? Get in touch and we will look together at where your data is leaking today.