How to measure AI search traffic in Google Analytics 4 and Search Console: ChatGPT, Perplexity, Gemini, AI Overviews and AI Mode

Two kinds of AI traffic, two places to look

The confusion in most reports comes from mixing two things. Google's own AI features, AI Overviews and AI Mode, sit inside Google Search, so a click from them is a Google organic click: it appears in Search Console, and GA4's default channel definitions place it in Organic Search, which Google defines as arriving "via non-ad links in organic-search results, including Google's AI Overviews and AI Mode".

Standalone assistants are different. When someone clicks a link in ChatGPT, the Gemini app, Claude, Microsoft Copilot or Perplexity, the browser usually sends a referrer such as chatgpt.com, and GA4 sees a referral. Search Console never sees these visits, because they did not come from Google Search. GA4's AI Assistant channel is defined as traffic "from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok" and explicitly "excludes Google's AI Overviews and AI Mode".

So the rule of thumb for an Omani business is: Search Console for Google's AI features, GA4 for everything else, and GA4 for conversions from both.

GA4's AI Assistant channel

On 13 May 2026, Google's Analytics release notes announced "New AI Assistant traffic measurement": "You can now identify how users are discovering your site through chatbots like ChatGPT, Gemini, and Claude" through a new AI Assistant channel in the default channel group. The mechanics, from the same note and the channel definitions page:

• When the referrer matches a recognised AI assistant, GA4 automatically sets the medium to ai-assistant and the campaign name to (ai-assistant).
• The AI Assistant channel rule is simply: medium exactly matches ai-assistant. You can also tag your own links with utm_medium=ai-assistant to force traffic into the channel, for example links placed in a custom GPT.
• The channel appears wherever the default channel group does: the Acquisition reports, explorations and as a dimension in custom reports.
• A further release on 11 June 2026 added Source Group, with built-in grouping for sources such as ChatGPT (OpenAI) and Perplexity, so you can see which assistant sent the visits without maintaining a regex.
• Google does not publish the full referrer list, so check the Session source dimension for the ai-assistant medium in your own property to see which assistants are recognised, and treat a new assistant appearing under Referral as a sign the list has not caught up.

Build your own channel with a custom channel group

If you want to include an assistant GA4 does not yet recognise, split assistants into separate channels, or keep AI referrals visible in a property that predates the change, use a custom channel group. Google's own help page uses an AI assistant channel as its worked example. The limits are two custom groups per standard property (five for Analytics 360), up to 50 channels each, and you need the Editor role on the property.

What Search Console shows for AI Overviews and AI Mode

Google's AI features documentation says sites appearing in AI Overviews and AI Mode are "included in the overall search traffic in Search Console and reported on in the Performance report", within the Web search type. There is no filter in the main Performance report that isolates them. Google's page on how impressions, position and clicks are counted sets out the rules:

• A click on a link to an external page in an AI Overview or in AI Mode counts as a click. Clicks to other Google pages do not.
• Standard impression rules apply: a link counts as an impression when it is in the current set of results, whether or not the user scrolled to it.
• An AI Overview occupies a single position on the results page, and "all links in the AI Overview are assigned that same position".
• In AI Mode, a follow-up question is treated as a new query: "All impression, position, and click data in the new response are counted as coming from this new user query."
• Experiments in Search Labs are excluded.

The Generative AI performance report

On 3 June 2026, Google announced Search Generative AI performance reports in Search Console, with dedicated reports for Search and Discover, and the help page notes that "As of August 31, 2026, we've rolled out these insights to all websites worldwide". The report answers one question: how often links to your site were shown inside a generative AI feature on Google Search.

• Metric: impressions only, defined as "how many times links to your site were shown to a user in a generative AI feature on Google Search". Clicks, click-through rate and position are not in this report; use the main Performance report for clicks.
• Features covered: AI Overviews and AI Mode, with Google saying it expects to update the list over time.
• Dimensions: pages, countries, dates (hourly to monthly) and devices, with a search type filter for Web: text-based and Web: multimodal.
• Aggregation: the chart is aggregated by property, so two links from your site in one AI response count as one impression, unless you add a URL filter; the pages table is aggregated by page. Chart and table totals can therefore differ.
• If the report is missing, Google says the site may not have enough impressions in these features yet, or may be excluded from Search generative AI features in Search Console settings.
• Open it from the Performance section in Search Console, or directly at search.google.com/search-console/performance/search-analytics/ai.

Link Search Console to GA4

Linking the two gives you Search Console queries and landing pages next to GA4 engagement and conversion data. According to Google's linking instructions, you need the Editor role on the Analytics property and to be a verified owner of the Search Console property; a web data stream can be linked to only one Search Console property and vice versa. The link adds two reports, Google organic search queries and Google organic search traffic, which you publish from the Library. Search Console data appears in Analytics 48 hours after collection and covers at most 16 months.

Because Google's AI clicks are inside the organic numbers, this is also how you connect a rise in AI Overview impressions to a change in organic landing-page conversions.

The gaps to know about

Measurement is good but not complete, and a few limits are worth stating before you present numbers to a board in Muscat.

• Assistants do not always send a referrer. Links opened from mobile apps or copied and pasted arrive as Direct. Some AI traffic will always be under-counted.
• A fetch is not a visit. When ChatGPT-User, Perplexity-User or Claude-User fetches your page to answer a question, that appears in your server logs, not in GA4, because no browser ran your tag. Being read by an assistant and being visited by a person are different events.
• You cannot see the question. Neither GA4 nor Search Console shows the prompt a user typed into an assistant. Search Console's query data covers classic Google queries; the Generative AI report has no query dimension.
• Recognised-assistant lists change. GA4's referrer list and Source Group are maintained by Google; a new assistant will show up as a plain referral until it is added, which is why a custom channel group with your own regex is worth keeping.
• Omani leads often finish on WhatsApp. If your main call to action is a WhatsApp link, mark that click as a key event in GA4, or the AI Assistant channel will look like traffic that never converts.

A monthly routine for an Omani business

How OGB Labs helps

We set up GA4 and Search Console for Omani businesses with the AI Assistant channel, a custom channel group, WhatsApp and form key events, and the Search Console link, then build a simple monthly dashboard so you can see what AI search is worth to you in enquiries rather than clicks. It is part of our SEO, digital marketing and AI search optimisation work in Muscat, and we build the fast bilingual websites that the traffic lands on. Message us on WhatsApp at +968 7111 0727.