How to track ChatGPT traffic in GA4 (and the part GA4 can't see)

People now ask ChatGPT which tool to use before they ask Google. When an assistant recommends you and someone clicks through, that visit is one of the most valuable you get: the person arrives with a specific problem and a recommendation already in hand.

Google Analytics 4 records most of these visits, but files them under Referral next to every blog that ever linked to you, so they are easy to miss. Here is how to pull them out, and where the gaps are.

The quick check: Traffic acquisition

1. In GA4, open Reports → Acquisition → Traffic acquisition.
2. Change the table's first column from "Session primary channel group" to Session source / medium.
3. Type chatgpt in the search box above the table. You should see rows like chatgpt.com / referral, and sometimes chatgpt.com / (not set) when the visit came in through a link ChatGPT tagged itself.
4. Repeat for perplexity, claude, gemini and copilot.

That answers "do I get any?". To watch the number over time you want all assistants in one row.

See every assistant at once

In Explore, start a Free form exploration. Add Session source as a dimension and Sessions, Engaged sessions and your key events as metrics. Then add a filter: Session source, matches regex, and paste:

.*(chatgpt|openai|perplexity|claude\.ai|gemini\.google|copilot\.microsoft|deepseek|grok|meta\.ai|mistral|you\.com|phind).*

The .* at each end makes it work whether GA4 matches the full value or part of it. Add new assistants to the list as they show up in your referrers.

Make AI its own channel

Explorations are fine for a look. For a permanent row in your reports, create a custom channel group so AI sits next to Organic Search and Social instead of inside Referral.

1. Go to Admin → Data display → Channel groups and copy the default channel group.
2. Add a new channel named AI assistants with the condition Source matches regex and the regex above.
3. Drag it above Referral. Channels are matched top to bottom, so if Referral comes first it will claim these visits.
4. Save, then pick your new group in the Traffic acquisition report's channel dropdown.

Custom channel groups also apply to past data, so you can see how AI traffic has grown since you started.

The part GA4 can't see

Assistant apps that drop the referrer

A link clicked in ChatGPT in a browser tab usually sends chatgpt.com as the referrer. The same link opened from a desktop or mobile app can arrive with nothing, which lands it in Direct. ChatGPT adds utm_source=chatgpt.com to many of the links it shows, which helps, but not every link and not every assistant does this.

A practical tell: direct visits that land straight on a deep page such as /pricing or a specific comparison post, from people who then sign up quickly. Nobody types those URLs. If those rise in step with your AI referrals, a share of them is probably AI too.

Google AI Overviews look like ordinary search

Clicks from the AI summary at the top of a Google results page come from google.com like any other result. Standard analytics can't tell them apart from regular organic clicks.

AI crawlers never show up at all

Before an assistant can recommend your page, a bot has to read it. Those bots fetch your pages without running JavaScript, so GA4's tag never fires. The main ones:

To see these you need your server logs, or a tool that receives crawler requests from your server. They are worth watching: a crawler reading your pricing page this week is often how you end up in answers next month.

What to do with the numbers

• Look at landing pages for AI visits. They show which pages assistants cite. Make those pages accurate, current and clear about who the product is for.
• Compare conversion rates. AI visitors often arrive further along than search visitors. If yours convert well, the channel deserves more of your attention than its size suggests.
• Ask new sign-ups. "ChatGPT recommended you" in a how-did-you-hear field catches the visits that arrived as Direct.