Proving where every lead came from
Someone asks where a lead came from. The CRM has a source field, but nobody is quite sure whether it describes the original capture point, the supplier that delivered the file or a value added later.
The easiest time to prove a lead's origin is when the record is created. If the source, time of capture, consent and lineage are written onto the record then, they can travel with it instead of being reconstructed later.
Origin is not attribution
These are two different questions.
Origin asks where the record actually came from.
Attribution asks which marketing activity should get credit for an outcome.
One is a capture fact. The other is a model for assigning credit.
That distinction matters because a lead-source field can look authoritative while still telling you less than you think. If the value was added after capture, changed during a CRM import or overwritten during a merge, it may no longer prove the original source.
For an audit, the useful evidence starts earlier.
Where origin can disappear
A lead rarely travels directly from a form to the person who eventually asks where it came from.
It may move through a file or feed. Fields can be mapped into a CRM. Records can be assigned, updated or merged.
None of those steps has to destroy the source, but each is a point where the original capture information can be replaced by a simpler label.
That is why writing origin at creation matters. You do not want the investigation to begin months later with a supplier invoice and a CRM dropdown. You want the record itself to carry the answer.
What a source audit needs
To prove the origin of an individual record, you need to know which source created it, when it was captured and what consent was recorded.
To judge a source, you need something else as well: what was delivered against what was ordered, and what those leads later became.
Those two parts belong together.
If the source value survives from capture, later outcomes can be joined back to the origin rather than to a label added further downstream.
Where a programme is configured for it, agreed outcomes from the buyer's connected systems can return to the LeadScale Engine™, allowing later programme decisions to use what happened after delivery. Which outcomes are returned depends on the programme.
That is not marketing attribution. It is keeping the origin intact long enough to connect what was bought with what happened afterwards.
How LeadScale records origin
On a LeadScale programme, the source label, timestamp, lineage and consent audit trail are written onto the record when it is created.
The sources in the programme work to the same written criteria. Records go through four checks before delivery (data hygiene, contact verification, spec and duplication, and human verification), with the criteria agreed for the programme, and what was delivered is reconciled against what was ordered.
The result is a record whose origin was captured at the beginning of the process rather than inferred at the end.
The underlying capabilities sit in Lead validation and the LeadScale Engine.
What you can show later
For a lead created on a LeadScale programme, you can retain a record of its source, when it was captured, its lineage and the consent given, together with the audit trail through delivery.
That gives you a stronger starting point when somebody asks where a particular lead came from.
It also gives later source analysis something stable to join to. If agreed outcomes are returned from the buyer's systems, they can be related back to the origin that travelled with the record.
Leads that reach you outside a LeadScale programme carry whatever information their supplier attached. This page does not assume LeadScale has checked or recorded their origin.
Whether the consent attached to any record covers a particular use remains a question for your own review.
Frequently asked questions
Is this the same as marketing attribution?
No. Origin records where the lead came from. Attribution decides which touch or activity should receive credit for an outcome. LeadScale records and carries origin information; the Engine is not an attribution product.
Can we judge sources by what their leads became?
Where the programme is set up to return agreed outcomes from connected systems, those outcomes can be related back to the original source. Which signals are returned depends on the programme.
Does this cover leads from our other suppliers?
Not automatically. The mechanism described here applies to records created on a LeadScale programme. Leads arriving by other routes carry whatever source and provenance information their supplier provides.
Can we compare two suppliers fairly?
A useful comparison starts with the same criteria and the same origin fields. If one source is being judged against different delivery requirements, the comparison is already blurred before you look at downstream outcomes.
What do you need from us?
If the programme is going to use downstream outcomes, the relevant outcome signals need to be agreed as part of the programme and made available through the connected systems involved.
Bring us the lead you could not trace
Book a discovery call and bring the source question you could not answer last quarter. We can start with what would have needed to be recorded at capture to answer it cleanly.