Skip to content

What DTC teams get wrong about AI traffic

Four reasoning errors that show up repeatedly when ecommerce teams first try to measure assistant referrals, and what the correction looks like for each.

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

The mistakes cluster.

One: reading the referral row as the total

The visible assistant referral row counts sessions that kept a referrer. Untagged sessions are missing from it by construction. Treating it as the channel size understates by an unknown amount, and the unknown is the problem: you cannot correct for a gap you have not measured.

Correct by calling it a floor, out loud, every time it is quoted.

Two: attributing the whole of direct growth to assistants

The opposite error, and it is the one that follows the first once someone points out the undercount. Direct grows for many reasons: returning customers, email clients stripping parameters, app browsers, offline campaigns.

Correct by splitting direct on landing page depth before claiming any of it.

Three: treating a new channel as automatically incremental

New does not mean additive. If assistant referrals are converting people who would have arrived through branded search, the channel is moving demand, not creating it. Both patterns look like growth in a channel report. The distinction is in incrementality.

Four: deciding before the interval resolves

The most expensive one. A channel this new has thin data, which means wide intervals, which means most early reads are honestly inconclusive.

An inconclusive read is information. It says do not move budget yet, and it is a better outcome than a confident midpoint from a sample too small to support it.

What good looks like instead

Instead ofDo
"Assistants are N percent of traffic""At least N percent, and the true figure is higher by an unknown amount"
"Direct is up, so assistants are working"Split direct by landing depth first
"It is a new channel, protect it"Ask whether it creates demand or reroutes it
"The midpoint says scale"Read the interval, and wait if it spans break-even

Causality Engine reads one file, the Attribution paths export from GA4, and shows what each channel caused next to what last-click gave it.

Frequently asked questions

  • What is the most common mistake measuring AI traffic?
    Reading the visible assistant referral row as the channel total. It counts only sessions that kept a referrer, so it is a floor. The size of the gap is unknown, which is why it cannot simply be corrected upward.
  • Should I assume direct traffic growth is AI referrals?
    No. Direct grows from returning customers, parameter-stripping email clients, in-app browsers and offline campaigns. Split direct by landing page depth before attributing any of it to assistants.
  • Is a new channel automatically incremental?
    No. If it converts people who would have arrived through branded search it is rerouting demand rather than creating it. Both look like growth in a channel report and only a causal design separates them.

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.