The challenge is measuring them. Until recently, Google Analytics 4 lumped AI visits in with ordinary referrals, or lost them entirely in Direct traffic. That has started to change. Here's what GA4 does out of the box, what it misses, and how to set up tracking you can rely on.

Step 1: Use GA4's New AI Assistant Channel

On May 13, 2026, Google added a built-in AI Assistant channel to GA4's default channel grouping. When GA4 recognizes a visit from a supported AI chatbot, it now labels it automatically:

ChatGPT, Gemini and Claude are among the recognized sources. No setup is required.

To see it: go to Reports > Acquisition > Traffic acquisition. AI Assistant appears as its own row. Click the + next to the primary dimension and add Session source / medium to break it down by chatbot.

Two important caveats: it isn't retroactive — visits before May 13, 2026 keep their old classification, usually Referral, so treat that date as the start of your trend line. And Google AI Overviews and AI Mode aren't included — clicks from AI features inside Google Search still count as Organic Search, because they happen within Google's own search results.

Step 2: Build a Custom Channel Group for Wider Coverage

The built-in channel only catches sources GA4 recognizes. To include more AI tools, or to group them your own way, create a custom channel group:

  1. Go to Admin > Data display > Channel groups.
  2. Click Create new channel group and name it something like "Channels with AI detail." GA4 copies the default channels as a starting point.
  3. Click Add new channel and name it AI Chatbots.
  4. Set the condition to Source matches regex and paste:
.*(chatgpt|openai|perplexity|gemini\.google|copilot\.microsoft|claude\.ai|meta\.ai|deepseek).*
  1. Save, then drag the AI Chatbots channel above Referral in the list. GA4 assigns each session to the first channel it matches, so if Referral sits higher, it will claim your AI traffic first.
  2. Save the channel group.

Unlike most GA4 settings, custom channel groups apply to historical data, so this also gives you a view of AI traffic from before May 2026. Update the regex as new AI tools appear.

Step 3: Find Out Which Pages AI Sends People To

Knowing how much AI traffic you get is useful. Knowing where it lands is far more useful, because it shows which content AI tools trust and cite.

  1. Go to Explore and start a Free form exploration.
  2. Add the dimensions Session source / medium and Landing page + query string.
  3. Add the metrics Sessions, Engaged sessions, Key events and Total revenue (if you sell online).
  4. Add a filter where Session medium exactly matches ai-assistant, or use your custom AI Chatbots channel.
  5. Put landing page in rows and source in columns.

Look for patterns. AI tools often favor detailed guides, comparison pages, original data and clear definitions. Pages that already get AI traffic are good candidates to expand and keep up to date.

Step 4: Compare AI Visitors With Everyone Else

AI visitors often behave differently. They may land deep in your site, read more and convert at a different rate. Compare the AI channel against Organic Search and Referral on:

This is the number that gets leadership's attention. "AI traffic is 2% of sessions" sounds small. "AI visitors convert at twice the site average" starts a budget conversation.

Step 5: Account for the AI Traffic You Can't See

This is where most guides stop, and where the real measurement gap is. A significant share of AI-driven visits never shows up as AI traffic, for three main reasons.

Missing referrers. Mobile apps, including ChatGPT's own app, and some browser privacy settings often don't pass referrer information. Those visits land in Direct. Industry estimates vary widely, but a meaningful share of AI-referred visits likely arrives this way.

Copy and paste. Someone reads an AI answer, then types your brand name into Google. That visit shows up as Organic Search, even though AI started the journey.

Zero-click answers. Often the AI answers the question using your content and the person never visits at all. No session, no data.

You can't fix these completely, but you can reduce the blind spot:

Step 6: Report It Simply

A monthly AI traffic summary for stakeholders only needs a few lines:

If you use Looker Studio, connect your GA4 property and build a simple page filtered to the AI channel, so the numbers update automatically.

The Bottom Line

GA4's new AI Assistant channel is a welcome start, but it only counts the AI visits that arrive with a recognizable label. Add a custom channel group for wider coverage, focus on which pages AI sends people to, and keep an eye on the Direct traffic that hides the rest.

Getting this right depends on a channel grouping and UTM setup that's already clean — if Referral and Direct are absorbing traffic they shouldn't, adding an AI Chatbots channel on top won't fix the underlying attribution problem. Our Attribution & Measurement Strategy service builds measurement frameworks that account for new channels like this one properly.

Clicks are only half the story, though. In the next post, we'll look at how to measure your brand's visibility inside AI answers, even when nobody clicks.

Sources: SEO Sherpa: GA4 just gave AI traffic its own channel · GA Agency: GA4's new AI Assistant channel is a start · Seresa: Why AI traffic still hides in Direct · PPC Land: ChatGPT adds UTM parameters to more links

Travis Gunn
Travis Gunn
Founder of GA4 Health Check. Working with Google Analytics since 2013, with over 250 clients audited across almost every industry vertical. 100% Job Success on Upwork for over a decade.