How to Measure Revenue After an AI Chat
Measure AI chat from reader engagement to a verified order. Separate assisted revenue, incremental lift and publisher earnings with a clear baseline.
An AI chat can help someone choose a product. To understand its value, you need to follow what happened after the answer: whether the person opened a product, reached a merchant, placed an order and kept that order.
Start with a clear definition of the result you want to measure. A conversation followed by a purchase can be useful evidence. It does not, by itself, show that the conversation caused the purchase.
Separate three questions
What happened in the experience? Measure eligible visits, conversations, useful answers and product or merchant handoffs. Keep each step's denominator visible. The share of conversations that reach a product is different from the share of all site visits that reach one.
Which orders meet your assist rule? Decide what qualifies as meaningful assistance and which observed orders can be connected to it. Document the event order, reporting window and duplicate handling. Call this assisted revenue, with the rule attached.
What did the experience add? Compare eligible groups under an appropriate experiment. People who choose to chat may already be more likely to buy. Comparing them with everyone who did not chat can describe those groups, but cannot establish incremental lift.
Write the measurement plan before the pilot
Choose the pages, audience, products and dates in scope. Record the baseline and the people responsible for the site, analytics and order data. Agree which question would make you keep, change or stop the pilot.
Define assistance around an observable action relevant to the task. Opening chat is an exposure or engagement event; it need not earn order credit. A useful recommendation followed by a verified product handoff may be a better candidate, if your configured integration records it.
Select a reporting window that fits the buying cycle. Do not choose a longer window simply because it produces a bigger number. Show how the result changes under a shorter rule, and keep unmatched journeys visible.
Verify the path to an order
Check the available events and identifiers in the actual installation. Do not assume a provider records every cart action, carries an identifier across domains or receives the merchant's order data.
For a retailer with permitted order access, reconcile qualifying events with a stable order record. Check duplicate purchases, cancellations and refunds. Define whether a report uses gross sales, net sales or another basis, and use that basis consistently.
For a publisher sending a reader to another merchant, a click is a handoff. An order, commission, payable balance and settled payment are later records. Report the stages you can verify and label the rest unknown. Do not convert all merchant clicks into sales or use a merchant's basket value as publisher revenue.
Teams using GA4 can start with Google's ecommerce collection guidance, then verify their own configured events. The GA4 collection checklist explains what to test before interpreting a report. The reconciliation guide explains how to review it against source records.
Keep attribution and incrementality separate
An attribution rule allocates credit among observed touchpoints. An experiment asks whether a change produced a different outcome. Neither becomes the other because a dashboard labels it ROI.
Where practical, assign eligible visitors to comparable experiences before engagement, keep the assignment stable and define the primary outcome and guardrails in advance. Plan sample size and duration around the expected buying cycle and actual traffic. If the evidence is too sparse, say the test is inconclusive.
Review revenue per eligible visit alongside answer quality, incorrect recommendations, site performance, reader experience and support burden. A stronger commercial result does not excuse a broken customer journey.
Make the weekly review useful
Report the scope and dates, eligible visits, engaged conversations, verified handoffs, matched orders and unmatched records. Show the revenue basis, costs and reversals separately. Keep the baseline and comparison next to the result.
End with a decision: keep the configured experience, repair a named step or stop the test. If the order join is missing, finish that measurement work before claiming a revenue improvement. If the sample is too small, preserve the result and set the next review.
Brambles.ai powers AI chat on publisher and retailer sites. Start with the product-discovery overview, then agree the content, placements, available actions and evidence needed for your pilot. Publisher teams and Brand teams should use separate outcome definitions that match their business.
Related posts
View all
How to Test AI Chat for Final-Sale Variants on Shopify
Use one product and two colors to check whether AI chat gives the right return terms before a shopper adds the item to their cart.

How to Test AI Chat for Fixed Bundles on Shopify
Compare a bundle added from AI chat with the same bundle added from its Shopify product page. Check the options, quantities, and cart grouping.

How to Test AI Chat Across Shopify Markets
Use two Shopify markets and two products to see whether AI chat recommends items shoppers can buy after they change countries.
Explore Brambles.ai
Learn more about our AI-powered agentic commerce platform, agentic shopping, and shopping assistance solutions.
Explore More Insights
Discover more articles on AI, automation, and business innovation
View All Articles