How to Track AI-Referred Ecommerce Sales: Traffic, Orders and Agent-Placed Purchases
How to measure ecommerce sales from ChatGPT, Gemini and AI Overviews: GA4 channels, platform AI orders, surveys and comparisons with organic.
Quick answer
AI-driven ecommerce sales arrive through three routes, and each needs a different measurement. AI-referred visits (a shopper clicks from ChatGPT, Gemini, Copilot or Perplexity) appear in GA4's AI Assistant channel with their revenue. AI search on Google (AI Overviews and AI Mode) is counted inside Organic Search, with impressions in Search Console's generative AI report. Orders placed inside assistants may never touch your website, so they come from your commerce platform's sales channel or order source data. Combine all three with a post-purchase survey, then compare conversion, revenue per visit, average order value and repeat rate against organic search rather than session counts.
Three routes, three data sources
| Route | Example | Where to measure | Blind spot |
|---|---|---|---|
| AI-referred visit | Shopper clicks a product link in ChatGPT | GA4 AI Assistant channel; utm_source=chatgpt.com | App visits without referrer land in Direct |
| Google AI features | Click from an AI Overview or AI Mode | Search Console generative AI report (impressions); GA4 Organic Search | No clean split of AI Overview clicks in GA4 |
| In-assistant order | Checkout completed in an assistant via the platform's agentic channel | Commerce platform orders by sales channel or source | No website session; no on-site behaviour |
| Influenced but unattributed | Shopper researched in an assistant, later typed your URL | Post-purchase survey | Self-reported; sample only |
Set up website measurement
GA4's default channel group has included an AI Assistant channel since May 2026, covering referrals from sources such as ChatGPT, Gemini, DeepSeek, Copilot and Grok; Google states it excludes AI Overviews and AI Mode, which remain in Organic Search. Ecommerce purchase events in those sessions attribute revenue to the channel automatically. Check that your purchase event fires reliably, including on accelerated checkouts, and that channel rules from older custom setups do not override the default. The general setup, including Search Console and server logs, is in our guide to measuring AI search traffic.
- Confirm the AI Assistant row appears in Traffic acquisition with purchases and revenue
- Add session source to split ChatGPT, Gemini, Copilot and Perplexity
- Build an exploration of AI Assistant sessions by landing page and product
- Compare with Organic Search on conversion rate, revenue per session and average order value
- Annotate dates of feed, product data and channel changes
Track orders placed through assistants
When assistants complete or hand off checkout through commerce platforms, the order is created in your store without a normal website session. Your platform's order data is the source of truth. Shopify's Help Center says orders from AI channels in its Agentic Storefronts appear in the admin with channel or referrer attribution, and it provides sales, orders, sessions and conversion reports for those channels. Note that for ChatGPT, Shopify describes customers completing purchase on your own online store checkout inside ChatGPT's in-app browser, so those orders also leave a web session. On other platforms, check how protocol-based orders (UCP, ACP) are labelled, and ask your platform or payment provider how they appear in exports.
Join platform order data with web analytics in a simple monthly report so leadership sees one number for AI-driven revenue, with the routes broken out underneath.
Pro tip
Add an order tag or note attribute for agent-placed orders if your platform does not label them, so customer service and returns teams can recognize them too.
What to compare with organic traffic
AI channels are still smaller than organic search for most stores, so judge them on quality and trend, not volume.
| Metric | Why it matters |
|---|---|
| Conversion rate | AI visitors often arrive later in the decision |
| Revenue per session | Combines conversion and order value |
| Average order value | Assistants may favour certain price points or bundles |
| Landing page mix | Shows which products assistants recommend |
| Return rate | Tests whether recommendations matched needs |
| Repeat purchase rate (cohort) | Whether AI-acquired customers stay |
| Share of total revenue | The channel's real weight, month by month |
Benchmarks: useful direction, not targets
Published aggregates suggest AI-referred shoppers are valuable. Adobe Analytics reported in August 2026 that AI-referral visits to US retail sites converted 60 percent better than non-AI traffic and generated 53 percent more revenue per visit, with time on site up and bounce rates down. These are averages across large retailers; do not set targets from them. Measure your own baseline for three months, then track change.
Want AI channels in your ecommerce reporting?
ZSpace Labs sets up GA4, platform order attribution and combined AI revenue reports for Shopify and custom stores. See our CRO and analytics audit.
Fill the gaps with a post-purchase survey
Many AI-influenced purchases leave no trail: the shopper researched in an assistant on their phone, then typed your URL on a laptop. A one-question post-purchase survey ("How did you first hear about us?" with AI assistants as an option, or a follow-up asking which tool) captures part of that influence. Treat the results as directional and track the trend.
Turning the data into decisions
- Products with AI landings but low conversion: check page facts, stock and delivery visibility
- High AI impressions in Search Console, few clicks: give visitors a reason to click (tools, detail, offers)
- Strong in-assistant orders, weak site visits: invest in feed quality and post-purchase experience
- High return rate on AI-acquired orders: improve sizing, compatibility and specification data
- Rising AI share: prioritize product data completeness in the categories assistants recommend
Direct AI Traffic vs AI-Assisted Journeys
Keep two ideas separate in reporting. Direct AI traffic is measurable: sessions with an AI referrer or tag, orders attributed to an AI sales channel. AI-assisted journeys are broader and mostly invisible: a shopper researches in an assistant, later searches your brand or types your URL, and converts as direct or branded organic traffic. Analytics will undercount the second, and no tool currently measures it precisely.
Report the first as fact and estimate the second with triangulation: post-purchase surveys, trends in branded search and direct traffic after AI visibility improves, and product-level patterns (products assistants recommend often tend to show rising direct sales). Present AI-assisted influence as a range with its method stated, never as a precise attributed number. For what happens to those orders operationally, see orders placed by AI agents.
| Direct AI traffic | AI-assisted journeys | |
|---|---|---|
| Definition | Visit or order with an AI referrer, tag or channel | AI influenced the decision; visit arrives via another channel |
| Measured by | GA4 AI Assistant channel, utm tags, platform order channel | Surveys, branded and direct trends, product patterns |
| Confidence | High | Directional only |
| How to report | Exact numbers | Ranges with method stated |
Conclusion
AI-driven ecommerce revenue comes through referred visits, Google's AI features and orders placed inside assistants, and no single tool sees all three. Use GA4's AI Assistant channel for visits, Search Console for Google's AI features, platform sales channel data for agent-placed orders and a survey for influence, then compare quality metrics with organic search. For what to change once you can see the data, read how AI agents change the ecommerce funnel and ecommerce attribution.
Common questions.
GA4's default channel group includes an AI Assistant channel for visits from sources such as ChatGPT, Gemini, Copilot and others, and ChatGPT tags links with utm_source=chatgpt.com. Purchases in those sessions appear as AI Assistant revenue. Orders completed inside an assistant may not create a website session at all.