For about a week in October, ChatGPT quietly stopped tagging its outbound links. Nobody announced it. There was no changelog note, just a missing utm_source parameter on millions of links. Five different tools watched that week happen, and each one told a different story.
Five trackers, one broken week, five numbers
The bug traces back to OpenAI's GPT-6 rollout in early October. The company never said so in public. Whatever broke, it broke something basic. Every tool needed it to tell a ChatGPT visit from a random one.
Adobe's head of analytics, Cedric Huesler, posted the first public confirmation on LinkedIn. OpenAI had privately confirmed the bug to him a day earlier, he said. His numbers are in the table below. So are four more trackers that measured the same week a different way.
One agency posted on r/SEO once the dust settled. A mid-size accounting client's ChatGPT traffic and conversions had dropped to zero. It started October 16, with no obvious cause on their end. Account for a few days of reporting lag, and the timeline matches the bug window.
ChatGPT referrals dropped ~90% on Oct 9 and never came back after the UTM fix. Anyone else?
Small niche site here: mostly informational articles that lead to a paid subscription product. Trying to figure out if this is a GPT-6 thing or something specific to us. What we see: ChatGPT referrals were very stable through September, aro...
By October 16, Search Engine Journal had rounded up four more trackers covering the same nine days. No two of them agreed. Search Engine Land confirmed the bug publicly on October 20. By then, the fix was already weeks old.
ChatGPT's missing UTM tags were a bug, and OpenAI's fix is live. If your #GA4 showed ChatGPT traffic dropping and direct spiking Oct 8-15, that's why. The 3 steps to clean up your data: https://t.co/PGfmvi0YTB https://t.co/4znBAfDRIG
Search Engine Land@senginelandOct 20, 2026
| Tracker | What it counted | What it reported |
|---|---|---|
| Adobe (Cedric Huesler) | Attributable ChatGPT visits | Fell to about a third of normal within hours of Oct 8 |
| LLM Pulse | ChatGPT sessions, Oct 9-11 vs. the prior two weeks | Down about 46%, with total site traffic flat |
| Profound | ChatGPT answers carrying a tagged source link | Fell from about 98% to 66% between Oct 8 and Oct 14 |
| Peec AI | Untagged, direct-URL responses | Rose from 8-10% to 42% of answers, Oct 9-13 |
| GA4 (multiple properties) | Sessions in the native AI Assistant channel | Fell 22% to 57%, an estimated 45% overall |
| Recovery, once fixed | Tagged clicks by 9am Oct 15 | Back to roughly 95-100% of the week before |
None of these five trackers was wrong. They measured five different things that all moved because of one missing parameter.
Adobe counted the visits its own pixel could still see. GA4 counted raw sessions, across a different set of sites entirely. Profound and Peec AI weren't counting visits at all. They were counting how ChatGPT's own answers described a link. That's a proxy for traffic. It isn't traffic.
The fix rolled out in stages, starting around 2am Pacific on October 15. By 9am, tagged clicks were almost back to normal. Recovery numbers are in the table too. The confirmation that unlocked all of this reached the public through one executive's LinkedIn post. OpenAI itself never said a word about it in public.
"AI traffic" never meant one number
Before asking why your tools disagree, notice something first. They're often answering different questions while sharing one loose label.
Google's generative AI performance report finished rolling out worldwide by the end of August 2026. It counts impressions, how often a page showed up inside an AI Overview or an AI Mode answer, sorted by page, country and date. It has no click column. And it has never once seen a ChatGPT or Perplexity visit. It only watches Google's own surfaces.
GA4's native AI Assistant channel comes closer to what people actually mean by AI traffic. It only covers three named platforms, and only when a referrer survives the trip. Our GA4 setup guide covers those gaps in full. A third category, the AI-visibility platforms in the table above, counts neither clicks nor impressions. It counts citation presence inside an answer instead. That correlates with traffic loosely, at best.
So a founder asks how AI traffic did this month. Three tools can give three honest, non-overlapping answers, and all three claim to track the same thing. A customer success lead pulls GA4's session count for the board deck. Marketing pulls the citation tool's number for the same month. Both go up. Nobody in the room should call that proof the two things grew for the same reason.
26 content formats. Published on your domain. Matched to your brand.
Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, Google AI Mode, and Google AI Overviews.
A referrer is a promise the browser doesn't have to keep
A UTM tag and an HTTP referrer are two separate signals. Either one can vanish without the other. In-app browsers inside the ChatGPT and Perplexity apps often drop the referrer entirely. Medical and legal questions get their parameters stripped before the link even ships. Copy a link out of an answer and paste it into a new tab. Now you're carrying neither signal at all.
Our piece on tracking AI traffic when referrers go missing walks through a four-layer method for catching what the referrer alone won't show you. Most AI sessions arrive referrer-less, by most estimates, so every GA4 count is a floor, never a total.
| What | Estimate |
|---|---|
| AI sessions arriving with no referrer at all | Roughly a third to two-thirds, by practitioner estimate |
A separate analysis of how much hides in the Direct channel found the undercount large enough to change which quarter you'd call your best one.
GA4 and Search Console disagree about plain Google traffic too
This isn't a problem unique to AI. Marketers have compared GA4 sessions against Search Console clicks for years. The two rarely line up, even for ordinary organic search.
Some of the gap is structural. GA4 sometimes splits a visit that crosses midnight into two separate sessions. Search Console counts a click once, no matter the clock. Search Console also drops a chunk of its lowest-volume queries from the report, for privacy. Google calls that anonymization, and it quietly shrinks the number you'd compare against GA4's organic line.
A few practitioners trace their own gaps to double counting instead. The same visitor gets two different user IDs, if a site loads the GA4 tag twice by accident. Cookie blockers add a third wrinkle. They hide real sessions from GA4. Search Console doesn't depend on a browser cookie, so it just keeps counting the click. None of these tools is broken. They were built to answer different questions, and they get compared anyway.
AI referral traffic inherits all of that. Then it adds a layer of its own. A chatbot can simply choose not to send the signal at all.
A spike that wasn't traffic at all
Not every mismatch means a tool is undercounting. Sometimes a number moves because of something that was never a visitor.
On November 4, an agency reported something strange on r/SEO. A recovering site's Search Console clicks had spiked hard over one weekend, while impressions barely moved. The exact numbers are below. Several other SEOs said they'd seen the same pattern, on unrelated sites, that same Saturday. The spike got picked up by Search Engine Roundtable within days.
| What moved | By how much |
|---|---|
| Weekend clicks | Up roughly tenfold |
| Impressions | Flat |
| Click-through on terms ranked below page three | Hit 100% |
The working theory was bots, not real readers. It might have been a rank tracker. It might have been a CTR-manipulation service. GA4, on the same properties, showed nothing unusual at all. One commenter had a simple test before touching anything. Check the server logs and referrers first. Then ask whoever owns the account about rank trackers or CTR campaigns.
The useful habit, borrowed from that thread, is simple. Check the same day across every property you manage before reacting to any single spike. A pattern that shows up everywhere at once is a platform quirk. A pattern on one site alone is worth a harder look.
Your competitors are getting cited by AI. You're not.
Every day without citation tracking is a day your competitors pull ahead in ChatGPT, Perplexity, and Claude.
What to actually trust each month
Pick one number as your tracked trend. Stop trying to make every tool agree on its exact size. GA4's AI Assistant channel, layered with a custom regex channel for whatever Google hasn't added yet, is a reasonable default. Just make sure everyone reading the report knows it's a floor.
Treat Search Console's AI report as a Google-only signal. It's not a stand-in for chatbot traffic. Treat citation-tracking platforms as a measure of where you're being cited. That's genuinely useful. It just isn't the same as how many people clicked through.
RankControl's AI Visibility Tracking checks citations across all seven engines every week, and keeps that count in one dashboard. A citation swing doesn't depend on whichever traffic tool is having a rough week. Our guide to mention tracking vs. citation tracking goes further into why those two move apart.
Before treating any single week's number as a trend, ask whether something broke first. The October bug is just the extreme version. Smaller versions of the same pattern happen most months. A platform tweaks how it decorates links. A browser update changes referrer behavior. The tools built to watch the same traffic quietly start measuring different things again.
A few habits keep the monthly reconciliation from turning into a guessing game. Write down which signal each tool depends on, tag, referrer or citation, right next to its number. Check the same week across every property you run before treating one site's swing as real.
Keep a short log of platform changes, too. A sudden drop that lines up with a model release or an app update usually isn't your content's fault. And when the undercount is large enough to matter, report a range instead of a single number that only looks precise.
Doing it yourself or handing it off
Reconciling five dashboards by hand every month is a real job, not a quick glance. You can own it yourself. Pull GA4, Search Console, and whichever AI-visibility tool you've connected. Note what each one actually measures. Write the gap into your report instead of pretending it isn't there. Or let RankControl carry the citation half of that picture automatically. Then the only number you're left reconciling by hand each month is the traffic one.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
