ChatGPT Traffic in Google Analytics: Where It Shows

A ChatGPT visit shows up in Google Analytics 4 as a separate "AI Assistant" row if GA4 recognizes the referrer, as Referral if it does not, or as Direct if no referrer reaches the browser at all. Open Reports, then Acquisition, then Traffic acquisition, and check all three before you decide how many bookings an AI chat actually sent you.

Quick answer

• In GA4, open Reports > Acquisition > Traffic acquisition and set the primary dimension to Session default channel grouping.
• Look for a row named AI Assistant, the channel Google added on May 13, 2026 (Google, checked 2026-10-04) for sources such as ChatGPT, Gemini, Deepseek, Copilot and Grok (Google, checked 2026-10-04).
• If an assistant you care about turns up under Referral instead (Google never names Perplexity for this channel), build your own channel under Admin > Data display > Channel groups with a regex condition.
• A visit that arrives with no referrer at all, such as a link copied out of a chat into a new tab, lands under Direct instead and needs a different fix.
• Add your booking key event as a check on every one of these rows, and ask new clients how they heard about you, so a visit GA4 never saw still gets counted somewhere.

Where in GA4 does a ChatGPT visit actually show up?

Sign in to Google Analytics, click Reports in the left menu, then Acquisition > Traffic acquisition (Google, checked 2026-10-04). This report groups every visit by where it came from, and its default column is Session default channel grouping, a set of rule-based buckets such as Direct, Organic Search or Referral that GA4 assigns to each session.

Two other dimensions in the same dropdown matter here. Session source names the specific publisher, such as "google" or "youtube," rather than the bucket it falls into, and Session source / medium shows the publisher and the type of traffic (search, referral, an ad) together. Switch to either one with the dimension dropdown above the table, and use the search bar above it to pull up one value at a time, the way Google's own instructions search "google / organic" to isolate unpaid Google visits (Google, checked 2026-10-04). The same search box finds an assistant's domain, if one was passed as a referrer.

Does Google Analytics have a built-in channel for AI assistants?

Yes. Google's changelog dates it May 13, 2026, and describes it plainly: "Google Analytics now provides a dedicated way to measure and analyze traffic originating from popular AI assistants," naming ChatGPT, Gemini and Claude as examples of what it catches (Google, checked 2026-10-04). On a matching visit, GA4 rewrites the medium (the kind of traffic a session is tagged with) to "ai-assistant," files the session under a channel named AI Assistant, and sets the campaign name to "(ai-assistant)."

The channel's own definition is narrower in its wording: "The medium is set to 'ai-assistant' and the campaign is set to '(ai-assistant)' if the referrer matches a list of AI Assistants," and it names ChatGPT, Gemini, Deepseek, Copilot and Grok as the examples on that list (Google, checked 2026-10-04). Google does not publish the complete list anywhere I could find. The same page says the channel "excludes Google's AI Overviews and AI Mode," the answers Google shows inside its own Search results, and counts clicks from those under Organic Search instead. Claude appears in the changelog's examples but not the definition's, and Perplexity in neither, so treat both lists as samples, not as a guarantee about any one assistant.

Why do some AI visits still read as Direct or Referral?

Two gaps sit between "a client used an assistant" and "GA4 filed it as AI Assistant."

The first is the matching list itself. An assistant GA4 does not recognize yet still carries a referrer, so the session falls back to Referral, GA4's bucket for any visit whose medium is "referral," "app" or "link" (Google, checked 2026-10-04). That is where to look for any assistant Google's list does not match, Perplexity included if your reports show it there.

The second gap is the referrer itself going missing. GA4 calls a session Direct when the source exactly matches "(direct)" and the medium is "(not set)" or "(none)" (Google, checked 2026-10-04). Nothing told GA4 where the visit came from. Google counts someone who enters your address directly in that bucket (Google, checked 2026-10-04), and a link copied out of a chat into a new tab, or an address read in an answer and typed by hand, arrives the same way: a real visit with nothing for GA4 to label. Google Analytics direct traffic covers the other causes of that same bucket, so rule those out before you credit or blame an assistant for your Direct numbers.

How do you build your own channel for the assistants GA4 misses?

A custom channel group lets you add rules GA4's own list does not cover yet. Go to Admin, then under Data display click Channel groups, then Create new channel group, which starts as a copy of the default group (Google, checked 2026-10-04).

Google's own tutorial walks through this case: add a new channel, name it something like "AI assistants," add a condition, and select "matches regex" (a pattern that matches many URL variants at once, rather than one exact text string). It names ChatGPT, Gemini, Microsoft Copilot, Claude and Perplexity as popular assistants and gives a ready pattern built from terms such as "openai," "chatgpt," "gemini," "copilot" and "perplexity" (Google, checked 2026-10-04). Because GA4 files a visit under the first channel whose rule matches, move your new AI channel above Referral in the list, as Google instructs, or the Referral rule will still catch a matching visit first.

Google's example does not say which field to match against; Source, one of the fields it lists as supported, is the one that names where a visit came from. Its pattern is also broad (it includes a bare "gpt" term and an opening "ai" term), so once data arrives, add Session source as a secondary dimension and confirm every source the channel caught is really an assistant.

A standard property can hold two custom channel groups beyond the default one, each with up to 50 channels, and creating or editing one needs the Editor role or above on the property (Google, checked 2026-10-04). Once saved, pick your new group as the primary or secondary dimension in Traffic acquisition the same way you would the default one.

How do you know an AI visit actually turned into a booking?

A channel row only tells you a session happened. Whether it booked is a separate column. GA4 key events for leads covers setting up that marker; once it exists, the Traffic acquisition report's Key events column, which counts how many times users triggered a key event, sits next to every channel row, AI Assistant included (Google, checked 2026-10-04).

Illustrative: the salon and every figure below are made up for this post, and none comes from a real GA4 property or a client.

Take an imaginary single-location hair salon that books through a form on its own site. Its Traffic acquisition report for last month shows:

The booking rate for the recognized AI Assistant channel is bookings divided by sessions: 5 / 34 = 0.147, about 15 percent. The same division works for any channel row. That rate covers only visits Google's list matched; the 11 Referral sessions and the 8 front-desk answers are partial views of the same clients, not numbers to add together, since one person can show up in more than one row.

Can your front desk catch the visits no analytics tool sees?

A client who acts on an AI assistant's answer does not always click a link GA4 can see. The assistant may have been asked out loud, the answer read off someone else's phone, or a screenshot passed around a group chat. None of that reaches a browser session, so no channel, built-in or custom, will ever hold it.

Andrea Lechner-Becker, Chief Strategy Officer at GNW Consulting, names the low-tech fix on the B2B Marketers on a Mission podcast: self-reported attribution, asking "How did you hear about us?" on the form and on the first call (YouTube, checked 2026-10-04). I would make it a fixed list of answers rather than an open text box, with an AI assistant as its own option, logged the same way the front desk already logs "Google" or "a friend." It will never match GA4's count one for one, since a client can both click through and later not recall which assistant it was, but it is the only count that survives a visit GA4 could not see in the first place. How to get ChatGPT to recommend your business covers the other half of this, earning that mention before you can measure it.

What should you ask whoever manages your GA4 property?

• Does the Traffic acquisition report show an AI Assistant row at all, and since what date?
• Which rows under Referral have a source value that looks like an assistant's domain rather than a normal website?
• Is the booking key event added as a column on the AI Assistant row, not just counted separately?
• If an assistant you want to track is missing, who has Editor access to add a custom channel for it?
• Does the front desk's "how did you hear about us" list already include an AI option, or only "Google" and "a friend"?

Ask for a screenshot of the Traffic acquisition report with the AI Assistant row visible, not a summary number. A missing row means no session in that date range matched Google's list, not that no client used an assistant; the Referral rows and the front-desk answers still apply.