What AI referral data can tell you about sales
AI referral reports can show recorded visits and attributed orders. Estimating additional sales requires another step: determining what would likely have happened without the intervention.
Separate those questions before reporting the effect of a product-content change.
Three claims can use the same orders and mean different things
Imagine a fictional analytics report that attributes 12 orders to visits carrying an AI-service referrer. “Twelve orders were attributed to that channel under this model” describes the report. “Twelve customers discovered us through AI” adds a claim about the earlier journey. “AI created twelve additional orders” adds a causal claim about what would have happened without the channel.
The first observation cannot establish the other two on its own. A returning customer may already know the shop. A different attribution model may assign the same order elsewhere. Missing referral information can also leave part of the journey unclassified.
| Statement | What would support it |
|---|---|
| Visits were recorded with a particular referrer | The captured traffic records and channel rule |
| Orders were attributed to that channel | The attribution model, window and order reconciliation |
| Those orders were additional | A comparison designed to estimate the counterfactual |
The example is synthetic. Its purpose is to separate questions before they become a single headline in a sales presentation.
Record the definition before comparing periods
Write down which referrers or campaign parameters enter the channel, which orders count and which attribution window is used. Save that definition with the reporting period. If a channel rule changes between two exports, a difference in totals may partly reflect reclassification.
Then reconcile the order metric. Gross order count, paid orders and revenue after cancellations or returns answer different commercial questions. Use the measure appropriate to the decision and name it explicitly. A traffic report alone does not resolve those accounting choices.
Google's documentation on AI features in Search states that appearances in those features are included in overall Search Console Web performance. Do not manufacture a separate AI Overviews traffic total from a dataset that does not isolate it. The origin of a measurement determines what the report can say.
Design a comparison around the decision you control
If you want to evaluate a catalogue improvement, first define what changed and which outcomes it could plausibly affect. Better product information may coincide with a promotion, a stock recovery or a seasonal change. A before-and-after chart cannot separate these explanations simply by adding the date of the content update.
Where a controlled comparison is feasible, define the treatment, comparison group and outcome before reading the result. Where it is not, keep the analysis descriptive and list material changes that occurred during the period. That still helps a merchant decide where to investigate without converting uncertainty into a fabricated return-on-investment figure.
For routine reporting, a compact note beside the chart is often enough: the channel definition, the attribution rule, the order measure and any known coverage gaps. Those details make the number reusable. Without them, the next person may interpret an attributed order as a newly acquired customer or an incremental sale.
Keep measurement systems distinct
Search Console and store analytics observe different parts of a journey. Google's AI-feature documentation explains how activity from its AI features is included in the overall Web search reporting.
That does not create a complete separate count of all assistant-driven purchases. Do not merge differently defined reports into one total without explaining their scopes.
Use the e-commerce measurement plan, available in French, to define the decision and comparison before the intervention starts.
Decide what can be learned now
If attribution is available but causal evidence is weak, you can still inspect the landing experience, product questions and observed conversion path. These findings can guide improvements without claiming incremental revenue.
If the business needs a causal estimate, design that measurement before the next intervention. Define the comparison, primary outcome and duration according to the actual traffic and operational constraints.
Do not invent an experiment after seeing a favourable result and describe it as a planned test.
