How to Measure ChatGPT and Perplexity Traffic in GA4

B2B teams cannot prove AEO without measurement. GA4 added a native AI Assistant channel on May 13, 2026. Qualifying sessions get medium ai-assistant, campaign (ai-assistant), and Default Channel Group = AI Assistant. That channel is a floor, not a full picture. Perplexity is not named in Google's live list. Mobile apps strip referrers. History before May 2026 is not backfilled. The practical setup is native channel + custom channel group + prompt log + conversion reporting.

G2's 2026 AI Search Insight Report found that 51% of B2B software buyers start research with an AI chatbot more often than Google. If those visits land in Referral or Direct, the board will keep treating ChatGPT as a branding experiment. This post is the GA4 half of that stack. For Google's own AI surfaces, use Search Console, not this channel. See Google AI Mode vs AI Overviews and the GSC platform properties post.

Why ChatGPT referrals do not show up as organic

ChatGPT referrals are not organic search. Organic Search in GA4 is reserved for search engines, including Google's AI Overviews and AI Mode. ChatGPT, Gemini, and other assistants are referrers. Until May 13, 2026, most of them sat in Referral. Some never sent a referrer at all and landed in Direct.

That split is why AEO looks fake on a default Traffic acquisition report. A buyer asks ChatGPT for a vendor shortlist, clicks a source, and your dashboard credits a random referring domain or (direct) / (none). The session is real. The channel label is wrong. Austin Heaton has reported 5,130 ChatGPT referrals from that work. None of those sessions belong in Organic Search.

Two more traps sit on top of the channel mix-up:

• Citations are not clicks. A model can name you, quote you, or link you. Only the click creates a GA4 session. That is why you still need a prompt log. See AI mentions vs AI citations.
• Google's AI answers are a different report. Google's Default Channel Group docs say the AI Assistant channel excludes Google's AI Overviews and AI Mode. Those clicks stay in Organic Search. Mixing them into one AI traffic number will overstate ChatGPT and hide Google.

If ChatGPT is sending demos and your GA4 report still calls it Referral, book a 30-minute call and we will map the dual setup on your property.

What GA4 native AI Assistant channel actually captures

GA4 native AI Assistant channel captures sessions whose referrer matches Google list of AI assistants. Google May 13, 2026 What's New note named ChatGPT, Gemini, and Claude. The live Default Channel Group page now describes the channel as traffic from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok, and it excludes AI Overviews and AI Mode.

Google own definition is mechanical. The medium exactly matches ai-assistant. When the referrer matches Google list of AI Assistants, GA4 sets medium to ai-assistant and campaign to (ai-assistant). You do not add a tag. You do not edit the default group. You open Reports / Acquisition / Traffic acquisition and look for the AI Assistant row.

What Google has actually stated, as of this page being fetched on August 21, 2026:

• Launch date: May 13, 2026, in What's new in Google Analytics.
• Named at launch: ChatGPT, Gemini, and Claude.
• Named in the live Default Channel Group description: ChatGPT, Gemini, Deepseek, Copilot, or Grok.
• Explicit exclusion: Google AI Overviews and AI Mode, which remain Organic Search.
• Google has not published the full hostname list behind a list of AI Assistants. Do not invent one.

Claude was named on May 13 and is not in the current published sources-like sentence. Deepseek, Copilot, and Grok are. That is Google help page, not a recap. Confirm the live list on the day you put a number in a QBR. Google says these definitions may evolve as the market changes.

On June 11, 2026, Google also shipped a Source Group dimension with built-in grouping for ChatGPT (OpenAI) and Perplexity, and it said Source Group is populated retroactively. That is a different field from Default Channel Group. Use it as a source-cleanup layer. Do not treat it as a replacement for the AI Assistant channel.

What it misses (Perplexity, in-app referrers, history before May 2026)

The native channel misses three things that matter for B2B reporting: engines Google has not named, sessions with no referrer, and everything before May 13, 2026. Perplexity is the coverage gap. In-app browsers are the dark-traffic gap. The missing backfill is the trend-line gap.

Perplexity is not in Google's live named list. The Default Channel Group page names ChatGPT, Gemini, Deepseek, Copilot, and Grok. It does not name Perplexity. Recaps from Digital Applied (June 11, 2026) and Insightland (updated July 28, 2026) report that Perplexity still lands in Referral. Secondary blogs disagree. Until Google names Perplexity in the AI Assistant definition, treat those visits as Referral unless your custom group catches them.

Seer June 22, 2026 tracking guide documents the referrer hostnames you will actually see when the header is present: chatgpt.com, gemini.google.com, perplexity.ai, and claude.ai. That table is a snapshot of source values, not Google official channel list. Use it to write source rules. Do not use it to claim Perplexity is inside the native channel.

In-app and stripped referrers land in Direct. ChatGPT mobile app, in-app browsers, and copy-paste URLs often send no document.referrer. Seer table shows ChatGPT search-result clicks can arrive as Direct, source Direct, medium none, campaign (not set). Recaps put that dark share in a wide range. I am not going to print a 60-70% multiplier I cannot verify on a primary page. The defensible line is simpler: the AI Assistant row is a floor. Direct will still hide some AI clicks.

The native channel is not a historical rebuild. Google has not published a backfill statement for AI Assistant. Recaps (Digital Applied, Insightland, Seer) report classification is forward-only from May 13, 2026. Custom channel groups, by contrast, can be applied retroactively. That is why you keep both.

Copilot is named in the live default-channel description. That does not mean every Copilot session will show up. Microsoft app surfaces can strip the referrer the same way ChatGPT mobile app does. Name coverage and referrer reliability are different problems. Do not collapse them.

How to build a custom AI channel group (regex, priority above Referral)

Build a custom channel group in Admin / Data display / Channel groups, add an AI Assistants channel with a source regex, then reorder it above Referral. Google documents this path and the reorder rule. Traffic is included in the first matching channel, so if Referral sits above your AI rule, Perplexity stays Referral forever.

Google own Example: AI assistants on the custom channel groups page is the UI path to copy. You must be an Editor or above at the property level.

1. Open Admin / Data display / Channel groups.
2. Click Create new channel group (this copies the default group) or copy an existing group.
3. Add a new channel. Name it AI Assistants.
4. Add a condition. Dimension: Source. Match type: matches regex.
5. Paste a regex. Copy the expression from Google Example: AI assistants page (it names ChatGPT, Gemini, Microsoft Copilot, Claude, Perplexity). A tighter starting pattern many teams use is chatgpt|openai|gemini|gpt|copilot|perplexity|claude.
6. Save the channel. Click Reorder. Drag AI Assistants above Referral. Click Apply, then Save group.
7. In Reports / Acquisition / Traffic acquisition (and User acquisition), set this group as the primary or secondary dimension.

Two limits from the same Google page: a standard property gets 2 custom groups besides the predefined one; a 360 property gets 5. Each group can hold 50 channels. Custom groups apply retroactively in reports, explorations, and audiences going forward. They are not in the BigQuery export schema.

Google sample regex is broad and can match unrelated sources that contain ai. If you want a tighter rule, Seer published case-study pattern (on Seer original page) groups chatgpt, poe.com, copilot, bard, gemini, perplexity, openai, and claude. Update the expression when URLs change. Google says that explicitly.

Run native and custom in parallel for at least two weeks. Native is the Google-maintained list. Custom is the coverage you control, including Perplexity and pre-May 13 history. If the counts diverge, the gap is usually Perplexity, Claude, or a source the native list has not named yet.

If you want the custom group, conversion events, and a 90-day baseline built on your GA4 property, book a 30-minute call.

How to report citations vs clicks vs conversions without mixing Google AI Mode into one number

Report four columns, not one AI total: citations, referred clicks, conversions, and Google AI Mode / AI Overviews. GA4 only sees the click. Prompt logs see the citation. Search Console sees Google generative surfaces. Mixing them into one KPI hides which engine is actually producing pipeline.

Use this split in the weekly report:

• Citations (prompt log). A fixed list of 30-50 buyer prompts, run across ChatGPT, Perplexity, Gemini, and Claude. Record cited-with-link, cited-without-link, mention only, or absent. Citations churn. See why AI citations disappear after 30 days. Deep Research answers are a separate log. See how to get cited in ChatGPT Deep Research reports.
• Referred clicks (GA4). Native AI Assistant channel for Google named engines. Custom AI Assistants channel for Perplexity and the long tail. Break down Session source: chatgpt.com, perplexity.ai, gemini.google.com, claude.ai. Do not roll Google organic into this row.
• Conversions (GA4 key events). Demo, signup, or qualified-lead events on those two channel groups. Last-click will undercount. Add a self-reported How did you hear about us option for ChatGPT / Perplexity / Gemini.
• Google AI Mode and AI Overviews (Search Console). Those clicks stay Organic Search in GA4 by Google definition. Keep them in GSC, including the generative AI performance report if your property has it. Do not add them to the AI Assistant total.

Intent is not uniform across engines. Seer Interactive original client case study (October 1, 2024-April 30, 2025, one site) published conversion rates of ChatGPT 15.9%, Perplexity 10.5%, and Google Organic 1.76%. That is one client GA4, not a law. Use it as a reason to split engines, then measure your own property.

Do not UTM-tag every citation you hope ChatGPT will copy. ChatGPT sometimes appends utm_source=chatgpt.com on source links and sometimes does not. A custom source regex plus the native medium is more stable than hoping models keep your query string. If you already ship partner URLs with UTMs, keep the taxonomy. Do not spray utm_medium=ai across internal links as a measurement strategy.

G2 reviews are an upstream citation source, not a GA4 channel. If ChatGPT is quoting G2 instead of your site, the click may never happen. That work lives in how G2 reviews become ChatGPT citations, then you watch whether those citations ever become chatgpt.com sessions.

How Austin Heaton reports AI search for clients

Austin Heaton reports AI search as four numbers: citations, referred clicks by engine, conversions from those clicks, and Google AI Mode / Overviews in Search Console. The native GA4 channel is the floor for named assistants. The custom group recovers Perplexity and pre-May 2026 sessions. Pipeline is the output, not the session count.

That is how the published client numbers were earned, not estimated:

• 5,130 ChatGPT referrals from Austin AEO work, reported on the about page.
• Lumanu: 566 ChatGPT clicks, 101 conversions inside 60 days.
• Rise: AI search expansion of 575%.
• iSpeedToLead: 7.79% AI citation share, first in its competitive set.

Citation share and ChatGPT clicks are different metrics. iSpeedToLead 7.79% is a visibility number. Lumanu 101 is a conversion number. Rise 575% is a session-growth number. If you squash those into one AI impact slide, you cannot tell whether you have a citation problem, a referrer problem, or a landing-page problem.

The operating cadence is weekly clicks, monthly prompt audits, quarterly conversion quality. Weekly: native AI Assistant vs custom AI Assistants vs Direct. Monthly: the 30-50 prompt set, including whether a citation still has a link. Quarterly: conversion rate by engine against organic search. A free AI SEO audit will tell you whether crawlers can reach the pages you are about to measure. It will not configure GA4.

What to do this week

This week, confirm the native channel is populating, stand up the custom group above Referral, annotate May 13, 2026, and connect one key event. You can prove AEO with a floor number and an honest caveat. You cannot prove it with Organic Search.

1. Open Traffic acquisition. Look for AI Assistant.
2. Create the custom group. Admin / Data display / Channel groups. Source matches regex. Reorder above Referral. Save.
3. Annotate May 13, 2026 on an acquisition chart so nobody reads the new row as a traffic spike.
4. Add one conversion view. Key events for demo, signup, or sales-qualified lead, filtered to native AI Assistant and the custom group, split by Session source.
5. Start the prompt log. Twenty commercial prompts is enough for week one.
6. Keep Google AI Mode out of the ChatGPT total. Put Overviews and AI Mode in the Search Console column.

Then leave it alone for 90 days of clean data before you rewrite the content roadmap off a three-week blip.

If you want Austin Heaton to wire this reporting into an AEO program, not just a dashboard, book a 30-minute call.

Services

Austin Heaton AEO services cover the measurement layer this post describes and the work that feeds it: technical audits, revenue-page content, entity authority, and citation monitoring across ChatGPT, Perplexity, Gemini, and Google AI surfaces. Single-threaded senior ownership. No junior handoff between the regex and the pipeline number.

Read Next:

• Google AI Mode vs AI Overviews
• Why Your AI Citations Disappear After 30 Days
• How to Get Cited in ChatGPT Deep Research Reports
• How G2 Reviews Become ChatGPT Citations

Frequently Asked Questions

Does GA4 track ChatGPT automatically now?

Partly. Since May 13, 2026, GA4 assigns medium ai-assistant and Default Channel Group = AI Assistant when the referrer matches Google list. Google named ChatGPT at launch. The channel still needs a referrer header, is not a published backfill, and does not replace a custom group for engines Google has not named.

Why is Perplexity in Referral?

Because Google live AI Assistant definition names ChatGPT, Gemini, Deepseek, Copilot, or Grok, and does not name Perplexity. Until Google adds it, Perplexity sessions with a referrer follow the Referral rule. A custom channel with a perplexity source regex, placed above Referral, is the fix Google documents.

Why is AI traffic in Direct?

Because many AI clicks never send a referrer. Mobile apps, in-app browsers, and copied URLs arrive as (direct) / (none). Seer ChatGPT table shows search-result clicks can land in Direct. The native channel cannot classify a session with no referrer. Treat Direct as a possible hiding place, not as branded type-in only.

Should we UTM-tag AI citations?

Not as your primary plan. ChatGPT sometimes adds utm_source=chatgpt.com and sometimes does not. Privacy-sensitive answers may omit UTMs. Rely on referrer-based native and custom channels. Keep a clean UTM taxonomy for links you control. Do not UTM-tag internal links hoping models will copy them.

How often to review the report?

Weekly for AI Assistant vs custom AI Assistants vs Direct. Monthly for the prompt log and conversion rate by engine. Quarterly to compare AI-referred conversion quality against organic search and to refresh the regex if new hostnames appear. Ninety days of baseline before you change strategy off the new channel.