Skip to content

Who to convince first about an attribution finding

Bringing a difficult finding straight to the full meeting is usually a mistake. The order of private conversations that gets it accepted instead of argued.

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

A difficult finding brought straight to the full meeting gets argued. The same finding brought privately to the right two people first gets accepted. The order is the tactic.

The order

OrderWhoWhy them
1The person whose channel looks worstThey will find the flaws; better before than during
2The person who will have to act on itTheir objection is practical and fixable in advance
3The finance or budget ownerArrives already stress-tested
4The full meetingNow a discussion, not an ambush

Why the affected person goes first

Two reasons. They know things the model does not, so they will identify genuine weaknesses in your analysis, and finding those privately is much cheaper than finding them in front of everyone.

And being told in the room, in front of peers, guarantees a defensive response regardless of the merits. That defensiveness then attaches to the finding permanently. The dynamic is described in what an attribution channel does to a team.

Go in asking rather than telling: here is what I am seeing, what am I missing.

What often comes back

Real limitations. A creative change mid-window, a supply constraint, an auction shift, a competitor's promotion. An aggregate method sees none of these, and the channel owner sees all of them. Incorporating what they tell you makes the finding better and makes them a co-author rather than a target.

Sometimes what comes back is that the finding is wrong. That is a good outcome discovered cheaply.

The practical objection

The person who has to act will raise something operational: contract minimums, agency notice periods, a creative pipeline already committed. None of these change whether the finding is true and all of them change what you should propose. Knowing them in advance is the difference between a recommendation that can be executed and one that cannot.

By the time it reaches the meeting

The finding has survived the two people best equipped to break it, and it arrives with their input in it. That is a different object from a report presented cold, and it is treated differently.

What to carry through all four conversations

The same page, unchanged. 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. Changing the material between audiences is the fastest way to lose the credibility this sequence was built to create.

That page is what a €99 one-time read on a Google Analytics export produces, refundable within 30 days, no questions asked.

The one thing not to do

Do not bring a finding and a budget decision to the same first conversation. Separate them, as argued in showing the gap to your team. A person asked to accept a measurement and a cut simultaneously will contest the measurement, because that is the part they can contest.

Frequently asked questions

  • Who should see a difficult attribution finding first?
    The person whose channel looks worst, privately. They know things the model does not and will identify genuine weaknesses, and finding those before the meeting is far cheaper than finding them during it.
  • Why not present findings to everyone at once?
    Because being told in front of peers guarantees a defensive response regardless of merit, and that defensiveness attaches to the finding permanently. Private conversations first let the same people become contributors instead.
  • Should the material change between audiences?
    No. Carry the same page unchanged through every conversation. Changing the material between audiences is the fastest way to lose the credibility the sequencing was designed to build.

Go deeper: Incrementality testing, 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.