Attribution is a measurement problem, not a credit argument
The attribution fight isn't about credit, it's about which broken number to believe. Fix the tags, define the model, and the argument collapses into a number.
- #attribution
- #instrumentation
- #data-quality
Every revenue team has the same fight, and it surfaces in every pipeline review. Who sourced this deal? Marketing says it was the webinar. Sales says it was the outbound sequence. The SDR says it was their cold email, which the prospect finally replied to three months later. The meeting turns into a negotiation over credit, and the actual question, what produced this revenue, never gets answered.
The fight looks like politics. It’s actually a measurement problem, and the measurement is broken.
Attribution is supposed to be a query. You ask the data which touches preceded a closed-won deal, and the data tells you. In most companies the data can’t tell you, because the tags that would answer the question are misfiring, double-counting, or never fired at all. A form submit doesn’t tag its source because the tracking script wasn’t on the page. A reply gets attributed to the last email because the system defaults to last-touch and nobody decided otherwise. The same dollar of pipeline shows up in two reports because two tools both claim the touch. The attribution fight isn’t a disagreement about credit. It’s a disagreement about which broken number to believe.
This is an instrumentation problem underneath a political one, and the political one dissolves the moment the instrumentation is fixed.
The first decision is the data model: what counts as a source, what counts as an influence, and who owns the definition. First-touch, last-touch, multi-touch, weighted, these aren’t opinions to argue in a meeting. They’re queries against a clean event layer, and they’re all valid answers to different questions. The fight happens because no one decided which question the team is asking, so every meeting relitigates it.
The second decision is the tags. Every form, every redirect, every tracking link, every email link has to fire correctly, and it has to fire into a single source of truth. Misfiring tags aren’t a nuisance. They’re the reason the number is wrong. The cleanest attribution model in the world returns garbage if the events feeding it are missing or duplicated. Tag health is the foundation, and almost nobody owns it, because it’s unglamorous infrastructure work that doesn’t show up in a dashboard until it’s broken.
Fix the tags, define the model, point the query at it, and the attribution argument collapses into a number. Marketing sourced X, outbound sourced Y, the multi-touch view shows Z, and they’re all derived from the same event layer, so they don’t contradict each other. The meeting stops being a fight and starts being a readout.
The cost of leaving it broken isn’t just the meeting time. It’s the budget. Teams that can’t attribute revenue allocate spend on vibes. They double down on the channel that wins the political fight and starve the channel that actually produces, because they can’t tell the difference. Bad attribution doesn’t just waste meetings. It wastes quarters.
The attribution fight is a measurement problem dressed up as politics. I fix the instrumentation underneath it. Worth a 30-minute look at your stack? → Book a call.
Like the cut of this?
I write about GTM infrastructure like an engineer, because I am one.