AI Search Analytics: Track AI Traffic in GA4 and Beyond

AI search analytics in two halves: track AI traffic in GA4 with a tested regex, then measure the AI answers analytics cannot see. Weekly routine included.

AI search analytics answers two questions: how many visits AI engines send you, and how often they mention you when nobody clicks. This guide sets up tracking AI traffic in Google Analytics 4, including the new AI Assistant channel and a tested regex, then adds the answer-side checks analytics cannot do. It ends with a 30-minute weekly review.

Definition: AI search analytics measures how AI answer engines affect a website. The clicks half counts the visits engines such as ChatGPT, Perplexity, and Gemini send you, in tools like Google Analytics 4. The answers half measures whether those engines name or cite you at all, which analytics cannot see.

The two halves of AI search analytics

Clicks are the half you already have tools for. AI traffic analytics lives in GA4: an AI-referred visit with a referrer or UTM tag arrives with a source and a landing page.

Answers are the bigger half, and they leave no trace in analytics. In browsing data on 900 U.S. adults from March 2025, people who saw a Google AI summary clicked a link inside it on just 1% of visits. They clicked a traditional result on 8% of visits, versus 15% without a summary (Pew Research Center). An engine can recommend you to a buyer who never visits. Metric definitions and formulas are in our post on AI search visibility metrics.

What changed in GA4 in 2026: the AI Assistant channel

In May 2026, Google Analytics added an AI Assistant channel to the Default Channel Group. When the referrer matches Google's list of recognized AI assistants, GA4 sets the medium to ai-assistant. Find it in Reports > Acquisition > Traffic acquisition, grouped by Session default channel group.

It has three gaps:

• The list is unpublished. Google's channel definitions name ChatGPT, Gemini, DeepSeek, Copilot, and Grok as examples. The release note names ChatGPT, Gemini, and Claude. Neither names Perplexity.
• AI Overviews and AI Mode are excluded. Those clicks count as Organic Search, and GA4 cannot split them out.
• No referrer, no match. Sessions with no referrer and no UTM tag land in Direct.

GA4's Source Group dimension, added in June 2026, groups ChatGPT and Perplexity traffic retroactively, but it is not a channel. Treat the native channel as a starting point and add a channel group you control.

How to track AI traffic in GA4, step by step

Custom channel groups apply retroactively, so this setup also shows AI traffic from before May 2026. Standard properties allow two custom groups.

Step 1: Create the channel group

Go to Admin > Data display > Channel groups and click Create new channel group. GA4 starts you from a copy of the default rules.

Step 2: Add an AI engines channel

Add a channel named AI engines with two conditions joined by OR:

1. Medium exactly matches ai-assistant, which catches whatever Google's list recognizes.
2. Source matches regex, with this pattern:

^(www\.)?(chatgpt\.com|chat\.openai\.com|perplexity\.ai|perplexity|gemini\.google\.com|copilot\.microsoft\.com|copilot\.com|claude\.ai|grok\.com|chat\.deepseek\.com|deepseek\.com|meta\.ai)$

GA4 regex is full-match, and report filters are case-sensitive, so the pattern lists exact lowercase domains, and the anchors keep it exact in partial-match filters too. In our test it matched every listed domain, with or without www, and rejected look-alikes such as notion.ai, character.ai, and copilot.github.com.

Skip the sample AI regex on Google's custom channel groups help page. Under full-match rules it missed grok.com and chat.deepseek.com in our test, and it matched unrelated sources such as lombardi.com (via its "bard" rule) and notion.ai. Add other AI domains you spot in Referral.

Step 3: Reorder and save

GA4 puts each session in the first channel whose rules it matches. Your copy includes Google's AI Assistant channel; delete it, or move AI engines above it, so all AI sessions land in one channel. Then click Reorder, move AI engines above Referral and Organic Search, and save.

Step 4: Read it in reports

In Traffic acquisition, switch the primary dimension to your new channel group. To check ChatGPT traffic and the rest with no setup, use Session source as the dimension and add a "matches regex" filter with the same pattern. Do not filter on Session source / medium: "chatgpt.com / referral" never matches an anchored pattern.

ChatGPT traffic analysis: landing pages and key events

The useful questions are where AI visitors land and whether they convert. Build a Free form exploration:

• Rows: Session source, then Landing page + query string
• Values: Sessions, Engaged sessions, Engagement rate, Key events, Session key event rate
• Filter: Session source matches regex, using the same pattern

Duplicate the tab, remove the filter, and add your channel group as a column to compare AI engines with Organic Search on the same pages. If signups or demo requests are not key events yet, mark them in Admin.

OpenAI says ChatGPT adds utm_source=chatgpt.com to referral links from its search results, for sites that allow its OAI-SearchBot crawler (OpenAI publisher FAQ). In GA4, UTM parameters override the referrer and missing UTM fields show as (not set), so some ChatGPT sessions land in Unassigned. Filtering on Session source catches them.

Why GA4 undercounts AI traffic

When tracking AI traffic, treat every GA4 number as a floor:

• No referrer. GA4 records a session as direct when it has no referral information. Native apps and in-app browsers can open links without sending one.
• Referrer policies. A no-referrer policy omits the Referer header entirely. The engines rarely document whether their outbound links send a referrer.
• AI agents and AI browsers. Agent modes and AI browsers such as ChatGPT Atlas and Perplexity Comet load pages in a real browser, so their visits can fire GA4 like any other session. OpenAI signs ChatGPT agent's requests, so a CDN that verifies signed agents can flag them.
• Copy and paste. A reader pastes your URL or searches your brand after an answer. GA4 sees direct or branded organic.
• AI Overviews and AI Mode. Counted in Organic Search by design.
• No click at all. The largest gap, and the reason the answers half exists.

Three ways to recover some signal:

1. Ask. Add "AI assistant (ChatGPT, Perplexity, etc.)" to a "How did you hear about us?" field.
2. Watch direct traffic to deep pages. Few people type a long blog URL from memory, so a rise hints at copied links.
3. Check server logs. Look for ChatGPT-User, Perplexity-User, and Claude-User in server or CDN logs; their vendors document these as fetches made when a person asks a question. User agents can be faked, so check hits against published IP ranges where they exist (OpenAI publishes one for ChatGPT-User). A verified hit is not a visitor, but it shows an engine fetched your page to answer someone.

The answers half: AI visibility your analytics cannot see

An engine can name you, cite your page, or leave you out, and none of it reaches GA4. Track mention rate, citation share, and position (rank, meaning appearance order in the answer) per prompt and engine, and classify each run as Named, Cited only, or Absent.

First-party data on AI answers exists only for Google Search's AI features and Microsoft's Copilot and Bing surfaces:

• Search Console. The Generative AI performance report launched June 3, 2026 and had reached all sites worldwide by August 31, 2026. It shows impressions in AI Overviews and AI Mode by page, country, device, and date, but no clicks, queries, or answer text. Whether AI Overviews names your brand is what our AI Overview tracker shows.
• Bing Webmaster Tools. AI Performance, in public preview since February 2026, shows citations, grounding queries, and page-level citation activity for Microsoft Copilot and Bing's AI summaries. A June 2026 update added Bing's Citation Share: your share of all citations for a grounding query.

No self-serve first-party report covers ChatGPT, Perplexity, Claude, Grok, DeepSeek, Meta AI, or the Gemini app itself; Search Console covers only AI features inside Google Search. For those, run a fixed prompt list yourself (same wording, several runs, logged per engine), as described in our guide to tracking brand mentions in AI search.

Or skip the spreadsheet. The free AI visibility checker takes a one-time snapshot across all 8 engines, prompts and answers included. The LLM rank tracker re-runs every tracked prompt daily on all 8 engines, with citation tracking for cited pages. Paid plans are on a waitlist; you can reserve a plan now. Tracking shows where you stand. It cannot make an engine mention you.

AI traffic analytics and answer data at a glance

A 30-minute weekly AI search analytics review

Same day each week, same order:

1. GA4 channel trend (5 min). Sessions in the AI engines channel, week over week, split by Session source so you monitor ChatGPT traffic separately. Scan Referral for AI domains your regex misses.
2. Landing pages and key events (5 min). Top 10 AI landing pages. Flag new entries and drop-outs.
3. Hidden traffic (3 min). Direct sessions to deep pages, plus survey answers that name an AI assistant.
4. Search Console (5 min). Generative AI impressions by page, week over week.
5. Bing Webmaster Tools (4 min). Citations, Bing's Citation Share, and new grounding queries.
6. Tracked prompts (5 min). Mention rate, citation share, and position per engine. List prompts that moved between Named, Cited only, and Absent.
7. One note, one action (3 min). Annotate what changed and pick one thing to do.

Do not react to a single week; answers vary run to run, so compare 4-week trends. Monthly, re-test your regex against the full Referral source list.

Free tool to track AI traffic: what each category does

Three tool categories show up for this search:

For your own site, the first row is the free answer. Panel estimates help you size a competitor, not measure yourself. Only the third row reads the answer text itself, and that is where SeenMeter sits. Real answers, not a black-box score.

FAQ

How do I track AI traffic in GA4?

Start with the built-in AI Assistant channel in Traffic acquisition. Then add a custom channel group whose AI engines channel matches the medium ai-assistant or a source regex, placed above Referral.

Why does my ChatGPT traffic show up as direct in Google Analytics?

GA4 records a session as direct when no referral information arrives: links opened from apps, referrer policies that strip the header, or URLs pasted from an answer. The utm_source=chatgpt.com tag helps when the link keeps it.

Does GA4's AI Assistant channel include Perplexity?

Google has not said. Neither the channel definition nor the May 2026 release note names Perplexity, and the referrer list is unpublished. Add perplexity.ai to your own channel group.

Does Google Analytics show traffic from AI Overviews?

Not separately. Clicks from AI Overviews and AI Mode count as Organic Search. Search Console's Generative AI performance report shows impressions in those features, but not clicks.

Can I see which ChatGPT prompts sent visitors to my site?

No. Analytics sees the source and the landing page, not the conversation. To learn which prompts name you, run or track a fixed prompt set against the engines.

Check where you stand

GA4 shows the clicks. For the answers, start with the free AI visibility checker: submit your domain and email, and get a report with every prompt disclosed and every answer quoted. It's free and needs no signup. While SeenMeter is in beta, checks run concierge-style: we run your brand through all 8 engines and email the full report within 24 hours.