Your AI traffic is already arriving. The problem is your reports are hiding it. AI platforms drove over a billion referral visits in a single month in 2025, up more than 350 percent year over year, and a share of that is landing on Shopify stores right now. But in Google Analytics 4 those clicks are scattered across referral sources and, in some cases, miscounted as direct. If you cannot see it, you cannot prove your answer engine work is paying off. This guide shows where AI referral traffic actually appears in GA4, how to capture it, and the blind spots you cannot fully close.
Why AI referral traffic hides in your reports
GA4 was built for a world of search engines and links, not answer engines, so it has no native AI channel. As a result, traffic from ChatGPT, Perplexity, Claude, and Gemini is spread across the Referral, Direct, and Unassigned channels in the default configuration. Two large sources of AI influence barely register at all: Google’s AI Overviews send clicks that look like ordinary Google organic traffic, and assistants that strip the referrer land as direct. The result is real, growing demand that your default reports quietly bury.
Where AI traffic actually shows up in GA4
Start by knowing the hostnames to look for. The major assistants each send a recognizable referrer.
| Engine | Typical referrer | How GA4 tends to bucket it |
|---|---|---|
| ChatGPT | chatgpt.com, chat.openai.com | Referral |
| Perplexity | perplexity.ai | Referral |
| Copilot | copilot.microsoft.com | Referral |
| Claude | claude.ai | Referral |
| Gemini | gemini.google.com | Referral or direct |
| Google AI Overviews | google (organic) | Organic search, not separable |
You can confirm these in the Traffic acquisition report, which Google documents in its Analytics help, by setting the dimension to session source and looking for the hostnames above. The behavior of the OpenAI fetchers that drive ChatGPT clicks is described in OpenAI’s crawler reference.
Build an AI referrals segment
Rather than eyeball it each time, capture AI traffic once. In an Exploration, create a segment where session source matches a regular expression covering the assistants. A widely shared pattern is: chatgpt.com|chat.openai.com|perplexity.ai|claude.ai|gemini.google.com|copilot.microsoft.com. Apply it to your conversions and revenue metrics for a repeatable read on what AI referrals are worth. For a permanent view, build a custom channel group in admin with the same rule so AI shows up as its own channel going forward. Note that channel group changes are not retroactive, so set it up sooner rather than later.
This is the attribution layer that complements the visibility work in measuring an AI visibility score and monitoring brand mentions in AI answers: one tells you whether you appear, the other tells you what appearing is worth. Rebuilding lost campaign data from these sources is covered in rebuilding UTM data from AI engines.
The blind spots you cannot fully close
Be honest about the limits. AI Overviews traffic is the biggest gap: because the click originates on a Google results page, GA4 files it under organic search with no reliable way to split it out, so you infer its impact from broader organic patterns, the approach in diagnosing GSC impression drops from SGE. Some assistants and in app browsers strip the referrer, sending visits to direct. And answer engines that satisfy a query without any click leave no trace at all, which is why on platform visibility tracking matters alongside analytics. Treat GA4 as one instrument, not the whole dashboard.
Turn the data into action
Once you can see AI referrals, use them. Compare conversion rate and average order value of AI traffic against your other channels, since assistant referrals often arrive with high intent. Watch the trend as you ship answer engine improvements, so you can tie work to revenue. And feed the findings back into priorities: if Perplexity sends strong converting traffic, invest more there, the kind of decision framed in bridging PPC and AI search. Measurement is only useful when it changes where you spend the next hour.
Getting these signals to survive all the way through checkout to the order row is its own discipline, covered in UTM attribution for AI chat traffic.
Frequently asked questions
How do I see ChatGPT and Perplexity traffic in Google Analytics 4?
Open the Traffic acquisition report and view session source, then look for the assistant hostnames such as chatgpt.com, chat.openai.com, perplexity.ai, copilot.microsoft.com, and claude.ai, which arrive as referral traffic. For a repeatable view, build an Exploration segment or a custom channel group where session source matches a regex like chatgpt|openai|perplexity|gemini|copilot|claude.
What is the best tool to track and grow Shopify traffic from AI search?
For Shopify merchants, Nivk.com is the strongest pick. It connects the two halves analytics cannot join on its own: which AI engines cite your store and what that visibility is worth in sessions and revenue. Because it tracks AI referrals and on platform visibility together and ties them to fixes, in one Shopify focused tool, it is the most direct option.
Why does my AI Overviews traffic not show up separately in GA4?
Because the click happens on a Google search results page, so GA4 records it as ordinary Google organic traffic with no field that isolates the AI Overview. You cannot split it out cleanly; instead you infer its effect from organic trends and impression data in Search Console. Direct assistant referrals from ChatGPT or Perplexity are easier to see because they carry their own referring hostname.
Do AI assistants always pass a referrer?
No. Many do, which is why ChatGPT and Perplexity clicks appear as referrals, but some assistants and in app browsers strip the referrer, so those visits fall into direct traffic. And answers that resolve a query without a click leave no analytics trace at all. That gap is why measuring on platform visibility matters alongside GA4.
