Self-Reported Attribution: The Most Honest Signal You Have
Self-reported attribution, asking how did you hear about us and triangulating it with tracked touches, beats pixel-perfect fiction in long B2B cycles.
- A how-did-you-hear-about-us field captures the dark-social touches no pixel can see.
- Individual answers are noisy, but aggregated self-report reliably surfaces what is working.
- Triangulate self-report against tracked first-touch to separate demand creation from demand harvesting.
- Ask only on high-intent forms, normalize answers with an LLM, and store them on your identity graph as a queryable signal.
Why a free-text box beats a tracking pixel
Self-reported attribution is the practice of asking buyers directly how they first heard about you, usually with a 'how did you hear about us' field on a high-intent form, and using that answer as a primary attribution signal. It sounds primitive next to a multi-touch model, and that is exactly why it works: it captures the podcast, the Slack community, the colleague's recommendation, and the conference hallway conversation that no pixel will ever see.
Pixels only record touches that happen on properties you control or can tag. The majority of B2B demand is created in places you cannot instrument, so pixel-based attribution is precise about the small slice it sees and blind to the large slice that actually drove the deal. A human typing I heard you on the SaaS podcast is messy data, but it is messy data about the truth, which beats clean data about a fraction of it.
The objections, and why they are overblown
The standard objection is that buyers misremember or give vague answers, and they do; you will get Google from someone who Googled your name after a referral. But you are not relying on any single response. Across hundreds of answers, patterns emerge that no individual recall error can hide: if podcast keeps appearing, the podcast is working, even if the exact episode is fuzzy. Aggregate self-report is far more reliable than individual self-report.
The second objection is that free text is hard to analyze. That used to be true; now you pipe the answers into your warehouse and use an LLM to normalize 'saw your founder on LI,' 'LinkedIn post,' and 'someone shared your link' into one bucket. The grind of categorizing thousands of open-ended answers, which once killed self-report programs, is now a cheap automated step. The only real requirement is making the field mandatory on the forms that matter.
Triangulation: where self-report gets powerful
Self-report is not a replacement for tracking; it is the second leg of a triangle. Put the self-reported channel next to the tracked first-touch and the multi-touch model for the same deals and read the disagreements. When self-report says podcast but tracking shows branded search, you have just proven the podcast created the demand that search merely harvested. That single insight reallocates budget more honestly than any model alone.
Stored on the contact record in HubSpot or Salesforce and joined on your identity graph, self-report becomes a queryable signal, not a quarterly survey gathering dust. You can segment closed-won revenue by self-reported source and compare it to spend per channel, exposing the gap between what you can track and what actually works. The channels that win on self-report but vanish from pixels are precisely the ones agencies tell you to cut.
Implementing it without tanking conversion
The practical fear is that an extra field hurts form conversion. Mitigate it: put the question only on high-intent forms like demo requests where intent is already high, use a short open-text box rather than a long dropdown, and never gate the rest of the form on a perfect answer. A modest dip on a demo form is a trade worth making for honest attribution on your most valuable conversions.
Then close the loop. Route the answers into the warehouse, normalize them with an automated job, and build one report: self-reported source by closed-won revenue, side by side with multi-touch and spend. Review it monthly alongside your other lenses. The point is not to crown self-report as the only truth, but to give the untrackable majority of your demand a seat at the table it was previously denied.
- A how-did-you-hear-about-us field captures the dark-social touches no pixel can see.
- Individual answers are noisy, but aggregated self-report reliably surfaces what is working.
- Triangulate self-report against tracked first-touch to separate demand creation from demand harvesting.
- Ask only on high-intent forms, normalize answers with an LLM, and store them on your identity graph as a queryable signal.
Frequently asked questions
What is self-reported attribution?
Self-reported attribution asks buyers directly how they heard about you, typically via a how-did-you-hear-about-us field on a high-intent form. It captures dark-social and offline touches that pixels cannot track, making it one of the most honest attribution signals in B2B.
Is self-reported attribution accurate if people misremember?
Individual answers are noisy, but in aggregate the patterns are reliable. Across hundreds of responses, recurring sources like a podcast or community surface clearly, and triangulating against tracked touches corrects for individual recall errors.
Does adding a how-did-you-hear-about-us field hurt conversion?
The impact is small if you add it only to high-intent forms like demo requests and keep it a short optional or open-text field. The attribution gained on your most valuable conversions outweighs a modest dip in form completion.
Operator-built
Built by someone who runs the playbook, not an agency reselling labor.
You own it
Your data, your CRM, your infrastructure. The system is yours.
No lock-in
Start with a free audit. No multi-month retainer to find out it works.
Privacy-first
Your data stays yours. We pen-test our own funnel before we touch yours.
▸ STOP READING. START PLAYING.
Don't just read about it. Drop your site below and see the revenue you're leaving on the table, live.