To track AI traffic in GA4, start with the AI Assistant channel Google added on 13 May 2026. GA4 now files visits from recognised AI assistants there by itself, and the Traffic acquisition report shows them as a row of their own, with the tool behind each visit one click away.
Clicks from Google’s AI Overviews and AI Mode are not in that row. It is the easiest part of measuring where a company shows up in AI answers, and the least complete: some assistants land elsewhere, some visits carry no source, and in B2B what matters is the pipeline behind them.
Where GA4 files AI traffic now
Google’s release note says GA4 sets the medium to ai-assistant and the campaign to (ai-assistant) when a visit’s referrer matches its list of AI assistants, and files the visit under the new channel. With the medium changed, those visits no longer show under Referral. To read them:
- In Reports, open Acquisition, then Traffic acquisition, which lists sessions by channel.
- Find the AI Assistant row and add Session source as a secondary dimension to see each tool.
- Swap in Landing page to see where each tool sends people, and read the key events column for leads.
Google’s channel definitions and its release note name the tools as examples. Where each one lands:
| Tool | Named by | Where GA4 files it |
|---|---|---|
| ChatGPT and Gemini | The channel definitions and the release note | AI Assistant |
| Claude | The release note | AI Assistant |
| Copilot, Deepseek and Grok | The channel definitions | AI Assistant |
| Perplexity | Neither; only Google’s custom channel example | Check Referral |
| Google AI Overviews and AI Mode | The channel definitions | Organic Search |
| Any click with no referrer | Google’s (direct) / (none) page | Direct |
Google describes the channel as covering “sources like” these tools and publishes no full list. The source categories file on its channel page covers search, social, shopping and video sites, with no AI category, so treat the table as a starting point to check against your own data.
Find the AI visits the channel misses
Assistants Google does not recognise
Switch the table to Session source / medium and filter for Referral. Any AI address still listed there is an assistant GA4 has not classified, and a reason for the custom channel below. Look for perplexity.ai first, since Google names it in neither list.
Tagged links with a missing medium
Google says missing UTM parameters leave (not set) values in reports, so a link from an AI tool tagged with a source and nothing else can surface with a (not set) medium. Check the Unassigned channel for AI addresses.
Visits with no source
Google defines (direct) / (none) as traffic without a clear referral source. A buyer who copies your address out of an answer, or types your name in after reading one, lands there. Read Direct as a trend beside branded searches and the other traces of a buyer who never clicked.
Months before 13 May 2026
Older AI visits sit in Referral under their own source names. Google does not say whether the new channel reclassifies them, but it says custom channel groups apply to past reports, and its Source group dimension, added on 11 June 2026, is filled in retroactively and groups ChatGPT and Perplexity.
Build your own AI channel, and fix Google’s example
A custom channel group is worth building when an assistant you care about sits in Referral. It can cover assistants only: AI Overviews and AI Mode arrive as google / organic, like every other Google click, so no rule can pull them out.
- In Admin, under Data display, open Channel groups and create a new group. It starts as a copy of the default, so every other channel stays as it is.
- Add a channel named AI assistants with two conditions joined by OR: Default channel group exactly matches AI Assistant, or Source matches regex, with your own list.
- Google files a visit under the first channel it matches, in the order listed, so move AI assistants above Referral, save, and pick the group in Traffic acquisition.
Google’s help page on custom channel groups offers this example pattern for the source condition:
^.*ai|.*\.openai.*|.*chatgpt.*|.*gemini.*|.*gpt.*|.*copilot.*|.*perplexity.*|.*google.*bard.*|.*bard.*google.*|.*bard.*|.*.*gemini.*google.*$
Google’s regex help says Analytics matches the full value and is case sensitive by default. Under that rule the first branch, ^.*ai, catches any source ending in “ai”, so a referral from any .ai company, a software vendor or a partner directory, counts as an AI assistant.
The gpt and copilot branches catch any site with those letters in its name. And two assistants Google’s own channel names, Deepseek and Grok, slip through on their usual addresses, chat.deepseek.com and grok.com. Matching part of the value instead would only widen the net.
A narrower pattern lists exact hostnames and allows a subdomain in front of each:
(.*\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|chat\.deepseek\.com|grok\.com|meta\.ai)
Build your own list the same way, from the source values your property actually records, and add to it when a new assistant starts sending visits. Google’s note on its example says the same: update the pattern when the assistants you want to measure change.
How to track AI Overview and AI Mode traffic
GA4 cannot separate them. Google’s channel definitions put AI Overviews and AI Mode in Organic Search, and Google’s referrer carries no search terms, so a click from either arrives as google / organic beside every other Google click.
Search Console holds the other half. Its generative AI performance report, launched in June 2026 and open to every site since 31 August, counts impressions in AI Overviews and AI Mode by page, country, device and date. It shows no clicks and no queries.
Clicks sit in the ordinary Performance report. A click on a link in AI Mode or an AI Overview counts as a click there, under the Web search type, mixed in with every other Google click. To set the two tools side by side:
- Export the pages with AI impressions from Search Console, month by month.
- In GA4, open the Landing page report filtered to google / organic, the comparison Google itself suggests for the two tools.
- Compare those pages’ sessions, engaged sessions and key events with pages that show no AI impressions.
- Read the result as a direction, not a count: Google says the two tools’ data “won’t match completely”.
Copilot and Bing’s AI answers
Copilot’s clicks land in the AI Assistant channel. Bing Webmaster Tools’ AI Performance report counts how often Copilot and Bing’s AI summaries cite your pages, and Microsoft says its Citation Share does not “represent traffic share”, so read citations beside visits, never in place of them.
Carry AI visits into the CRM
In B2B, one session is rarely the sale. A buyer clicks through from an assistant, leaves, comes back weeks later by typing your name, and fills in the form. In GA4’s session reports that form sits under Direct, and the first AI touch is gone.
- Capture the first visit: the landing page address with its query string, the referrer, and the source and medium, kept in a first-party cookie or browser storage.
- Pass them into hidden fields on every form, and write them to the contact as original source fields that are never overwritten.
- Store the buyer’s own answer to how they heard of you beside them, and ask again on the first call.
- Report leads, opportunities and pipeline value by first source each month, with AI next to Organic Search.
The captured source and the buyer’s answer will not always agree, and the disagreement is informative:
| Captured source | Buyer says | What it means |
|---|---|---|
| AI assistant | AI | Confirmed |
| Direct | AI | An AI visit analytics missed; count it |
| AI assistant | Something else | The assistant was a later step, not the first |
Hidden fields only pay off when the source survives all the way to the deal, which is the work of tying each lead’s first source to the opportunity it became.
A monthly AI traffic sheet
Compare each line with your own last month, not with someone else’s benchmark:
| Number | Where it comes from |
|---|---|
| AI Assistant sessions | Traffic acquisition |
| AI sessions outside the channel | Referral and Unassigned rows that match your list |
| AI share of sessions | AI sessions divided by all sessions |
| AI key event rate | Key events from AI sessions divided by AI sessions, beside Organic Search |
| Leads with an AI source | The CRM, split into captured and self-reported |
| Pipeline from those leads | The CRM’s opportunity value |
| AI impressions in Google | Search Console’s generative AI report |
| Citations in Copilot and Bing | Bing’s AI Performance report |
Analytics sees only the buyers who clicked. Pair the sheet with a monthly check of whether ChatGPT names you for your buyers’ questions, the part of AI visibility that never reaches a report.
● About the author
Hamza Hashim is the marketing strategist at Katama. He owns the channel mix and the order it gets built in: what ships first, what waits for evidence, and what gets stopped when the evidence says stop. Meet the team.