How to Track AI Search Traffic in GA4 and Beyond

The short version

Google Analytics 4 now documents a default AI Assistants channel. When a recognized assistant sends a referrer, GA4 assigns the medium ai-assistant and the campaign (ai-assistant). That gives many properties a clean starting point without a custom regex.

Three boundaries still matter. GA4 sees visits after a click, while an AI answer can mention your brand without sending a visit. Google classifies clicks from AI Overviews and AI Mode as Organic Search. Visits without a referrer cannot be assigned to an assistant from GA4 data alone.

Why AI search attribution is incomplete

The first gap is zero-click behavior. Pew Research Center analyzed browsing from 900 U.S. adults and 68,879 unique Google searches from March 2025. When an AI summary appeared, users clicked a traditional result in 8% of visits, compared with 15% when no summary appeared. A source inside the summary received a click in 1% of visits with a summary. Citation exposure and website traffic are different measurements.

The second gap is the HTTP referrer. A source can send only its origin, or omit the Referer header, depending on its policy and the navigation context. The web standard's default policy sends the origin for same-security cross-origin requests, but stricter policies and app-to-browser paths can remove that evidence. When the evidence is absent, a responsible analytics system leaves the visit unattributed.

The third gap is channel overlap. Google's current default-channel documentation puts non-ad links from AI Overviews and AI Mode inside Organic Search. Ahrefs made the same limitation explicit in its June 2025 study of 81,947 sites: Google's AI search traffic could not be reliably separated from traditional search in site analytics. Do not create a precise Google AI traffic number from data that lacks the distinction.

Step 1: Check GA4's native AI Assistants channel

Open Reports → Acquisition → Traffic acquisition. Set the primary dimension to Session default channel group and look for AI Assistants. Use the session-scoped dimension for visit performance. Use the first-user dimension only when the question is how a person was originally acquired.

Add Session source / medium as a secondary dimension. This shows which assistant generated the visit and confirms whether GA4 assigned ai-assistant. OpenAI provides an additional check: its publisher documentation says ChatGPT search links automatically include utm_source=chatgpt.com.

Step 2: Build a controlled custom channel when needed

A custom channel remains useful when you need a stable reporting definition, want to include an assistant GA4 has not classified, or need to apply the rule retroactively in reports and explorations. Google says standard GA4 properties can create two custom channel groups in addition to the predefined group.

1. Open Admin → Data display → Channel groups.
2. Copy the default channel group and name the copy AI traffic reporting.
3. Add a channel named AI Assistants.
4. Use Source matches regex as the channel condition, with assistant domains verified in your property.
5. Do not combine that source condition with Medium exactly ai-assistant in the same condition group. An unclassified assistant can still carry referral, so requiring both values defeats the fallback.
6. Place AI Assistants above Referral. Google evaluates channels in order and uses the first match.

A conservative source regex looks like this:

^(chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|notebooklm\.google\.com)$

Treat that list as a starting point. Add a host only after it appears in your acquisition data or the platform documents it. Google's first-party example is source-regex driven and uses a broad expression that matches terms such as ai, gpt, and google. For a production property, exact host matching reduces the chance that an unrelated source moves out of Referral or Organic Search.

Do not add Google Search to this custom channel. GA4's documented behavior keeps AI Overview and AI Mode clicks in Organic Search, and the visit record does not expose a dependable flag for splitting them out.

Step 3: Build the report around business outcomes

Session count alone says little about value. In Traffic acquisition or an Exploration, use the AI Assistants channel with these dimensions and metrics:

Small samples swing sharply. Ahrefs reported that AI search supplied 0.5% of its traffic but 12.1% of signups in one 30-day window in 2025. That case study describes one site and one measurement window. Report the visit and conversion counts beside every rate so readers can judge the denominator.

Step 4: Connect GA4 to visibility and revenue

GA4 starts after the click. To measure the full path, combine it with prompt-level monitoring, server-side referral evidence, and your CRM.

Measure answer exposure

Track a fixed set of buyer prompts across ChatGPT, Perplexity, Gemini, Claude, and Google AI Overview. Store mention status, position, citations, cited URLs, competitor names, sentiment, engine, and run time. The AI search monitoring guide explains that layer. It gives you the denominator that referral reports lack: how often the brand was present before anyone had a chance to click.

Preserve server-side referral evidence

Foglift Tracker records recognized AI-referrer visits from the request itself. It stores the landing path, matched referrer host, and timestamp. It does not store an IP address, cookie, fingerprint, or full query string. Referrer-stripped visits stay uncounted.

This complements GA4 because the server sees the incoming request before browser analytics runs. It still cannot identify the prompt that produced the visit. Match trends by engine, landing page, and time window, then label the relationship as an inference unless a campaign parameter or other deterministic identifier connects the records.

Carry the source into the CRM

Persist the first attributable AI source and the converting-session source with the lead. Keep both fields. A person can first arrive from Perplexity, return through branded search, and convert later. Add “AI assistant” to the self-reported discovery field so users can tell you about exposure that did not create a trackable first visit.

Join those fields to qualified pipeline, closed revenue, activation, or retention. The AI search ROI framework covers the broader operating model. Keep click attribution and self-reported influence in separate columns so the total remains auditable.

Use an evidence-graded dashboard

A useful dashboard shows the whole path while preserving the strength of each signal. Use three labels: confirmed, inferred, and directional.

Review the dashboard weekly for operational changes and monthly for business outcomes. The weekly view finds broken classification, new assistant sources, citation losses, and landing page shifts. The monthly view gives conversion and pipeline denominators time to accumulate.

Sources and data freshness

1. Google Analytics Help, Default channel group, accessed July 14, 2026. Documents the AI Assistants channel definition and Google AI Overview / AI Mode treatment.
2. Google Analytics Help, Custom channel groups, accessed July 14, 2026. Documents channel order, limits, retroactive reporting, and the AI-assistant example.
3. OpenAI, Publishers and Developers FAQ, accessed July 14, 2026. Documents utm_source=chatgpt.com on ChatGPT search referral URLs.
4. MDN, Referrer-Policy header, accessed July 14, 2026. Documents when origin data is sent or omitted.
5. Pew Research Center, Google AI summary click analysis, July 22, 2025. Sample: 900 U.S. adults and 68,879 Google searches.
6. Ahrefs, AI Traffic Has Increased 9.7x in the Past Year, June 26, 2025. Sample: 81,947 sites.
7. Ahrefs, AI search conversion case study, June 16, 2025. Single-site, 30-day Ahrefs conversion analysis.
8. Foglift Tracker documentation, accessed July 14, 2026. Current recognized referrers, stored fields, privacy boundary, and referrer-stripping behavior.

Frequently asked questions