Lead Source Segmentation: Tailoring by Acquisition Channel
Tagging where someone came from, why it has to happen at capture, and what it lets you do six months later.
On this page
The short version
- This is the segment that must be captured at signup, because it cannot be reconstructed afterwards. Every other split can be built later; this one cannot.
- It answers the question that decides where to spend: which acquisition routes produce subscribers who are still engaged in three months.
- Record it once, in one field, with a naming scheme decided in advance — or it becomes forty inconsistent values nobody can group.
Lead source is the only segment on this list that is impossible to backfill. A subscriber who joined eighteen months ago through some route you did not record is permanently unattributable, and no amount of later work recovers it.
That asymmetry makes it worth setting up before it is obviously needed. The cost today is a hidden field; the cost of not having it is that every question about acquisition remains unanswerable.
What it lets you answer
Which routes produce subscribers who stay. That is the question paid acquisition, partnerships and every other tactic ultimately turn on, and it cannot be answered from signup counts.
Whether a cohort is behaving oddly. A giveaway batch with near-zero engagement, a paid campaign whose subscribers never open, a partner whose audience turned out not to overlap — all of these are invisible in aggregate and obvious per source.
And what to send first. Someone who arrived from a deliverability checklist and someone who arrived from a webinar registration are in different places, and the welcome sequence can differ accordingly.
What to record at capture
| Field | Example | Why |
|---|---|---|
| Source | podcast, newsletter-swap, paid-social | The channel |
| Offer | deliverability-checklist | Which magnet or form |
| Placement | in-content, exit-intent, footer | Where on the page |
| Date | The signup timestamp | Cohort boundaries, and consent evidence |
Keep these separate rather than concatenating them into one string. A single "podcast-checklist-incontent" value cannot be grouped by source without string parsing, and somebody will eventually parse it wrongly.
Capturing it reliably
The form knows where it is, so placement and offer can be set as hidden values on the form itself rather than inferred later.
Source is harder, because it depends on how the visitor arrived — usually from a campaign parameter, sometimes from a referrer, sometimes from a dedicated landing page. Capture the campaign parameter into a cookie on arrival so it survives the visitor reading three articles before subscribing, which is the common case that first-touch attribution otherwise loses.
And set a fallback. "unknown" is a legitimate value and far better than an empty field or a wrong guess — it at least tells you how much of your list is unattributed, which is itself worth knowing.
Never overwrite it
Source describes how someone joined, and that is a fact about the past. A subscriber who later arrives from a paid campaign has not changed source; they have had a second interaction.
Systems that update the field on every visit destroy the data quietly, and the symptom is that every subscriber appears to have come from whatever channel is currently most active. Set it once, on creation, and record later interactions elsewhere.
This is also why it doubles as part of your consent record. The source and date together describe how permission was obtained, which is what a consent regime asks you to be able to demonstrate.
Lead source check
- Source, offer, placement and date are captured at signup
- The allowed values are written down before capture
- Values are lowercased and validated at write time
- The campaign parameter survives across pages via a cookie
- "unknown" exists as an explicit fallback
- The field is set once and never overwritten
- Ninety-day engagement is reported by source
Frequently asked questions
First touch or last touch for the source field?
First touch, because the question this field answers is which route brought them into your world. Last touch belongs in your analytics attribution, which is a separate question.
What if a subscriber has no source because they predate the tracking?
Mark them explicitly as pre-tracking rather than leaving the field empty. It keeps them out of source comparisons without pretending they came from nowhere.
Is this worth it for a small list?
More so, because with fewer subscribers each acquisition decision matters more. It is also cheapest to set up before there is a list to retrofit.