How to track ChatGPT traffic

What a ChatGPT click looks like

When someone clicks a link in a ChatGPT answer, two things can tell your analytics where they came from:

1. The UTM tag. OpenAI's publisher FAQ says ChatGPT automatically adds utm_source=chatgpt.com to referral URLs, so a citation link arrives as https://yoursite.com/page?utm_source=chatgpt.com. A tag in the URL survives even when the browser sends no referrer.
2. The referrer. Clicks from the ChatGPT website usually carry chatgpt.com as the referring site. Older links can still say chat.openai.com.

Every common analytics tool reads at least one of these, so in most setups ChatGPT traffic is already being counted. The question is where it's filed.

What you won't see

Some ChatGPT influence never reaches your analytics as ChatGPT:

• Copied links. Someone copies your URL out of an answer and pastes it into a browser or a chat. No tag, no referrer: it's a direct visit.
• Mentions without a link. ChatGPT names your product, the reader searches for it on Google a minute later. That visit is Organic Search, or Direct if they typed the address.
• Some app clicks. A link opened from a mobile app can arrive without a referrer. If the link was a tagged citation, the UTM tag still names ChatGPT; if not, it's Direct.
• Answers nobody clicks. If the reader got what they needed from the answer, there's no visit to measure at all.

So treat the ChatGPT number as a floor. A rise in branded searches and direct visits to deep pages, at the same time as ChatGPT referrals grow, is often the same effect.

In Google Analytics 4

Google added an AI Assistant channel to GA4's default channel group in 2026. Its definition covers sources like ChatGPT, Gemini, DeepSeek, Copilot and Grok: when the referrer matches Google's list, GA4 sets the medium to ai-assistant and the campaign to (ai-assistant). Google's AI Overviews and AI Mode are excluded and stay in Organic Search. Look under Reports → Acquisition → Traffic acquisition with Session default channel group as the dimension.

The default channel isn't retroactive, and Google doesn't publish its full list of assistants. A custom channel group fixes both: it applies to past data and you decide what's in it.

1. Admin → Data display → Channel groups → Create new channel group (needs Editor access). It starts as a copy of the default group.
2. Add new channel, name it "AI assistants", and add a condition: Source matches regex:

.*(chatgpt\.com|chat\.openai\.com|perplexity|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|deepseek|grok\.com|meta\.ai|mistral\.ai|you\.com|phind\.com|poe\.com|kimi\.com).*

3. Reorder so the new channel sits above Referral (traffic goes to the first channel it matches), then Save group.
4. In Traffic acquisition, switch the dimension to your new channel group.

Standard properties get two custom channel groups. To see what this traffic does, build a free-form exploration with Session source as rows and Sessions, Key events and Purchase revenue as values. Revenue only appears if you send purchase events, which is the hard part (more below).

In Plausible, Fathom, Umami and similar tools

Privacy-first tools list chatgpt.com as a referrer source, and they read utm_source too, so ChatGPT shows up in the Sources report without setup. Filter by it to see which pages ChatGPT visitors land on. What they won't show without extra work is money: revenue needs events you send yourself.

In your server logs: crawlers, not visitors

OpenAI runs several user agents, and none of them is a visitor:

A ChatGPT-User fetch in your logs means ChatGPT read the page for someone, which is a useful signal on its own, but it isn't a visit. JavaScript analytics never counts these fetchers, and DataBull's server-side bot filter drops them too. If you want ChatGPT to cite you, make sure robots.txt and your firewall let OAI-SearchBot in.

Does ChatGPT traffic buy?

That's the number that matters, and it's the one most setups can't show. GA4 can, if you send a purchase event with a value and currency from your checkout and keep the session attached through a hosted payment page; here is what that takes. Privacy-first tools can if you send revenue goals yourself.

DataBull starts from the payment instead. Connect Stripe, Polar, Dodo Payments or Creem with a key, add one script tag, and every sale is credited to the visit that brought the buyer. ChatGPT gets its own row in the AI channel with:

• visitors, sales, revenue and conversion rate, next to Search and Social;
• lifetime value of the customers it first brought in, renewals included;
• how many days and visits those buyers took before paying, and which source closed the sale.

The same works for Claude, Perplexity, Gemini and Copilot; see AI traffic analytics for the full list.

A five-minute monthly check

Whatever tool you use, the same short routine tells you whether ChatGPT matters for your site yet:

1. Count it. Visitors from chatgpt.com this month against last month. Small numbers are normal; the trend is what you're watching.
2. See where they land. The landing pages of ChatGPT visitors are the pages ChatGPT cites. Those pages are worth keeping accurate, because their text is what gets quoted.
3. Compare quality. Pages per visit, reading time and conversion rate for ChatGPT visitors against Organic Search. A visitor who arrives from an answer that recommended you often behaves differently from one who clicked a search result.
4. Follow the money. Sales and revenue credited to ChatGPT, and, if you sell subscriptions, how long those customers stay.
5. Watch the side effects. Branded searches and direct visits to deep pages. When those rise together with ChatGPT referrals, part of that growth is likely ChatGPT too.

Tag the links you control

When you paste your own link into a custom GPT, a ChatGPT project or a shared chat, add a tag so it's counted even without a referrer: ?utm_source=chatgpt&utm_campaign=my-gpt or simply ?ref=chatgpt. The same habit helps everywhere the referrer gets lost; the tweet guide shows how.

Checked in October 2026 against: OpenAI: Publishers and developers FAQ, OpenAI: crawlers and user agents, Google Analytics: traffic-source dimensions, Google Analytics: custom channel groups. Spotted something out of date? Tell us.