How to Read GA4’s AI Assistant Channel Without Fooling Your Ecommerce P&L

How to read the row

• Sessions in AI Assistant: User clicked a link from a recognised assistant and the referrer survived.
• Revenue / purchases on that channel: Sales with last-click (or your selected model) credit to that AI session.
• Tiny AI Assistant volume: Either low AI discovery or discovery that never left a referrer.
• Flat AI Assistant, rising Direct / branded search: Possible “saw you in AI, came back later” behaviour — not proven by GA4 alone.

Caveat: Industry reporting (not Google’s release note) consistently notes that some assistant / in-app flows strip referrers. Those visits land in Direct. No channel rule can invent a source the browser never sent.

Director checklist (15–20 minutes with your analyst)

Ask for a one-pager covering the last 28 days vs the prior 28:

1. Traffic acquisition → Session default channel group — volume, engagement rate, and conversion rate for AI Assistant vs Organic Search, Direct, Paid Search.
2. Source / medium drill-down — which assistants appear (e.g. ChatGPT, Gemini, Claude); flag anything still sitting in Referral that looks AI-related.
3. Landing pages — top AI Assistant landers: product, category, or blog? That tells you whether AI is feeding the catalogue or content.
4. Purchase reconciliation — AI Assistant purchase count and revenue vs Shopify (or OMS) for the same period. Expect a gap; watch for step changes.
5. Branded search trend — Search Console branded queries over the same window. Rising brand demand with flat AI Assistant can still be AI-influenced discovery you cannot last-click.

Questions for Monday stand-up

1. Do we have the native AI Assistant channel, and has anyone eyeballed it this month?
2. Are we reporting AI Assistant as “all AI traffic” in any board or agency pack?
3. Which landing pages does AI Assistant actually send, and do they convert?
4. Are we still relying on last-click alone to decide whether AI content “works”?
5. For links we control (feeds, partner placements), are we using UTMs so referrer loss does not bury the source in Direct?

What not to do

• Do not declare AI discovery a failure because AI Assistant is small — you may be looking at the floor.
• Do not reallocate half the paid budget based on one channel row without Shopify reconciliation and branded-search context.
• Do not assume Google’s own AI shopping / answer surfaces all appear under AI Assistant — check Organic Search and Ads separately.
• Do not invent assistant names for Direct sessions with no source signal.

Final thoughts

#3/100 — The AI Assistant channel is a floor, not the full AI discovery story.

GA4’s native AI Assistant measurement (from May 2026) is a real step forward for ecommerce leaders who need a clean, official place to look. Use it. Just do not let it become the only story you tell the board. Pair it with landing-page quality, purchase reconciliation, and branded demand — that is how you protect margin while the industry argues about “AI attribution.” Need a clear read on how AI Assistant, Direct, and Organic Search are shaping your ecommerce numbers? Email info@taggurus.co.uk or book a meeting today to discuss.

---

FAQ

Q: Do we need a custom channel group for AI traffic?
A: Not for Google’s recognised assistants — the Default Channel Group includes AI Assistant. A custom group can still help catch edge domains or tighten naming for your own reporting pack.

Q: Is AI Assistant the same as AI Mode / AI Overviews traffic?
A: No. Google's release note is about traffic from popular AI assistants (chatbots). Google's own AI search surfaces are typically analysed with organic / Search behaviour, not assumed to sit in AI Assistant.

Q: Where is the official announcement?
A: What’s new in Google Analytics — 13 May 2026, New AI Assistant traffic measurement.