Track AI Traffic in GA4: See Your ChatGPT Referrals

2. What Changed in GA4 in May 2026

Quick Answer: Google added an AI Assistant channel to the GA4 default channel group. When the referrer matches a recognised assistant, GA4 sets the medium to ai-assistant, the campaign to (ai-assistant), and files the session under AI Assistant. Nothing needs to be switched on.

Google’s own documentation describes the channel plainly: AI Assistants is the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok. The change was reported in mid-May 2026 and reached most properties within weeks.

Three things happen at once when GA4 recognises the referrer:

• Medium becomes ai-assistant. What the channel rule matches on, so it is the value to use if you build anything custom on top.
• Campaign becomes (ai-assistant). A reserved label, the way (organic) works. Not something you set.
• Channel becomes AI Assistant. It appears in the standard acquisition reports beside Organic Search and Direct.

Two limits matter before you read any number. The channel is not backdated, so a year-on-year comparison shows a step change that is really a definition change. And it excludes Google’s own AI Overviews and AI Mode — those sit in Organic Search, since the click comes from a search result page.

3. Where to Find AI Traffic in Your GA4 Reports

Quick Answer: Open Reports, Acquisition, Traffic acquisition, and look for AI Assistant in the channel column. To see which assistant sent the visit, switch the primary dimension to Session source — chatgpt.com, gemini.google.com and copilot.microsoft.com appear separately.

Four views answer four different questions, and it is worth knowing which one to open:

• Channel view. How much of your traffic is AI at all, next to every other channel.
• Session source view. Which assistant. The mix is rarely even; one usually dominates.
• Landing pages, filtered to the channel. Which pages the assistants send people to, and so what to write more of.
• Any view with a key event applied. Whether the sessions do anything. Sessions alone prove nothing.

The landing page view is the one most people skip and the one that changes decisions. If your AI landing pages are all explainers, that is a content signal — see content formats chatbots prefer. If they are pricing and comparison pages, you are already getting commercial intent, and the prompts buyers actually type is what to research next.

One warning while you track AI traffic in GA4 at small volumes: a few dozen sessions a month makes percentages jumpy. Use a 90-day window and compare equal periods.

4. What the AI Assistant Channel Still Misses

Quick Answer: The channel only works when a referrer arrives. Links opened inside a chatbot’s mobile app, copied into a browser, or passed through a privacy setting arrive with no referrer at all, so GA4 files them under Direct. Assistants outside Google’s list also fall through.

This decides how much you trust the number. GA4 classifies on the referrer header: no header, no classification. Someone who reads a ChatGPT answer on their phone and taps your link in the in-app browser is, as far as GA4 knows, a person who typed your address from memory.

The AI Assistant channel is a floor, not a total. The real number is larger and nobody can tell you by how much.

Three specific leaks account for most of it:

• In-app browsers on mobile. The biggest leak by far, and the one you cannot fix from your side.
• Assistants Google has not listed. Perplexity is the one Malaysian clients ask about most, and it commonly arrives as ordinary Referral.
• Copy-paste and shared links. Someone sends your URL to a colleague on WhatsApp. That visit is Direct forever.

If your Direct channel has been climbing without an obvious cause, this is now a candidate. Our guide to too much direct traffic in GA4 covers the others. The honest framing is that the channel is a confirmed minimum and the trend matters more than the absolute figure, the point we also make in whether ChatGPT visitors actually convert.

5. How to Build a Custom AI Channel Group

Quick Answer: Build one custom channel group that catches both the native medium and the assistants Google misses. Create it in Admin, add an AI rule matching medium ai-assistant or source containing perplexity, then move that rule above Referral so it is evaluated first.

You only need this if the assistants outside Google’s list matter to you. If your Referral report shows no perplexity or other AI sources, the native channel is enough.

How to set up a custom AI channel group in GA4

The job takes about ten minutes and destroys nothing, because channel groups are applied when you view a report, so the change is retroactive in your reports and reversible.

1. Check what is arriving. Open Reports, Acquisition, Traffic acquisition, set the dimension to Session source and the range to 90 days, then note every AI hostname sitting in Referral.
2. Open the channel group editor. Admin, then Data display, then Channel groups. Create a new group from a copy of the default so every existing definition is kept.
3. Add one channel called AI. Two conditions joined with OR: session medium exactly matches ai-assistant, and session source contains the hostnames from step one.
4. Move the AI rule above Referral. GA4 reads rules top to bottom and stops at the first match. Below Referral, the rule never fires.
5. Check it the next day. Open Traffic acquisition, switch the channel group selector to your new group, and confirm the AI row is larger than the native one.

Keep the native group as your default view and treat the custom one as the wider lens. Two views you understand beat one that merges both definitions. Across many properties, the governance side sits in our guide to scaling enterprise SEO in Malaysia.

6. How Much Traffic AI Assistants Actually Send

Quick Answer: Across ZenWeb-managed Malaysian SME accounts, AI Assistant sessions run between roughly 1% and 5% of all sessions, with professional services and software highest and retail lowest. Nobody in the sample is getting the majority of their traffic from chatbots.

The pattern is research behaviour, not industry glamour. Where buyers compare suppliers and work out a budget before enquiring, the assistants get used. Where they decide in the moment, they do not, which is why a B2B site sees roughly four times the share a restaurant sees.

So the small percentages are not the whole story. A research-stage visitor is worth more than an idle one. The next three sections test that.

7. Where AI Sessions Get Misfiled

Quick Answer: In ZenWeb-managed accounts, a quarter to a half of identifiable AI sessions land outside the AI Assistant channel. Gemini classifies most cleanly, ChatGPT loses a large share to Direct on mobile, and Perplexity is usually filed as ordinary Referral.

Read the Direct column as the mobile column. The assistants with heaviest phone use lose the most, because the in-app browser drops the referrer before GA4 sees it. That is platform behaviour, not a tagging mistake on your site.

The Perplexity row is the argument for the custom group in section five. Left alone, that traffic sits in Referral beside directory listings and nobody reading the report knows it is there, which matters most if you depend on being recommended locally. See how chatbots pick local businesses.

8. Does AI Traffic Actually Convert?

Quick Answer: In the ZenWeb sample, AI Assistant sessions produce enquiries at a higher rate than organic search, paid search and social. The volume is small, but the intent is late-stage — people arrive having already had their basic questions answered elsewhere.

The last two columns tell opposite stories on purpose. AI Assistant is the smallest channel here and the strongest per session, which is the honest case for the work. It will not replace organic search this year, and it is not noise either.

One caution before that rate reaches a board meeting. Small denominators exaggerate rates, so 200 sessions and 8 enquiries looks spectacular beside 20,000 sessions. Report the enquiry count alongside the rate. That is the discipline we argue for in marketing attribution for business owners.

9. How Fast the Number Is Moving

Quick Answer: AI sessions in ZenWeb-managed accounts have grown from a rounding error in early 2024 to a few percent of sessions in 2026, and the enquiry share has grown faster than the session share throughout. Almost every account now sees some AI traffic.

The gap between the first two rows is the finding. AI has supplied about twice the share of enquiries as it does of sessions, and that ratio held while both numbers grew. A channel that punches above its weight consistently earns a line in the report.

These figures combine the native channel with the sources GA4 misfiles, so they run higher than the AI Assistant channel alone. For the visibility side, getting named in AI answers is the input, and what LLMs actually reward explains the mechanics.

10. What to Put in Your Monthly Report

Quick Answer: Four lines are enough — AI sessions, AI enquiries, the top three landing pages, and the source split. Add one sentence on what you changed. More than that gets skimmed and starts arguments about definitions rather than decisions.

The temptation with a new channel is to build it a dashboard. Resist. A four-line block inside the report you already send does more, because it sits beside channels the reader trusts.

• Sessions and enquiries as counts. Percentages alone hide how small the base is.
• Top three AI landing pages. The only line that tells you what to publish next month.
• Source split. One assistant usually dominates; when that shifts, how you are cited changed.
• One sentence of context. What you published or fixed, so next month’s movement has a cause.

Pair it with a monthly prompt check: the same ten buyer questions, recording who gets named. When you track AI traffic in GA4 you see people who already clicked; the prompt check shows the answers where you were never mentioned. That gap is where the work is, which is the loop behind generative engine optimisation services and the expertise signals machines can verify. If you sell products, product listings in AI search is the equivalent input; choosing an AI SEO agency in Malaysia covers what to demand from whoever runs it.

11. Conclusion

Quick Answer: To track AI traffic in GA4 today, open the AI Assistant channel first, treat it as a minimum rather than a total, add a custom group only if assistants outside Google’s list matter, and judge the channel on enquiries rather than sessions.

The setup problem is largely solved. What is left is a reading problem. You need to know the number under-counts, knowing why, and knowing which view to open when someone asks whether any of this is working.

Small, growing, above-average intent is a fair summary for a Malaysian SME in 2026. Worth four lines a month and a content decision or two; not yet worth restructuring a marketing plan around. For the wider comparison, AI SEO versus traditional SEO sets out what changes, and our earlier guide to tracking AI search traffic in GA4 covers the manual methods still useful when the native channel falls short.

12. Frequently Asked Questions

1. Do I still need a regex to track AI traffic in GA4?

Not for the common assistants. Since May 2026 GA4 files recognised chatbot referrals into an AI Assistant channel automatically. You only need a custom channel group if assistants outside Google’s published examples send meaningful traffic — usually Perplexity.

2. Why does ChatGPT traffic show up as Direct?

Because no referrer arrived. Links opened inside a chatbot’s mobile app usually strip the referrer header, and URLs copied out of an answer carry nothing. GA4 has no signal to classify with, so the session goes to Direct. Nothing on your site causes it and nothing on your site fixes it.

3. Does the AI Assistant channel include Google AI Overviews?

No. Google’s documentation states the channel excludes AI Overviews and AI Mode, because those clicks originate on a search results page. They count as Organic Search, so any gain inside AI Overviews shows up there rather than in the AI channel.

4. Is AI traffic worth chasing for a small Malaysian business?

It depends whether your buyers research before they enquire. In ZenWeb’s client sample, professional services and software see several times the AI share retail and F&B see. The sessions are few but convert well, so the work belongs inside ordinary SEO rather than in a separate budget line.

5. Will my historical AI traffic be reclassified?

No. The channel is not retroactive, so earlier sessions stay in Referral or Direct where they landed. Comparing this year to last will show a jump that is a definition change, not growth. Note the rollout date on any chart that crosses it.