Short answer: mostly, yes. When someone clicks a link in ChatGPT, Perplexity, Gemini, Copilot or Claude, the visit usually shows up in Google Analytics 4 as referral traffic, with the assistant's website as the source (for ChatGPT, chatgpt.com). Three gaps remain, covered below. The biggest: clicks from Google's own AI Overviews and AI Mode can't be separated from normal Google searches anywhere.

See it in five minutes

  1. In GA4, open Reports, then Acquisition, then Traffic acquisition.
  2. Change the table's first column from "Session primary channel group" to Session source / medium.
  3. In the search box above the table, type chatgpt. Then try perplexity, gemini, copilot and claude.

You'll see rows like chatgpt.com / referral. That is your ChatGPT traffic: sessions, engaged sessions and key events, the same as any other source.

Make GA4 sort it for you

Searching every time gets old. A custom channel group puts every AI assistant into one "AI assistants" channel that shows up in your normal reports. Google's steps, in short:

  1. Go to Admin, then under Data display choose Channel groups. (You need Editor access.)
  2. Click Create new channel group. This starts from a copy of the default group.
  3. Click Add new channel and name it AI assistants.
  4. Add a condition: Source, matches regex, with this pattern:
.*(chatgpt\.com|chat\.openai\.com|perplexity|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai).*
  1. Save the channel, then click Reorder and move it above Referral. This is the step people miss. GA4 puts each visit in the first channel it matches, so if Referral comes first, it catches all of these visits and your new channel stays empty.
  2. Save the group. In Traffic acquisition, switch the table to your new channel group.

Two limits worth knowing: a standard GA4 property can have only two custom channel groups (plus the default), and the group applies to past data too, so you can see history right away.

The three gaps

1. Some AI visits show up as "Direct." When an app doesn't pass along where the visitor came from, GA4 has no source to show. Visits from AI apps on phones are the usual suspects. You can't recover these, so treat your AI channel as a minimum, not the full number.

2. Google's AI Overviews and AI Mode are invisible as their own channel. Clicks from them arrive as normal Google organic traffic. Search Console doesn't split them out either. Google says AI features "are included in the overall search traffic in Search Console" and are "reported on in the Performance report, within the 'Web' search type." There is no filter for them.

3. AI that never sends a click. When an assistant answers a question using your page and the person doesn't click, nothing reaches GA4 at all. That influence is real, but no analytics tool can count it.

What to do with the number

  • Look at engagement, not just sessions. Compare engaged sessions and key events for the AI channel with organic search. If AI visitors convert well, the pages they land on are worth improving.
  • Check which pages AI sends people to. Add Landing page as a second dimension. Those pages are the ones assistants trust; keep them accurate and current.
  • Watch the trend, not one week. AI referrals are still small for most sites and jump around from week to week.