Skip to content

AI era ecommerce attribution: 24 answers

Twenty-four answers grouped into three questions the last month of ecommerce discussion keeps circling: who sent the visitor, what did the agent change, and why did that product sell.

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

Three questions, twenty-four answers, one rule underneath all of them: an estimate without an interval is an opinion.

The last month of ecommerce discussion keeps circling the same three problems. Each one is a measurement problem wearing a different costume.

Who actually sent the visitor

AI assistants now send buyers, and they send them without the identifiers every attribution method depends on. The orders arrive and get filed under whatever sat closest to the sale.

What did the agent change

An agent can rewrite a whole catalogue in an afternoon. That speed is worth having, and it removes the contrast every causal method needs, unless you spend a little of it on structure.

Why did that product sell

Studying winners is a good way to form a hypothesis and a poor way to test one. The step between those two is where most product strategy quietly goes wrong.

The rule underneath

Every answer above reduces to the same discipline. Find the contrast, or admit there is none. Read the confidence interval rather than the midpoint. Record what could not be resolved instead of estimating it.

That is what causal inference is for, and it is why last-click attribution keeps producing confident answers to questions it cannot see.

Where a read fits

For the wider set of attribution questions, see the attribution answers hub.

Frequently asked questions

  • How do I measure traffic from AI assistants?
    You can isolate the sessions that kept a referrer, which gives a floor rather than a total, and split direct by landing page depth to spot untagged arrivals. Whether that traffic is incremental needs a causal design, not a bigger referral table.
  • How do I keep AI agent changes measurable?
    One lever per measurement window, a holdout chosen before results exist and verified with a post-batch diff, a field-level changelog written at the moment of the change, and prior state stored so a negative read can be rolled back.
  • Why is a bestseller not proof of what works?
    Its sales are the joint result of concept, execution, price, images, traffic, timing and placement, and the total is not labelled. Identifying the cause needs one property varied while the others are held fixed.

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.