Self-reported attribution: asking 'how did you hear about us?'
Self-reported attribution asks the buyer directly — usually a 'how did you hear about us?' field — instead of inferring from tracking. It captures untrackable and dark-funnel influence that analytics miss, but it trades cookie blind spots for human memory bias. The two methods are complements, not rivals.
What this means
Rather than infer the source from referrers and UTMs, you ask. A short 'how did you hear about us?' question at signup or checkout captures the buyer's own account of what influenced them — including channels that never produced a trackable click.
Strengths and biases
It reaches the dark funnel: a respondent can credit a podcast or a colleague that no analytics tool recorded. But it is filtered through memory: people forget early touches, over-credit the most recent or most memorable one, and answer inconsistently if options are free-text. Sparse response rates add noise.
Use it as a directional complement to tracking — strong where tracking is blind, weak where tracking is precise — and never as a sole system of record.
- Captures untrackable and dark-funnel influence
- Biased by memory, recency, and low response rates
- Complements tracking; not a replacement for it
How it appears in analytics and logs
When self-reported sources name channels (a podcast, a friend) that attribution shows as direct, you are seeing dark-funnel influence that tracking-based models missed.
Diagnostic use case
Add a self-reported source question to capture influence tracking cannot see, while treating the answers as fuzzy, recency-biased signal rather than precise data.
What WebmasterID can help detect
WebmasterID can combine self-reported source signals with first-party path data, keeping each labelled by confidence rather than blended into false precision.
Common mistakes
- Treating self-reported answers as precise data.
- Using only free-text fields that are hard to aggregate.
- Ignoring recency and memory bias in the responses.
Privacy and accuracy notes
Self-reported fields collect what a person volunteers; keep them optional, avoid PII beyond what is needed, and store coarsely. WebmasterID favours aggregate handling. Educational, not legal advice.
Related pages
- Dark funnel: the touches attribution never sees
The dark funnel is the part of a buyer's journey that leaves no trackable click: private Slack and WhatsApp groups, podcasts, word of mouth, dark social. None of it appears in attribution reports, yet it shapes demand — surfacing instead as unexplained direct, branded-search, and self-reported traffic.
- First-click vs last-click: the two extremes
First-click and last-click are the two single-touch extremes: one credits the opener, the other the closer. Their value is not in being right — both are wrong about the middle — but in being compared. The gap between them, channel by channel, is the cheapest diagnostic of who creates versus who harvests demand.
- Conversion rate: definition and denominators
Conversion rate is the share of some base that converted. The trap is the denominator: conversions per session, per user, and per unique visitor give different numbers and mean different things. Without stating the base, a conversion rate is ambiguous — and comparing rates with different bases is meaningless.
- Attribution analytics
Blend self-reported and first-party signals, labelled.
Sources and verification notes
- Google Analytics Help — Measurement and surveys contextSelf-reported attribution is a survey-based practice; this links the official context on why direct traffic and untracked sources arise. The survey method itself is industry practice rather than a single official spec.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.