How to Track Traffic from ChatGPT in GA4 and Beyond
Track ChatGPT traffic in GA4’s AI Assistant channel, understand what Direct visits hide, collect self-reported attribution, and monitor whether your brand appears in AI answers.
GA4 now puts the ChatGPT visits it can recognize in its own AI Assistant channel, so open Reports > Acquisition > Traffic acquisition, find that row, then search the session source for `chatgpt`. Treat that number as the floor: visits without a referrer land in Direct or Unassigned, so add a “How did you hear about us?” question to your sign-up form to catch the rest.
If prospects keep telling your team they discovered you through ChatGPT and you need a number you can defend this month, combine the visits GA4 confirms with what new sign-ups say about how they discovered you.
Find ChatGPT traffic in GA4
Start with the Traffic acquisition report. GA4’s default channel group includes AI Assistant, so it’s the simplest place to find recognized ChatGPT visits. Clicks from Google AI Overviews and Google AI Mode appear in Organic Search instead, so track AI Overviews in Search Console as a separate job.
Go to Reports > Acquisition > Traffic acquisition.
Keep the default channel group as the primary dimension. GA4 may label it Session primary channel group. Find the AI Assistant row, which combines every recognized assistant rather than ChatGPT alone.
To see ChatGPT on its own, change the primary dimension to Session source / medium, then search for `chatgpt`. Recognized visits show the `ai-assistant` medium, not the old `chatgpt.com / referral`.
Add Landing page + query string as a secondary dimension to see where ChatGPT visitors arrive.
Review Key events to see whether those sessions lead to the actions you care about, such as sign-ups, demos, or purchases.
Weigh Key events over raw sessions. A handful of ChatGPT visits that book demos tells you more than a large number that leave straight away.
No AI Assistant row? Your date range may contain no recognized assistant visits, or your property may use an edited channel group, so use the source search in step 3. GA4 added the channel on 13 May 2026, so earlier dates can show ChatGPT under Referral.
Av. António Augusto de Aguiar 122C 1050-046 Lisboa, Portugal
Minnesota
202 N Cedar Ave, Suite 1 Owatonna, MN 55060, USA
GA4 counts a visit in AI Assistant when its referrer matches a recognized assistant source, including ChatGPT, Gemini, Claude, Copilot, DeepSeek, and Grok.
If someone asks for one AI traffic number, explain that it lives in two places: AI Assistant for ChatGPT and other assistants, and Organic Search for clicks from Google’s AI features.
The channel relies on a referrer, so it misses visits that arrive without one. The Direct and Unassigned section below explains where those visits can go.
Build your own AI channel group if you need more control
Build a custom channel group when you need to compare months before 13 May 2026 or set your own source rules. GA4 applies custom groups to reports retroactively, so older data gets the same labels.
Go to Admin > Data display > Channel groups, create a new group, and add a channel called “AI assistants.” Use the matches regex condition for the sources you want to include, then place the channel above Referral so matching visits are classified first.
The opening `^.*ai` can match any source containing `ai`, so check what it catches in your property before relying on the total. A broad rule can include traffic you didn't intend to count.
Then open Traffic acquisition and switch the primary dimension to your new channel group. You can also use it in explorations, custom reports, and audience conditions. Save the report or comparison once it gives you a monthly view your team can repeat.
If you only need current recognized ChatGPT traffic, use the built-in AI Assistant row. Build a custom group when older data or your own source rules matter more.
Why some ChatGPT visits show as Direct or Unassigned
A ChatGPT visit can land in Direct or Unassigned when it reaches your site without a referrer GA4 can match, for example when someone copies your URL from an answer and pastes it into a browser.
Direct includes visits from saved links or people entering your URL. Unassigned appears when no other channel rule matches the event data. So read GA4's count as your minimum. It holds every ChatGPT visit GA4 could match and none of the ones that arrived without a referrer.
In Traffic acquisition, keep the landing-page secondary dimension from step 4 and read the Direct row. Look for pages receiving Direct traffic you can't explain, especially specific guides, product pages, or comparison pages that people are unlikely to type from memory. Treat those pages as leads, then check them against what people tell you in the sign-up question.
Landing pages can show what people reached, but they can't reveal the exact question someone typed. ChatGPT can rewrite someone’s prompt into its own narrower searches, so the page they land on reflects what ChatGPT searched for, not the words they typed. Use fan-out queries to plan variations of a question, not to claim you can see the searches ChatGPT runs on someone’s behalf.
Ask people where they heard about you
Analytics can't see every ChatGPT visit, so ask the people who arrive. Ask when a prospect books a call, creates an account, requests a demo, or completes a purchase.
Use a required source question with a clear AI option, then add an open-text follow-up. The required question gives you a comparable monthly number. The open-text answers explain what influenced the person.
Ask: “How did you hear about us?” and include an AI option.
Ask people who select AI: “Which AI assistant did you use?”
Ask: “What did you ask it?”
Ask sales prospects: “Did an AI answer influence your research before this call?”
Ask: “How did the AI describe our product compared with competitors?”
Attio's sign-up form, shown above, already lists AI as a source. Whatever wording you use, send the answers to your CRM or a sheet you compare with GA4 each month.
Don't force the survey number to match AI Assistant sessions. The two count different things: GA4 counts visits it could identify, and the survey counts what people remember.
Track whether ChatGPT mentions you, not just whether people click
Traffic shows what happened after someone clicked. It doesn't show whether your brand appeared in a ChatGPT answer when the reader never opened a link.
AI Peekaboo runs the prompts you choose across up to seven AI platforms: ChatGPT, Gemini, Perplexity, Google AI Overviews, Google AI Mode, Microsoft Copilot, and Claude API. It keeps each answer, whether and where your brand appears, sentiment, and cited sources. Its read-only GA4 connection lets you view traffic alongside those mentions.
Put mentions next to visits and you can see which problem you have: ChatGPT isn't naming you, or it names you and people don't click. If your brand is absent from the questions that matter, better attribution won't fix that. If you are mentioned but visits remain low, inspect the answer, the cited page, and the landing-page experience.
If you’re comparing tools for this job, start with these AI brand visibility checkers. AI Peekaboo can't show answers from before you start tracking, so begin with the buyer questions your team already hears on calls.
Put the three numbers in one monthly view
Put AI-answer mentions beside your GA4 and survey figures. Together they let you measure AI visibility without mistaking a mention for a click.
GA4 AI Assistant sessions and key events: confirmed visits from recognized AI assistant referrers and the outcomes those visits produced.
Survey responses that name AI: self-reported discovery that can include visits GA4 classified as Direct or Unassigned.
AI answer mentions and cited sources: whether your brand appears for the questions that lead people to research a solution.
Compare months rather than reacting to one. A rise in AI Assistant sessions means more when key events, survey answers, and brand mentions rise with it.
For a starting point on the third measure, request a free AI visibility report. It’s a one-time report with no card required, not ongoing monitoring.
How we checked this
Last checked: 18 October 2026.
Sources: Google Analytics Help release notes, channel definitions, Traffic acquisition guidance, custom channel groups, and known-bot exclusion; OpenAI Help on ChatGPT search; and articles ranking in Google for this question.
Frequently asked questions
How do I check AI traffic in GA4?
Open Reports > Acquisition > Traffic acquisition and look for the AI Assistant row in the default channel group. To isolate ChatGPT, change the report dimension to Session source / medium and search for `chatgpt`. Add landing page as a secondary dimension and review Key events to see what those visitors did after arriving.
How do I identify AI traffic?
GA4 identifies recognized AI assistant referrers with the `ai-assistant` medium and places them in the AI Assistant channel. It can't put a visit in that channel when the visit arrives without a referrer, because there's nothing to match against its list. Use a sign-up or sales-call question alongside GA4 to capture self-reported AI discovery.
Does Google Analytics track bot traffic?
No, not known bots. GA4 automatically excludes known bots and spiders, you can't switch that off, and GA4 doesn't show how much bot traffic it removed.
Does ChatGPT traffic in GA4 include Google AI Overviews?
No. GA4’s AI Assistant channel excludes Google AI Overviews and Google AI Mode. GA4 classifies visits from those Google features under Organic Search instead. Review both areas if your team uses AI traffic to mean visits from ChatGPT and Google’s AI search features.
Start with your own visibility.
See where your brand appears in AI answers and which competitors get mentioned.
Filipe Lins Duarte
