ChatGPT traffic dropped in GA4? How to track AI visitors properly
For a week in October, many ChatGPT clicks landed in GA4 as Direct. Here's what happened, how to check your own numbers and how to track ChatGPT traffic reliably from now on.
If your Google Analytics report shows ChatGPT visits falling sharply around 9 October 2026, you most likely didn't lose those visitors. You lost the label. For about a week, many ChatGPT links opened without the tag and referrer that GA4 uses to recognise them, so the visits were counted as Direct. Tagging began coming back on 15 October.
Below is what happened, a 15-minute check you can run on your own GA4 property, and how to set things up so you can track ChatGPT traffic in GA4 reliably from now on, even when the next change comes along.
What happened to ChatGPT traffic in October
Since June, OpenAI has added utm_source=chatgpt.com to links in ChatGPT answers, as Search Engine Land notes. That small tag, plus the browser's referrer, is how analytics tools know a visit came from ChatGPT.
Shortly after GPT-6 rolled out, both signals started going missing:
- The drop. LLM Pulse reported that daily ChatGPT referral sessions fell about 46% between 9 and 11 October across the sites it monitors, while total traffic on the same sites fell only about 2%. Referrals from Perplexity and Claude showed no break.
- Where the visits went. Adobe's Cedric Huesler looked at about 500 pages where ChatGPT had driven at least 5% of visits. Comparing 9–13 October with the week before, ChatGPT visits fell by roughly 31,000 a day while Direct visits on the same pages rose by roughly 26,000 a day. His explanation: links were opening in a way that strips both the UTM tag and the referrer.
- The fix. On 15 October, Huesler said OpenAI had told him the missing tag was a known bug and that a fix had started rolling out. According to Relevant Audience's summary, tagged ChatGPT clicks in Adobe's data were back to roughly 95–100% of normal within hours.
Three caveats matter. First, the bug confirmation is secondhand: OpenAI hasn't announced it publicly. Second, the rollout may not have reached every account straight away. Third, the referrer is still missing on most ChatGPT clicks, and no backfill has been announced, so visits recorded as Direct during that week will stay Direct.
For Indian sites, the timing is easy to pin down. The tag stopped at about 2 pm Pacific time on 8 October, which was the early hours of 9 October in India, and the fix began on the afternoon of 15 October IST.
Your ChatGPT visitors didn't vanish. For a week, they just stopped wearing a name tag.
How GA4 decides a visit came from ChatGPT
GA4 sorts every session into a channel using two things: the referrer (the site the visitor came from) and any UTM tags on the link. Google's default channel group documentation now includes an AI Assistant channel. When the referrer matches Google's list of AI assistants, GA4 sets the medium to ai-assistant, and the channel picks those sessions up. Google gives ChatGPT, Gemini, Deepseek, Copilot and Grok as examples, and notes that Google's own AI Overviews and AI Mode are not included.
The Direct channel is what's left when GA4 has nothing to go on: no referrer, no campaign tags. That's exactly what a ChatGPT click with both signals stripped looks like.
The practical takeaway: the AI Assistant channel depends on the referrer, and the referrer is the part that's still unreliable. So don't judge AI traffic by one channel line. Look at session source as well, and back it up with signals you control.
Check your own GA4 data in 15 minutes
- Add an annotation. Mark 9 to 15 October 2026 in GA4 as "ChatGPT tracking bug". Anyone reading the report in six months will otherwise think you lost AI traffic.
- Open Traffic acquisition and switch to session source. Go to Reports → Acquisition → Traffic acquisition and change the primary dimension to Session source / medium. Search for "chatgpt". Compare 1–8 October, 9–15 October and 16 October onwards.
- Find the pages ChatGPT used to send people to. Add Landing page as a secondary dimension for the week before 9 October. These are usually guides, pricing pages and comparison pages.
- Check Direct on those same pages. If ChatGPT went down and Direct went up by a similar amount on the same pages, the visits were still there. Adding ChatGPT and Direct together for those pages gives you a fair estimate of the real trend.
- Look at leads, not just sessions. Compare form fills, calls and WhatsApp enquiries for the same periods. If leads held steady, nothing changed in the real world.
- Confirm the recovery. From 16 October onwards, sessions with source chatgpt.com should be climbing back. If your property still shows almost none a week later, test it yourself: ask ChatGPT a question your site answers, click through to your site, and check GA4's Realtime report to see how the visit was labelled.
Set up GA4 to track ChatGPT traffic properly from now on
This won't be the last time an AI tool changes how its links work. A few small changes make your reporting much harder to break.
1. Create an "AI tools" custom channel group
In GA4 Admin, under Data display → Channel groups, create a custom channel group with a channel called "AI tools". Set the rule to Session source matches regex with something like:
chatgpt|openai|perplexity|gemini|copilot|claude|deepseek
Move the AI tools channel above Referral so those visits aren't swallowed by it. This catches visits that carry the UTM tag even when the referrer is missing, and you decide which tools count. Google's help pages say standard properties can create two custom channel groups, with up to 50 channels each, so there's room for this alongside any grouping you already use.
2. Ask every lead where they found you
Add a "How did you hear about us?" field to your enquiry forms, with "ChatGPT or another AI tool" as an option. Self-reported answers catch the visits analytics misses entirely, including people who read an AI answer and then typed your name into Google. It's the cheapest attribution fix there is, and our lead generation team can add it to your forms and landing pages.
3. Track the actions that matter as key events
Sessions are a weak signal. Form submissions, phone clicks and WhatsApp clicks are strong ones. Make sure each is recorded as a key event in GA4 and, ideally, lands in your CRM with its source attached. If enquiries currently end up in an inbox someone checks twice a day, our automation services can route them into a CRM with the source recorded.
4. Use UTMs on the links you control, and nowhere else
Tag the links you place yourself: ChatGPT ads, newsletters, your Google Business Profile website link, social bios. Never add UTMs to links between pages on your own site; that overwrites the original source and creates the very mess you're trying to avoid. If you're testing paid placements, our guide to ChatGPT ads in India covers the tracking setup.
5. Measure visibility, not just clicks
Many people read ChatGPT's answer and never click at all. Keep a list of 10 to 20 questions your buyers actually ask, such as "best interior designer in HSR Layout" or "ERP partner in Chennai for manufacturers", and check each month whether your brand appears in the answers. That number doesn't depend on any tracking tag. Our guide on getting your brand recommended by ChatGPT explains how to improve it.
What this means for Bangalore and Chennai businesses
People who click through from an AI answer have usually already read a summary of their options, so these can be some of your most valuable visits. That also makes it easy to overreact when the chart drops.
- Don't cut AEO or content work because of one bad week. The October dip was a measurement problem, not a demand problem.
- Report AI traffic as a range, not a single number. AI sessions in GA4, plus Direct on the pages AI tools favour, plus leads who said "ChatGPT" on the form.
- Judge on enquiries and revenue. Channel labels will keep changing as AI tools change. Leads don't lie in the same way.
If you'd like a second pair of eyes on your GA4 setup or your visibility in AI answers, that's part of what our SEO and AEO team does every month.
Frequently asked questions
Why did my ChatGPT traffic drop in Google Analytics in October 2026?
From about 9 October (India time), many ChatGPT links opened without the utm_source=chatgpt.com tag and without a referrer, so GA4 counted those visits as Direct. Industry data suggests most of the visits still happened; they were just labelled differently.
Is the ChatGPT UTM tracking issue fixed?
Mostly. Adobe's Cedric Huesler reported on 15 October that OpenAI called it a bug and that tagged clicks were returning to normal levels in Adobe's data. OpenAI hasn't confirmed this publicly, and the referrer is still missing on most clicks.
Where does ChatGPT traffic show up in GA4?
When GA4 recognises the referrer, it appears in the AI Assistant channel. When only the UTM tag survives, look for session source chatgpt.com in the Traffic acquisition report. When both are missing, the visit lands in Direct.
Will GA4 restore the missing ChatGPT data from 9 to 15 October?
No backfill has been announced, so sessions recorded as Direct during that week will stay Direct. Add an annotation in GA4 and compare ChatGPT plus Direct on your top AI landing pages to estimate the real numbers.
How can a small business track leads that come from ChatGPT?
Combine three things: an AI tools custom channel group in GA4, key events for forms, calls and WhatsApp clicks, and a "How did you hear about us?" question on every enquiry form with ChatGPT as an option.
The short version
- ChatGPT traffic in GA4 dropped around 9 October 2026 because links lost their tracking tag and referrer, not because people stopped clicking.
- Tagging started returning on 15 October, but the referrer is still unreliable and the lost week won't be backfilled.
- Annotate the dates, and check ChatGPT plus Direct on your top AI landing pages.
- Add an AI tools channel group, a "how did you hear about us" field and proper key events.
- Judge AI search on leads and visibility, not on a single channel line.
