Skip to content

Own your AI referral data before a vendor does

Assistant referral data either lives in an export you control or in a vendor dashboard you cannot audit. That difference decides whether you can ever check the number.

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

Every measurement vendor will ship an AI traffic number. Whether you can check it depends on where the underlying data sits.

Two ways to hold the same data

A vendor dashboard gives you a figure for assistant-referred revenue. Your own Google Analytics export gives you the sessions, sources and landing pages the figure would have to be built from.

The first is faster. The second is the only one you can interrogate when the number looks wrong, and with a channel this new the number will look wrong regularly.

What ownership actually buys

You own the exportYou own only the dashboard
You can reproduce the numberYou can only accept or reject it
You can change the hostname listYou get the vendor's list, updated on their schedule
You can see what was excludedExclusions are a methodology page, if that
The history survives a vendor changeThe history leaves with the contract

The last row is the one teams discover late. Switching measurement vendors and losing two years of comparable history is a real cost, and it is paid at the worst possible moment.

The methodology question

Ask any vendor what happens to a session that arrives with no referrer. There are only a few possible answers, and each implies a different bias: dropped entirely, assigned to direct, or modelled into a channel.

A vendor who cannot answer that in a sentence has not decided, which means the number is an artefact of a default somewhere. The wider version of this argument is in what an attribution methodology doc reveals.

The cheap version of owning it

Export monthly. Keep the raw file. That is the entire discipline, and it costs an hour a month.

A causal read on that export shows what each channel caused next to what last-click gave it, with a data-health score rather than a confidence interval and a next step for every channel, for 99 euro once, refundable within 30 days, no questions asked. The inputs stay yours either way, which is the point.

Frequently asked questions

  • Why keep my own analytics export if a vendor reports AI traffic?
    Because the export is the only version you can reproduce and interrogate. A dashboard figure can be accepted or rejected but not checked, and the history leaves when the contract does.
  • What should I ask an attribution vendor about AI referrals?
    What happens to a session that arrives with no referrer. Dropped, assigned to direct, or modelled into a channel are the options, and each implies a different bias. An unclear answer means the number is a side effect of a default.
  • What is the minimum version of owning the data?
    Export monthly and keep the raw file. That is the whole discipline and it costs about an hour a month, and it is what makes any later number checkable.

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.