How to Track ChatGPT Traffic in GA4, Plus the Leads and Revenue It Brings
Track ChatGPT, Gemini, Perplexity, Claude and Copilot traffic in GA4 with the AI Assistant channel, then connect it to leads, conversions and revenue in your CRM.
Short answer
GA4 now groups visits from ChatGPT, Gemini, Copilot and other assistants into a default AI Assistant channel (added 13 May 2026). To see leads and revenue, filter key events and purchase revenue by that channel and session source, and store the first-touch source in your CRM, because many AI visits arrive without a referrer and AI Overviews count as organic.
Key takeaways
- Since 13 May 2026, GA4's default channel group includes an AI Assistant channel; recognised referrers get the medium ai-assistant.
- Google's AI Overviews and AI Mode aren't part of that channel: their clicks are counted as Organic Search.
- Visits from AI apps that strip the referrer arrive as Direct, so GA4's AI numbers are a floor, not the total.
- To report leads and revenue, mark form submissions and purchases as key events, then break them down by session source and first user source.
- For B2B leads, capture the first-touch source on the first page view and pass it into your CRM, so a lead can be tied to revenue weeks later.
In this article (6 sections)
If you want to track ChatGPT traffic in GA4, the job got easier in 2026: Google added an AI Assistant channel to GA4's default channel group. But traffic is only half the question. What leadership asks is whether those visitors became leads, customers and revenue, and that needs a little more set-up.
This guide covers both: where AI assistant traffic shows up in GA4, how to add platforms GA4 doesn't recognise, how to report key events and revenue by AI source, and how to carry the source into your CRM so a lead from ChatGPT can be traced to a closed deal. It's the method I use when I measure AI search visibility for clients.
Where ChatGPT traffic shows up in GA4 now
On 13 May 2026, Google added AI Assistant to GA4's default channel group. When GA4 recognises a referrer from an AI assistant, it sets the medium to ai-assistant and the channel to AI Assistant. Google's description names sources such as ChatGPT, Gemini, DeepSeek, Copilot and Grok.
To see it:
- Open Reports → Acquisition → Traffic acquisition.
- Keep the primary dimension as Session primary channel group, and find the AI Assistant row.
- Add Session source as a secondary dimension to split it by platform: chatgpt.com, gemini.google.com, copilot.microsoft.com and so on.
If the row isn't there, either the rollout hasn't reached your property yet or you haven't had recognised AI traffic in the date range. Before May 2026, the same visits were usually filed under Referral, so older comparisons need the custom method below.
What GA4 still misses
| Visit | Where GA4 puts it | Why |
|---|---|---|
| Click from ChatGPT, Gemini, Copilot in a browser | AI Assistant | Recognised referrer |
| Click from an AI tool GA4 doesn't recognise | Referral | Not on Google's list |
| Click from an AI app that strips the referrer | Direct | No referrer is sent |
| Link with utm_source=chatgpt.com but no medium | Can land in Unassigned | Source set, medium missing |
| Click from Google AI Overviews or AI Mode | Organic Search | Counted as Google search |
| Someone reads an AI answer, then searches your brand | Organic or Direct | No click from the assistant |
So treat the AI Assistant number as a floor. The real influence of AI answers is larger, and part of it shows up as growth in branded search and direct visits.
Add platforms GA4 doesn't recognise: a custom channel group
If you see AI tools sitting in Referral, build a custom channel group:
- Go to Admin → Data display → Channel groups → Create new channel group (you need Editor access).
- Add a channel named AI assistants (all) with the condition Session source matches regex:
.(chatgpt\.com|chat\.openai\.com|openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|deepseek\.com|grok\.com|meta\.ai).Then drag the channel above Referral, because GA4 applies rules top to bottom, save, and select this channel group in the Traffic acquisition report.
Custom channel groups also apply to historical data, which makes before-and-after comparisons possible. Check the regex every quarter: new assistants appear and domains change.
How to see leads and conversions from ChatGPT
Traffic tells you very little on its own. To report outcomes:
- Mark the actions that matter as key events: form submissions, demo or call bookings, sign-ups, WhatsApp clicks, phone clicks (Admin → Data display → Key events).
- In Traffic acquisition, choose your key event in the Key events column filter, keep the channel group as the dimension, and add Session source.
- Compare the session key event rate for AI Assistant against Organic Search and Paid Search.
| Metric | Where | What it tells you |
|---|---|---|
| Sessions and engaged sessions | Traffic acquisition, by AI channel and source | Volume and quality of AI visits |
| Key events (leads) | Same report, key event filter | Leads that came in during an AI-referred session |
| Session key event rate | Same report | Whether AI visitors convert better or worse |
| First user source | User acquisition report | Whether AI introduced the visitor, even if they converted later |
| Landing page | Add as secondary dimension | Which of your pages AI assistants send people to |
How to see revenue from ChatGPT and other AI assistants
For ecommerce, with GA4 ecommerce tracking in place, the Traffic acquisition report already shows Total revenue and purchases by channel. Filter to AI Assistant and add Session source. For a fuller view, the Advertising → Attribution reports show how AI sessions contribute to conversions across several visits, not just the last one.
For lead generation and B2B, revenue lives in your CRM, so GA4 alone can't show it. The method:
- Capture the source on the first page view. Store the referrer, landing page and any UTM values in a first-party cookie or local storage, because the original referrer is gone by the time someone fills in a form.
- Pass it into the form as hidden fields: first-touch source, first-touch medium and landing page.
- Write it onto the contact and the deal in the CRM (HubSpot, Salesforce, Zoho or others) and keep it unchanged.
- Report revenue by first-touch source in the CRM: deals won and value where the first touch was chatgpt.com, perplexity.ai and so on.
- Optionally send offline conversions back to GA4 or your ad platforms when deals close.
Watch for domain changes along the way. A checkout or booking on a separate domain can break the chain unless cross-domain tracking is set up.
A monthly AI traffic report leadership will read
| Line | Source |
|---|---|
| AI Assistant sessions and trend | GA4, Traffic acquisition |
| Leads (key events) from AI, and conversion rate vs organic | GA4 |
| Revenue or pipeline with AI as first touch | CRM (B2B) or GA4 ecommerce |
| Top landing pages from AI | GA4, landing page dimension |
| Share of answers that mention you for your priority prompts | AI visibility tracking (outside GA4) |
| Branded search impressions trend | Search Console |
The last two lines matter because GA4 only sees clicks. To see how often assistants mention you without a click, you need prompt-based tracking; my free AI visibility tracking template covers the method, and ranking in ChatGPT covers how to grow those mentions. If you'd rather automate the report, see automated SEO reports.


