How to Track AI Search Traffic in GA4 (and the AI Overview Clicks GA4 Can’t See)

By Elavenil Elangovan · Last checked: November 4, 2026

“How much of our traffic comes from AI?” is a fair question in 2026. Try to track AI traffic in GA4 and you’ll get about half the answer.

It can now show you visits from ChatGPT, Gemini, Claude and other AI assistants. It can’t show you the click someone made inside a Google AI Overview or an AI Mode answer. Those visits land in Organic Search, mixed in with every other Google click.

This guide is the setup I use: the built-in AI Assistant channel, a custom channel group as a backup, an exploration that ties AI visits to leads, and the Search Console reports that cover the Google side. I’m working from Google’s own help pages, linked as I go. Where Google says nothing, I’ll tell you that too.

What GA4 can and can’t see

GA4 puts every session into a channel using its default channel group. Two definitions on that page matter here:

• AI Assistant: visits “from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok.” Google adds that it “excludes Google’s AI Overviews and AI Mode.”
• Organic Search: non-ad links in organic results, “including Google’s AI Overviews and AI Mode.”

A click from a ChatGPT answer can get its own row. A click from an AI Overview gets filed next to a click on a classic blue link, and GA4 has no dimension that tells them apart. The rest of this guide follows that split.

Step 1: Check the built-in AI Assistant channel

Google added this channel on May 13, 2026 (see What’s new in Google Analytics). When the referrer matches a recognized AI assistant, GA4 sets three values:

• Medium: ai-assistant
• Campaign: (ai-assistant)
• Default channel group: AI Assistant

To find it, open Reports → Acquisition → Traffic acquisition and keep the default channel group as the primary dimension. Look for the AI Assistant row.

Two caveats. Google doesn’t publish the full list of assistants it recognizes, so you can’t confirm whether a smaller tool is covered. And I haven’t found Google saying the channel applies to data from before the launch, so for older date ranges I assume it doesn’t.

If the row looks thin, switch the dimension to Session source / medium and search for chatgpt, perplexity, gemini and claude. Anything that matches but sits under Referral or Unassigned is AI traffic the built-in channel missed. If you see chatgpt.com as a source, that is the value your regex needs to catch, whatever medium it arrived with.

Step 2: Build a custom AI channel group

The custom group is my backup. You decide what counts as AI, and Google says custom channel groups “can be applied to your reports retroactively” (custom channel groups help page). That gives you history the built-in channel may not.

1. Go to Admin → Data display → Channel groups.
2. Click Create new channel group. GA4 starts you with a copy of the default channels. Name it something clear, like “Channels + AI”.
3. Click Add new channel, call it “AI Search”, and add a condition: Source matches regex, using the pattern below. Save the channel.
4. Click Reorder and drag AI Search above Referral. Traffic goes to the first channel whose definition it matches, so if Referral sits higher, it claims your ChatGPT visits first.
5. Click Apply, then Save group.

The regex I start with

.*(chatgpt|openai|perplexity|claude\.ai|gemini\.google|copilot\.microsoft|deepseek|grok\.com|meta\.ai).*

Why these names? SE Ranking’s 2026 AI traffic study of 101,574 websites (data through April 2026) found ChatGPT sent 74.78% of AI referral traffic, Gemini 11.56%, Perplexity 7.23%, Copilot 3.51% and Claude 2.62%. The top five cover almost all of it.

Google’s own example on the help page uses a much wider pattern. I keep mine narrow because a loose match on “ai” can pull in sources that have nothing to do with AI. I also leave bing.com out. Add it and all of your regular Bing search traffic ends up in the AI row.

Check the Session source report once a month. When a new AI tool shows up, add it to the pattern.

Limits worth knowing

• Standard properties get 2 custom channel groups (5 on GA4 360), with up to 50 channels in each.
• Channel definitions aren’t case sensitive.
• Custom channel groups don’t work in the Key events paths report.
• Deleting a group can’t be undone, so build a new one before you remove an old one.

Step 3: Tie AI visits to leads in an exploration

Session counts make a nice chart and not much else. What I want to know is whether AI visitors read, sign up or fill in the contact form.

1. Open Explore → Free form.
2. Add dimensions: your custom channel group (the session version), Landing page + query string, and Session source / medium.
3. Add metrics: Sessions, Engaged sessions, Key events and Session key event rate.
4. Put Landing page in Rows and your channel group in Columns, then filter the channel group to AI Search.

Now you can see which pages AI tools send people to and what those people do next. Compare the list with the pages you want cited. If an AI tool keeps sending visitors to an old post, that post is doing more work than you thought, and it deserves an update.

Why AI Overview clicks hide in google / organic

Back to the gap. Pew Research Center analysed the browsing data of 900 US adults in March 2025 (published July 22, 2025). Users who saw an AI summary clicked a traditional result in 8% of visits, against 15% when there was no summary. They clicked a link inside the summary in 1% of visits.

On Google’s side, Search Console counts a click on an external link in an AI Overview as a normal click. The whole AI Overview occupies one position, and every link inside it gets that same position. In AI Mode, a follow-up question counts as a new query. Google’s AI features guide also says clicks from results pages with AI Overviews are “higher quality”, meaning people tend to spend more time on the site.

In GA4, all of those visits arrive as google / organic. There’s no referrer flag and no parameter you can filter on. From what Google documents, any tool that claims to split AI Overview clicks out of GA4 is estimating.

Step 4: Fill the Google gap with Search Console

The Generative AI performance report

Search Console’s Generative AI performance report shows impressions from AI Overviews and AI Mode, broken down by page, country, device and date. It’s built around impressions. Clicks still sit in the main Performance report, mixed in with regular results.

The GA4 and Search Console link

Link GA4 to Search Console under Admin → Product links → Search Console links. Per Google’s integration guide, you get two reports: Google Organic Search Queries and Google Organic Search Traffic. They are unpublished by default, so open Library and publish the Search Console collection.

• One web data stream links to one Search Console property, and the other way round.
• Data covers up to 16 months and arrives about 48 hours late.
• Search Console metrics only combine with three GA4 dimensions: Landing page, Device and Country.

How I read the two together

1. In the Generative AI report, export the pages with the most AI impressions for the last 3 months.
2. In GA4, open Google Organic Search Traffic and find the same landing pages. Note organic clicks, engagement and key events.
3. Watch the trend. If AI impressions climb while organic clicks fall, the AI answer is probably satisfying the search on Google. If both climb, being cited is helping you.

This is correlation. Google gives you nothing more precise today, so I treat it as a direction check and keep the claims in my reports modest.

What the numbers mean for your site

Keep the scale in mind. SE Ranking puts AI platforms at 0.32% of all website traffic in 2026, up from 0.24% in 2025. Small share, fast growth.

Some AI app visits may also arrive without a referrer and land in Direct. I can’t measure that slice, so I flag it as a known gap whenever I report AI numbers.

Low numbers don’t mean AI is irrelevant. Plenty of people read the answer and never click, and Pew’s 1% figure shows how rarely links inside summaries get clicked. Being named in the answer can still shape who people contact. My post on how AI reads your reviews covers one of the signals that decides it.

My weekly check to track AI traffic in GA4

Ten minutes, every Monday:

• GA4 Traffic acquisition: the AI Assistant row and your AI Search row, week over week.
• Your exploration: top AI landing pages and their key events.
• Search Console Generative AI report: pages gaining or losing AI impressions.
• GA4 Google Organic Search Traffic: the same pages, with clicks and engagement.
• Session source: any new AI tool that needs adding to the regex.

FAQ

Your next step

Build the custom channel group today. It’s a ten-minute job, and because Google says it can apply to past data, you shouldn’t have to start from an empty report.

If you want me to set up AI traffic tracking and reporting on your site, start from my services page. If you want the opposite and need your pages out of AI Overviews, read how to get rid of AI Overviews. Running a new site with little traffic to measure yet? Begin with how to drive traffic to your new blog.