Measurement When the Referrer Disappears

Why this module exists

Two claims are made about AI-referred traffic, both by serious people, and they cannot both be casually true: that it is a rounding error, and that it is the fastest-growing channel in commerce.

They are reconcilable. AI-referred traffic is small in absolute terms for most retailers, is growing very fast, and is systematically undercounted — because a large share of it arrives with no usable referrer and lands in "direct."

This module builds a measurement you can defend. Not a perfect one; a defensible one, with its error bars stated. That distinction is what gets a number into a board pack instead of an argument.

6.1 Why the number is wrong

Four mechanisms, each independent, all pushing the same direction.

Referrers are stripped or absent. Answers rendered in an app, a native client or behind a redirect frequently arrive with no referrer. The visit is real; the attribution is gone. It becomes "direct."

The influence and the visit are separated in time. A shopper asks an engine on Tuesday, reads the answer, and searches your brand on Thursday. The engine created the demand; brand search takes the credit. This is the largest effect and it is entirely invisible to last-click.

Some answers end the journey. The shopper gets what they needed — your delivery time, your returns window — and never visits. This is unmeasurable from your side by construction. Its existence is why session counts understate influence.

Agents do not look like sessions. A machine fetching a feed, or transacting through a protocol, generates no visit at all. It may generate an order.

Four leaks between influence and the number in your dashboard. Only the first is a tagging problem.

The consequence is not "analytics is broken." It is narrower and more useful: your analytics reports a floor. Say so, and the number becomes usable.

6.2 Build a floor and a ceiling

The instinct is to find the number. Resist it — a single figure in this area is false precision, and the first person to poke it wins the meeting.

The floor: what you can see. Sessions and revenue from identifiable AI referrers, cleaned up as far as the mechanisms above allow. Improve it with three cheap moves:

Maintain an explicit AI-source list in your analytics and update it monthly; the default channel groupings lag badly.
Where an engine passes a parameter, capture it. Where it does not, note the absence rather than guessing.
Segment your "direct" traffic by landing page. Direct traffic that lands on deep product and comparison pages, rather than the homepage, has a different origin than genuine type-ins.

The ceiling: what plausibly exists. Three triangulation methods, each weak alone and useful together:

Method	What it catches	Weakness
Post-purchase survey — "where did you first hear about us / how did you research this?"	Time-separated influence, and answers that ended elsewhere	Self-report bias; needs volume
Brand-search lift modelling — model brand-query volume against your visibility work and known drivers	Demand pushed downstream by generative discovery	Confounded by campaigns and seasonality; needs a clean period
Direct-traffic decomposition — the trend in deep-landing direct traffic	Referrer-stripped visits	Confounded by app and email traffic

Report both bounds, with the method attached. "Between 2.6% and roughly 7% of revenue is AI-influenced; the lower bound is measured, the upper is triangulated from a post-purchase survey with n=1,400 and should be treated as indicative." That sentence survives scrutiny. A single number does not.

6.3 The measurements that survive

Some metrics degrade as attribution degrades. Some do not. Weight your reporting toward the second group.

Robust:

Mention rate and owned-citation share — the Module 3 metrics, in the exact senses defined there. Measured directly, independent of your analytics, and the leading indicators for everything else. Report both; the pair tells you whether engines are talking about you and whether they are using your own pages to do it.
Brand search volume — the demand that generative discovery pushes downstream shows up here. Watch the trend against category and against your own spend.
Assisted-conversion shape — whether journeys are getting shorter and more decisive; AI-influenced shoppers arrive more informed.
Feed-surface impressions — where a platform reports them, this is machine-side demand that never becomes a session.

Fragile:

Last-click channel revenue for AI sources.
Session counts from AI referrers.
Anything that requires a referrer to be intact.

6.4 Naming the counterfactual

Every AI measurement conversation eventually reaches the honest question: would that revenue have arrived anyway?

Frequently, yes. A shopper who asks an engine and then buys from you might have found you through search. Claiming the full value of those orders is the fastest way to lose the argument permanently.

Three defensible positions, in ascending order of strength:

Incremental visibility. Measure citation share before and after remediation, and report the change in mention rate as the outcome. Honest, and it is what you actually influenced.
Held-out categories. Remediate one product category and not a comparable one. Compare demand trends. Not perfectly clean, and far better than nothing.
Pre-registered claim. State before the work what you expect to move, by how much, by when, and what result would mean it failed. Then report it either way.

The third is what turns a growth team into one the finance function believes on the next request.

Marlowe & Finch — the number that got approved

The first attempt reported "AI traffic: 2.6% of revenue, up 340% year over year." The finance director's response: "340% of a rounding error, and half of those people would have found us anyway." The meeting ended there.

The second attempt reported this:

AI-influenced demand, Q2 2026. Measured floor 2.6% of revenue. Triangulated ceiling 6–8%, from a post-purchase survey (n=1,410) in which 9.1% of buyers said they researched the purchase with an AI assistant. Leading indicators on a fixed 40-prompt set, same engines, same method: mention rate 14/40 → 23/40; owned-citation share 28% → 48%; factual errors 6 → 1.

Counterfactual. Hallway rugs were remediated in April and floor lamps deliberately were not. Over the following ten weeks, non-brand demand for rugs grew 11 points faster than for lamps. Category seasonality is not identical, so treat this as indicative rather than causal.

The claim we will be judged on. By 31 December: mention rate at or above 30/40, owned-citation share at or above 60%, and AI-identifiable revenue share above 5%. Below 24/40 mention rate we stop the remediation programme and report why — that result would say the constraint is off-site, and the budget should move accordingly.

It was approved, and the reason is worth naming: the second version tells the finance director where it is weak before he finds out.

6.5 What to instrument now

Six things, none of which takes long, all of which are painful to backfill:

A maintained AI-source list in your analytics, reviewed monthly.
A post-purchase survey question on research method, running continuously so you have a trend rather than a snapshot.
Deep-landing direct traffic as a standing segment.
The Module 3 prompt set on a fixed schedule, same engines, same recorder, recording all three metrics separately.
Agent and crawler request logging, separated from human traffic at the edge.
Order-source tagging for protocol orders before you have any, so the first one is already countable.

Exercise — Build the model

Time: 90 minutes. Produces the artefact for this module.

Compute your floor from analytics, and write down what you know it excludes.
Pick one ceiling method you can start this month, and start it.
Choose your leading indicators — mention rate and owned-citation share, reported separately, unless you have something better.
Design one counterfactual you can actually hold: a held-out category, a held-out market, or a pre-registered claim.
Write the board paragraph in the form used in the case above: floor, ceiling with method and n, leading indicator, counterfactual, and the claim you will be judged on with its failure threshold.
Take it to your finance business partner before the board, and note which sentence they attack. That sentence is your next month's work.

Self-check

Name the four mechanisms that make analytics undercount AI-influenced demand. Which is largest, and which is unmeasurable in principle?
Why is a floor-and-ceiling more persuasive than a single figure?
Which metrics in your current reporting are fragile to referrer loss, and what would you promote in their place?
What is the strongest counterfactual you could actually run next quarter?
What failure threshold would you be willing to put in writing today?