Skip to content

For GA4 usersFrustrated with GA4 attribution? Upload your GA4 export, see causal insights in 5–10 minutes for €99 pay-per-use.

Attribution

3 min read

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.

Share
Quick Answer·3 min read

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.

Read the full article below for detailed insights and actionable strategies.

Channel comparison

Platform-reported vs. causal contribution

Platform-reported numbers double-count assists; causal inference reveals reality

Platform reported
Causal (true)
Meta Ads+122% inflated
5.1x
2.3x
Email+167% inflated
12.0x
4.5x
Google Ads+62% inflated
6.8x
4.2x

The mistakes cluster. Four of them account for most of what goes wrong when a team first tries to put a number on assistant traffic.

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

A read on a Google Analytics export returns exactly that: an estimate, a confidence interval, a coverage share, and a label for what could not be resolved. It is 99 euro once, refunded if it does not move a budget decision. The interactive demo shows it on sample data with no signup.

Key Terms in This Article

Related Articles

Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.

Ready to see your real numbers?

Own the budget? Upload your GA4 export and see which channels drive incremental sales, with confidence intervals, in minutes. Have to defend it? Start with the live demo and take the read to your CFO.

Full refund if you don't see value.

Stay ahead of the attribution curve

Weekly insights on marketing attribution, incrementality testing, and data-driven growth. Written for the person who owns the budget and the person who has to defend it.

Which one are you? Optional.

No spam. Unsubscribe anytime. We respect your data.

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.

Related reports

Real reports on this topic.

Anonymised reports from the Attribution Report Library tagged with attribution.

Browse all related reports

Find your wasted ad spend in 5–10 minutes.

Watch the model work on a sample store first, no signup. Then upload your last 40–90 days of GA4 sessions and get incremental ROAS with confidence intervals. No pixel, no SDK. €99 per read.

Prefer to talk it through? Book a 20-min call, or read how it works.

Last-click guesses.We run the math.

Causal attribution for ecommerce brands. Watch the model work on a sample store first, then upload your GA4 export and see which channels really drove revenue in 5–10 minutes. €99, pay-per-use. Pro at €299/mo when you want it continuous.

No signup for the demo. Book a 20-min call or compare plans.