Skip to content

Track AI traffic in GA4: ChatGPT, Perplexity, Gemini and Copilot

How to see AI referral traffic in GA4: the AI Assistant default channel, a custom channel group with regex, an exploration by landing page, and what the data misses.

By Crawlito · Updated 7 min read

In short

  • Since 13 May 2026, GA4 gives sessions from recognized AI assistants the medium ai-assistant, the campaign (ai-assistant) and an AI Assistant channel in the Default Channel Group.
  • Google has not published the full list of assistants it recognizes, so a custom channel group with your own source regex is still useful as a cross-check.
  • At the time of writing, ChatGPT links usually carry utm_source=chatgpt.com, which makes ChatGPT clicks identifiable even when the referrer is missing.
  • GA4 assigns a session to the first channel whose conditions it matches, so a custom AI channel must sit above Referral.
  • Referral data counts people who clicked through with a referrer or tag; visits with neither land in Direct, so AI traffic in GA4 is a minimum.
On this page

GA4 can show you visits from AI assistants in three ways: the built-in AI Assistant channel Google added on 13 May 2026, a custom channel group you define with a regular expression on the session source, and an exploration that breaks those sessions down by landing page and key events. Use the built-in channel for the headline number, your own channel group to check what it includes, and the exploration to see which pages people actually land on. All three count only visits that arrive with a referrer or a tracking tag, so treat the result as a minimum.

This guide sets up each one, with the exact menus and a tested regex, and explains what the numbers cannot tell you. For the wider question of crawler visits versus human clicks, see measuring AI crawler traffic.

The AI Assistant channel GA4 added in May 2026

Google's What's new in Google Analytics page has an entry dated 13 May 2026 titled "New AI Assistant traffic measurement". It says you can now identify visits from chatbots like ChatGPT, Gemini and Claude, and that it changes three traffic source values when the referrer matches a recognized AI assistant:

DimensionNew value
Mediumai-assistant
Default channel groupAI Assistant
Campaign(ai-assistant)

No setup is needed. Open Reports > Acquisition > Traffic acquisition, keep the primary dimension on Session default channel group, and look for the AI Assistant row.

What Google does not say is just as important:

  • Which assistants are recognized. The entry names ChatGPT, Gemini and Claude as examples. Google's default channel group definitions give ChatGPT, Gemini, Deepseek, Copilot and Grok as example sources. Neither publishes a full list, so you cannot tell from the documentation whether Perplexity or smaller tools are included. Check your own data, as described below.
  • Google's own AI features. Clicks from AI Overviews and AI Mode come from Google Search. GA4's default channel group definitions say Organic Search includes Google's AI Overviews and AI Mode, and that the AI Assistant channel excludes them. Google's AI features documentation also counts those clicks in Search Console under the Web search type. For more on how these clicks arrive, see Google Search referrers and AI Mode traffic.
  • History. The entry does not say the channel was applied to data before 13 May 2026. If you compare periods across that date, expect a step change where sessions moved out of Referral.

A later entry, dated 11 June 2026, adds a Source group dimension that consolidates messy source values and says it includes built-in grouping for sources like ChatGPT and Perplexity. It is useful for tidier reports, but it is a grouping of sources, not a channel.

Build your own AI channel group as a cross-check

A custom channel group lets you decide exactly which sources count as AI and see whether the built-in channel misses any. Google's custom channel groups help page describes the setup.

  1. Go to Admin, and under Data display click Channel groups. You need the Editor role or above.
  2. Click Create new channel group. GA4 starts you with a copy of the default group.
  3. Name it, for example "Channels with AI detail".
  4. Click Add new channel, name it "AI assistants (custom)", and add a condition: Source matches regex with the pattern below.
  5. Click Reorder and move the new channel above Referral, then click Apply and Save group.

The order matters. Google says traffic is assigned to the first channel whose definition it matches. Below Referral, your AI channel would never receive a session. Place it next to the built-in AI Assistant channel so you can compare them.

A pattern anchored on the hostnames avoids catching unrelated sources:

^(chatgpt\.com|(www\.)?perplexity\.ai|copilot\.microsoft\.com|gemini\.google\.com|claude\.ai|chat\.mistral\.ai)$

These hostnames are the assistants' own web addresses at the time of writing, not a documented list. Before you rely on the pattern, open Traffic acquisition, switch the primary dimension to Session source, search for terms like gpt, perplexity, copilot and gemini, and add any variants you actually receive.

Limits worth knowing: a standard property can have two custom channel groups and a GA4 360 property five, each with up to 50 channels. Custom channel groups apply to reports retroactively, so you can use the new group on past data. You can also make it the property's primary channel group from the same admin page.

Why ChatGPT is easier to identify than the others

At the time of writing, links from ChatGPT usually carry utm_source=chatgpt.com. So a ChatGPT click carries chatgpt.com as its source even when the browser sends no referrer. OpenAI used to describe this in a publishers FAQ, but that page is no longer available at its old address, so treat the parameter as observed behaviour that could change.

Other assistants do not document a tracking parameter. Their visits are identified by referrer only, so they are more likely to fall into Direct when a referrer is stripped.

Build an exploration by landing page

Channel reports tell you how much AI traffic you get. An exploration tells you where it lands and what it does.

  1. Open Explore and start a Free form exploration.
  2. Under Dimensions, import Session source / medium, Session default channel group and Landing page + query string.
  3. Under Metrics, import Sessions, Engaged sessions and Key events.
  4. Drag Landing page + query string to Rows and Session source / medium to Columns, or the other way round if you prefer.
  5. Add a filter: Session default channel group exactly matches AI Assistant. Duplicate the tab and use Session source matches regex with your pattern for the comparison.

What to look for:

  • Which pages get AI visits. Often deep pages: a pricing page, a comparison, a help article. Those are the pages to keep accurate and fast.
  • The query string. ChatGPT links usually include utm_source=chatgpt.com, which confirms the source of each landing page row.
  • Key events per session. Compare with Organic Search on the same pages, keeping in mind that the AI sample is usually small.

For the outcome side, including forms and lead quality, the guide to AI search conversion measurement goes into event design.

What GA4 cannot tell you about AI traffic

GA4 sees sessions where its tag runs in a browser and the visit carries a recognizable referrer or tag. That leaves gaps:

GapWhy it happensWhere it shows up
Visits with no referrerReferrer policies, links opened from desktop or mobile apps, copied URLsDirect
Clicks from Google AI Overviews and AI ModeThey come from Google SearchOrganic Search
Crawler and fetcher visitsBots such as OAI-SearchBot or ChatGPT-User usually do not run your analytics tagNot in GA4; use server logs
People who read an answer and never clickNo visit happensNowhere in analytics
Visitors who block analytics or decline consentThe tag does not run or runs in a limited modeMissing or modelled

So a rising AI Assistant channel shows more identifiable clicks, not necessarily more mentions in answers. A flat channel does not prove assistants ignore you. Our post on AI citations vs referral traffic explains how to report these as separate numbers with the right denominators.

Two more checks keep the data honest:

  • Look at existing segments and filters. A segment such as "medium does not contain referral" or "medium equals organic" now behaves differently for sessions that moved to the ai-assistant medium.
  • Check cross-domain setups. If visitors move from your marketing site to an app on another domain, a broken cross-domain configuration turns your own domain into the source of the second session. The guide to GA4 cross-domain referrals covers that fix.

A simple monthly AI traffic report

Keep it small and repeatable:

  1. Sessions and key events from the AI Assistant channel, with the month before and the same month last year where possible.
  2. The same from your custom channel, and the difference between the two.
  3. The top ten landing pages for AI traffic, with engaged sessions.
  4. Any new source values matching your search terms that are not yet in your regex.
  5. A note of anything that changed measurement: GA4 updates, consent banner changes, site migrations.

The planned post on an AI search reporting dashboard shows how to combine this with crawler data from your logs.

Frequently asked questions

Does GA4 track ChatGPT traffic automatically?

Yes, since 13 May 2026. Sessions whose referrer matches a recognized AI assistant get the ai-assistant medium and appear in the AI Assistant channel. ChatGPT links also usually carry utm_source=chatgpt.com at the time of writing.

Is Perplexity included in the AI Assistant channel?

Google's announcement names ChatGPT, Gemini and Claude and does not publish a full list. Check Session source values together with the channel in your own reports to see where Perplexity sessions land.

Do I still need a custom channel group for AI traffic?

It is optional. It lets you control exactly which sources count as AI and compare against the built-in channel. Standard properties allow two custom groups, so use one slot only if you will look at it.

Why is AI traffic so low in GA4?

Many AI-assisted visits arrive without a referrer and land in Direct, many answers are read without a click, and Google's AI features are counted as Organic Search. GA4 shows a minimum, not the full picture.

Can GA4 show AI crawler visits?

No. Crawlers and most fetchers do not run your analytics tag. Count them in server or CDN logs instead.

Make sure the pages AI visitors land on work

Once you know which pages AI traffic reaches, check that those pages are readable by the crawlers and fetchers that send it. The free check tests one page with no account needed, and an audit covers up to 500 pages with prioritized fixes.

Filed under Strategy and audits. Topics: analytics, measurement, chatgpt, perplexity, ai-search