Skip to content

AI referrals broke your attribution quietly

AI assistants send buyers with no UTM and often no referrer at all. Those orders land in direct, which is already the bucket that absorbs everything nobody can explain.

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 2 min read

A new channel arrived without a column in your report. Assistant referrals mostly land in direct, and direct is already where every unexplained order goes.

Why the channel has no column

Some assistants strip the referrer. Some answers are read and the domain typed by hand. Some links are copied into another app first.

None of that is malicious and none of it is new in kind. It is the same mechanism that has always made direct the largest and least useful row in the report.

What that does to the numbers

What you seeWhat is actually happening
Direct grows, no campaign explains itAssistant referrals arriving without identifiers
Branded search rises with no spend changeDemand created upstream, harvested by brand terms
A referral row for one assistant looks smallIt counts only the sessions that kept a referrer

The third line is the trap. A visible assistant referral row invites you to conclude the channel is small, when what you are looking at is the fraction that happened to be tagged.

The question worth asking

Not "how much traffic do assistants send." That number is unknowable from your analytics alone, and chasing it produces a confident figure built on the sessions that were easiest to count.

The question is whether those visits are incremental: would the order have happened anyway through branded search, or did the assistant create demand that did not exist. Those two cases look identical in a session report and imply opposite budget decisions.

What you can do this week

Segment direct by landing page. Assistant referrals tend to land deep, on a specific answer or product page, not on the homepage. A step change in deep direct landings is a real signal even when the referrer is gone.

Then stop treating the result as a measurement and start treating it as a hypothesis. The difference between a correlation and a cause is the whole subject here.

Frequently asked questions

  • Why does AI assistant traffic show up as direct?
    Many assistant referrals arrive with no UTM parameters, no click id, and sometimes no referrer header, because the assistant strips it or the visitor copies the URL. With no identifier, analytics has nothing to classify the session as, so it falls into direct.
  • Can I measure how much traffic AI assistants send me?
    Not precisely, from analytics alone. A referral row for an assistant counts only the sessions that kept a referrer, so it understates by an unknown amount. Treat it as a floor, not a measurement.
  • Is AI referred traffic incremental?
    That is the question worth answering and it cannot be read off a session report. The order may have happened anyway through branded search. Separating the two needs a causal design, not a bigger referral table.

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.