How to measure AI traffic from ChatGPT and Perplexity in Google Analytics 4

If you want traffic from ChatGPT or Perplexity to show up in Google Analytics 4, you create a dedicated segment or exploration that filters on the source domains chatgpt.com, perplexity.ai, gemini.google.com and copilot. That shows you the clicks that AI answer engines actually pass on to your site. What it does not show you is how often you get cited without anyone clicking. That is the most important limitation to understand before you read anything into the numbers.

AI traffic is visitors who click through from an AI service to your site. AI visibility is how often the AI engines mention and cite you in their answers, regardless of clicks. GA4 measures the first, not the second.

This guide is a follow-up to the deeper walkthrough of what the GA4 report actually shows and does not show. Here you get the exact click-paths, a copyable regex, and a setup you can reuse.

How do I see traffic from ChatGPT?

ChatGPT traffic shows up in GA4 as referral traffic from chatgpt.com. Here is how to find it quickly:

1. Open GA4 and go to Reports in the left-hand menu.

2. Select Acquisition, then Traffic acquisition.

3. Click the dropdown above the table (the default is "Session default channel group") and switch to the Session source / medium dimension.

4. Use the search field above the table and search for chatgpt.

You will typically see rows like chatgpt.com / referral. Those are the visitors who clicked a link in a ChatGPT answer.

If you want Perplexity, Gemini and Copilot in the same view, you are better off building a combined segment rather than searching for one domain at a time. That comes next.

One important clarification: ChatGPT's search function relies heavily on Bing's index, while OpenAI is also developing its own crawler (OAI-SearchBot). So whether you appear in ChatGPT is partly tied to how you are indexed in Bing, but not exclusively.

Setting up a segment for AI traffic in GA4

You get the real picture of AI traffic by gathering all the major answer engines into one filter. In GA4, you do this best in an Exploration (Explore), because that is where you can use segments freely and build tables across sources.

Here is how to set it up:

1. Go to Explore in the left-hand menu and create a Blank exploration.

2. Under Segments, click + to create a new segment. Choose Session segment.

3. Set the condition to the Session source dimension and choose the operator matches regex.

4. Paste in the regex below.

5. Drag in dimensions like Session source / medium and Landing page, and metrics like Sessions, Engaged sessions and Conversions, so you see both the volume and the quality of your AI traffic.

Copyable regex for AI sources

chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot

chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot

chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot

This captures the four most common answer engines in a Norwegian B2B context today. A few tips:

• The period is escaped with \ so that it matches an actual period, not just any character.

• copilot is written without a domain because Microsoft Copilot traffic can come via several hosts. Check your own source rows and tighten it up if you see noise.

• If you want to add more, use | (the OR symbol) between each one: for example, add |you\.com at the end.

Save the segment, and you can reuse it across all your explorations. You can also create a similar channel group or a comparison filter in the standard reports using the same logic, but exploration gives you the most flexibility.

Why GA4 does not show the full AI picture

Here is the distinction that determines how you should read the numbers: GA4 only counts clicks with a recognized referral. That means the report has three big blind spots.

Citation without a click. When ChatGPT or Perplexity summarizes the answer with you as the source, but the user gets what they need without clicking, nothing happens in GA4. You were visible, but invisible in the analytics.

In-app and missing referrer. Traffic from mobile apps or services that do not pass along a referral value often ends up under Direct rather than as an AI source.

Google AI Overviews and AI Mode. Clicks from Google's AI answers are usually counted under Organic Search, not as a separate AI channel. GA4's built-in AI channel does not capture these either.

The takeaway is simple: use GA4 to measure AI *traffic*, but do not confuse it with AI *visibility*. Visibility, that is, how often you are actually cited, has to be measured with other tools and methods. That is the whole point of the work described in the flagship guide to AI visibility for Norwegian B2B.

Why does this distinction matter so much? Because the answer engines overlap surprisingly little. An analysis by Profound of 100,000 prompts across ChatGPT and Perplexity found only 11 percent domain overlap, and between 6 and 16 percent across the major answer engines. So being cited in one engine does not mean you are visible in another. The click figures in GA4 tell you nothing about that coverage.

How to build on the numbers

Once the segment is in place, you can put it to work:

• Track the trend over time. Compare the AI segment month by month. You are looking for direction, not absolute numbers, since the volumes are often small at the start.

• Look at the landing pages. Which pages get AI clicks? That tells you which content the answer engines already consider worth citing.

• Measure quality, not just volume. Add engaged sessions and conversions to the table. AI traffic is often low in volume, but it can be high in intent.

To actually grow both the traffic and the visibility, you have to work on the content itself. Research on generative engine optimization (GEO) from Princeton and the Allen Institute shows that content with citations, statistics and clear source references becomes considerably more visible in AI answers, up to 40 percent more visibility, while keyword stuffing has little effect. Specifically, the study measured that citations gave 41 percent more visibility, statistics 31 percent and source references 30 percent. That is the kind of work we do in our AI visibility service.

Frequently asked questions

How do I see traffic from ChatGPT in Google Analytics 4?

Go to Reports, Acquisition, Traffic acquisition, switch the dimension to Session source / medium, and search for chatgpt. You will then see rows like chatgpt.com / referral, which are clicks from ChatGPT answers. For a combined picture of all your AI traffic, you should instead create a segment with a regex in an exploration.

Which regex do I use to capture all AI traffic in GA4?

Use chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot on the Session source dimension with the "matches regex" operator. It covers ChatGPT, Perplexity, Gemini and Copilot. Extend it with | in front of more domains if you want to add sources like you\.com.

Why do I see so little AI traffic in GA4 even though I know I am being mentioned?

Because GA4 only counts clicks with a recognized referral. If you are cited without anyone clicking, or the traffic comes from an app without a referrer, it does not show up as an AI source. That is the difference between AI traffic (clicks) and AI visibility (citations). GA4 only measures the first.

Do Google AI Overviews count as AI traffic in GA4?

No, usually not. Clicks from Google's AI Overviews and AI Mode tend to land under Organic Search, not as a separate AI channel. As a result, GA4 underestimates how much of your search traffic actually passes through an AI-generated answer.

How do I measure AI visibility when GA4 does not?

Visibility, that is, how often and how you are cited in AI answers, has to be measured with dedicated tools that check the answers to a fixed set of prompts over time, across several engines. Since the engines overlap so little (Profound found only 11 percent domain overlap between ChatGPT and Perplexity), you have to measure each engine separately. This is the core of the flagship guide to AI visibility.

Should I create a dedicated channel group for AI in GA4?

You can, and it makes for cleaner standard reports. But a custom channel group only affects data going forward and cannot be applied retroactively the way a segment in an exploration can. Start with the segment, and consider a channel group once you know the AI traffic is large enough to track on an ongoing basis.