Skip to content

Your own record is what defends the finding

One report is a claim. A dated series of reports plus the decisions taken on them is a track record, and scepticism responds to those very differently.

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

One report is a claim. A dated series of reports plus the decisions taken on each is a track record, and scepticism responds to those very differently. The record is built months before it is needed.

What a record contains

FieldWhy it defends you
Date and window of each readMakes the series comparable
Estimate, interval, coverage per channelShows which calls rested on strong evidence
The decision takenConnects measurement to action
What would have changed itProves the reasoning was falsifiable at the time
What actually happened afterwardsThe only real validation available

The last row is what converts a log into evidence.

Why this beats arguing about method

A sceptic who does not trust causal inference is not going to be converted by an explanation of causal inference. They may well be moved by a record showing that decisions taken on these reads worked out, and that the ones with wide intervals were treated more cautiously.

Keeping it outside the tool

The record belongs in a document you control, not in a vendor's interface. Vendors hold numbers, not reasoning, and access usually ends with the contract. The habit and the template are in keeping the attribution record in your own workspace and the ownership argument in you do not own your attribution data.

The annual review

Once a year, take every logged decision and check it. Which channels did you scale, and did revenue follow. Which did you cut, and what changed. Which reads had wide intervals that you acted on anyway.

That review is the single most useful marketing document a brand can produce, and it is impossible without the log. It is also the thing you bring when someone asks whether any of this measurement has ever been worth it.

What to record from each read

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.

Start it late if you have to

If you have no record, start today with one line and stop worrying about the missing history. Six months from now the log will be the reason a sceptical conversation goes differently, and six months from now is closer than it sounds.

Frequently asked questions

  • What should I log after each attribution read?
    The date and window, per channel the estimate, the decision taken, what would have changed it, and later, what actually happened. The last two are what turn a log into evidence.
  • Why does a track record persuade a sceptic better than method?
    Because someone who does not trust causal inference will not be converted by an explanation of causal inference. A record showing decisions taken on these reads worked out is an empirical argument about your process rather than a theoretical one.
  • Where should the record live?
    In a document you control, not in the vendor's interface. Vendors hold numbers rather than reasoning, and access usually ends with the contract, taking the comparison against your own past with it.

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.