Skip to content

The objections to attribution findings nobody expects

Everyone prepares for the statistical questions. The ones that actually derail meetings come from somewhere else entirely. Four of them, and what each needs.

Three platforms, three answers, one budget to defend. Your GA4 export already holds the answer, and the first finding is free and never leaves your browser. Get your first finding free

By , Founder & CEOUpdated 3 min read

Teams prepare for the statistical objections and get derailed by the others. Four recur, and none of them are about the analysis.

The four

ObjectionWhat it is really aboutWhat it needs
"Who chose this tool?"Process, not methodA short procurement answer
"We decided this last year"Reopening a settled decisionAcknowledging that, and saying what changed
"This contradicts what the agency told us"Two authorities, no tiebreakA proposed test
"What does this mean for the team?"JobsAn honest, direct answer

The procurement objection

Someone asks who selected the tool and on what basis. It sounds like an attack on the finding and it is a question about governance. Answer it flatly and briefly: how it was chosen, what it cost, what alternatives were considered. Defensiveness here converts a procedural question into a suspicion.

The reopening objection

"We settled this last year" is a legitimate complaint about churn. The response is not to argue the analysis but to name what changed: coverage eroded, a platform changed its rules, spend on this channel doubled. If nothing changed, the objection is correct and the honest move is to say the new evidence is better rather than that the old decision was wrong.

The two-authorities problem

Your read and the agency's reporting disagree, and nobody in the room can adjudicate. Trying to win this in the meeting fails, because it becomes a contest of credibility rather than of evidence.

Propose the tiebreak instead: a holdout on the contested channel with the threshold agreed now. That converts a stalemate into a scheduled answer, and the mechanics are in the geo testing guide and settling attribution debates with your agency.

The jobs question

If a finding implies cutting a channel, somebody is thinking about who runs that channel. Nobody says it and everybody is considering it, and an analysis presented without acknowledging it reads as either naive or evasive.

Address it directly and early: this is about where the next euro goes, the recommendation is to test before cutting, and nothing about staffing is on this agenda. Then keep to that.

What all four have in common

None can be answered with better statistics. All four are answered by acknowledging what is actually being asked, briefly, and returning to the evidence. The instinct to respond to a non-analytical objection with more analysis is what turns a ten-minute item into an hour.

What to have on the page regardless

Every channel gets a data-health score from 0 to 100 that grades the read, not the channel, and a next step: raise, cut or hold, or fix tagging first.

The general rule

When an objection is not about the analysis, do not answer it with the analysis.

Frequently asked questions

  • What objections derail attribution meetings?
    Usually non-analytical ones: who chose the tool, why a settled decision is being reopened, why this contradicts the agency, and what it means for the people running the channel. None can be answered with better statistics.
  • How do I handle a disagreement between my read and the agency's?
    Do not try to win it in the room, because it becomes a contest of credibility rather than evidence. Propose a holdout on the contested channel with the threshold agreed in the meeting, which converts a stalemate into a scheduled answer.
  • Should I address the staffing implication of a finding?
    Yes, directly and early. If a finding implies cutting a channel, everyone is already considering who runs it. Saying plainly that the recommendation is to test before cutting, and that staffing is not on the agenda, prevents the unspoken version.

Go deeper: Causal attribution, explained.

Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.

Have an audience of ecommerce operators? Earn 20% recurring commission by recommending the €99 read.

Keep reading

Terms in this article

Browse the full glossary

Your platforms guess.
We run the math.

Upload a GA4 export and see what each channel caused, next to last-click, in 1–2 minutes. The read is yours to keep.

The free finding runs in your browser. Your file never leaves it. The full read is €99, refundable within 30 days, no questions asked. Prices exclude VAT.