How to see ChatGPT traffic in your analytics

Short answer

In Google Analytics 4, open Traffic acquisition and look for source chatgpt.com, or use the AI Assistant channel. Also check campaign source for utm_source=chatgpt.com. In cookieless tools, open Referrers or the AI assistants view and filter the same host. Attributed ChatGPT traffic is a floor: when the tag and the referrer are both missing, the visit usually lands in Direct.

Two different “ChatGPT” signals

People mix up two things that look similar in a dashboard and mean something different for your content.

• AI referrals are human visits. Someone asked ChatGPT a question, clicked a link, and landed on your site. The browser may send a referrer from chatgpt.com, and many ChatGPT links also carry utm_source=chatgpt.com.
• AI crawlers are bots such as GPTBot, OAI-SearchBot or ChatGPT-User. They fetch HTML for training, search indexes or a live answer. They do not run your analytics script, so a script-only setup never counts them.

This article is about referrals: people from ChatGPT (and, with the same method, Perplexity, Claude and other assistants). Crawlers need an edge or server log path; see our AI report and edge collection pages for that side.

How ChatGPT marks a click

OpenAI’s help centre states that ChatGPT can add utm_source=chatgpt.com to referral URLs so destination sites can attribute the visit. That tag travels in the URL even when the browser withholds the referrer, which is why it became the main signal many teams rely on.

The referrer still matters. A desktop click that sends Referer: https://chatgpt.com/… lets any analytics tool that reads the referrer host put the visit under ChatGPT without depending on UTMs. In-app browsers and some “open in new tab” paths are less reliable.

Practical rule: treat utm_source=chatgpt.com and a chatgpt.com referrer as two independent proofs. Count a visit as ChatGPT when either is present. Do not invent a third proof by guessing that Direct spikes “must be” ChatGPT.

How to find it in GA4

1. Go to Reports → Acquisition → Traffic acquisition.
2. Set the primary dimension to Session source / medium (or Session source) and search for chatgpt.com.
3. Check the AI Assistant default channel. Google documents this channel for sessions whose medium is ai-assistant, including assistants such as ChatGPT when the referrer matches its list. Google’s own AI Overviews and AI Mode stay under Organic Search, not AI Assistant.
4. Open Reports → Acquisition → Campaigns (or an Exploration) and confirm sessions whose Campaign source is chatgpt.com from the UTM tag.
5. Segment a conversion or key event by that source. A source with visits but no outcomes is still useful; it tells you which answers send curious readers versus buyers.

If ChatGPT is missing while you know links were clicked, compare Direct traffic on the same landing pages and the same dates. A rise in Direct next to a fall in chatgpt.com is a classic sign that the tag or referrer was stripped, not that people stopped clicking.

What broke in October 2026

Around 9 October 2026, after a ChatGPT interface change, many cited links stopped carrying utm_source=chatgpt.com. Reporting at the time also described links opening with noreferrer, which removes the referrer. With neither signal, GA4 and every other client-side tool filed those visits as Direct. Industry coverage (Search Engine Journal and several measurement vendors) described sharp drops in attributed ChatGPT traffic while Direct on the same URLs rose.

A partial fix followed mid-month: the tag returned on a growing share of cited links, but not always on every surface (product cards and some answer layouts stayed untagged in early checks). The lesson for dashboards is durable even after the fix:

• Annotate the incident window in GA4 so week-on-week ChatGPT charts are not misread as demand collapse.
• Keep measuring visibility and citations (where your pages appear in answers) separately from click referrals.
• Preserve query strings on your own redirects. A trailing-slash or HTTP→HTTPS redirect that drops the query string destroys the UTM proof on arrival.

How cookieless analytics sees the same visits

Cookieless tools do not need a cookie to attribute a ChatGPT visit. They read the landing URL (including UTM tags your script keeps) and the referrer host, then group assistants into an AI channel. Plausible ships an AI Assistants channel; Fathom added an AI tab under Referrers in October 2026; others list chatgpt.com under referrers.

Wholetally follows that pattern for referrals: ChatGPT, Perplexity, Claude, Gemini, Copilot and similar hosts form one AI assistants channel, and utm_source=chatgpt.com (and similar tags) still count when the referrer is empty. Crawlers are counted apart, at the edge, so GPTBot never inflates “visitors from ChatGPT”. Details and the crawler list live on the AI report page; a factual matrix versus GA4, Plausible, Simple Analytics and Fathom is on Compare.

A short verification checklist

1. From a clean browser profile, click a ChatGPT citation to your site. Copy the first landing URL before redirects settle.
2. Confirm whether utm_source=chatgpt.com is present, and whether DevTools shows a chatgpt.com referrer on the document request.
3. Follow every redirect you own. If a redirect drops the query string, fix it before you change analytics tools.
4. Confirm the pageview your analytics tool stores still contains the path plus UTM tags (Wholetally keeps path and UTM tags; other query parameters are dropped on purpose).
5. In the dashboard, find the same visit under AI assistants / chatgpt.com within a few minutes.

What you still cannot see

No analytics product can promise a complete count of “everyone who discovered us in ChatGPT”. Three gaps remain even with a perfect setup:

• Answers without a click. If the model quotes you and the reader never leaves the chat, there is no visit to attribute.
• Stripped signals. No tag and no referrer means Direct (or your tool’s equivalent). Guessing the share that “should” have been ChatGPT is not measurement.
• Crawlers versus people. Training and search bots reading your pricing page are not referrals. Counting them as visitors makes AI traffic look larger and less useful. Keep them in a separate report.

For agencies and freelancers

If you manage analytics for client sites, put ChatGPT (and other assistants) in the weekly report next to organic search, not buried in Referral. Clients ask whether AI is replacing Google for their niche; a separate AI assistants line answers that without a custom GA4 exploration. When you install the script through a first-party proxy on the client’s domain, the same referral and UTM rules apply: you are not giving up ChatGPT attribution by going cookieless.

Keep crawler data off the client-facing visitor chart. A spike in GPTBot on a new guide is useful for the content team; it is misleading in a “sessions this week” slide. Edge collection is what makes that split possible on sites you already host on Cloudflare or Vercel.

What to do next

If you only need a weekly ChatGPT number in GA4, the Traffic acquisition + AI Assistant path above is enough. If you also want Perplexity and Claude in one channel, UTM fallbacks when referrers disappear, and a separate view of which AI crawlers read which pages, use an analytics tool that was built for that split. Wholetally’s AI report does both; edge collection is required for the crawler side.

New accounts get a 30-day trial, no card needed. Start on Pricing, or go straight to the app sign-up linked from that page.

Wholetally is cookieless web analytics with an AI report, edge collection and revenue per source. Built in the Netherlands. This article is general information, not legal advice.