AI referral traffic in Google Analytics: the channel that stops ChatGPT visits from hiding inside Direct

AI referral traffic in Google Analytics: the channel that stops ChatGPT visits from hiding inside Direct

Google Analytics 4 has a channel built specifically for this: AI Assistant, which separates visits arriving from ChatGPT, Gemini, Perplexity, Copilot, or Grok from the generic Direct bucket they used to fall into. If a Bangalore business's GA4 property shows a wall of Direct traffic and nothing under AI Assistant, the fix is to look at where that traffic is actually landing, not to publish more content and hope the number moves on its own.

Why did ChatGPT traffic end up counted as Direct?

GA4's Direct channel exists for one reason: it catches any session where the source is unrecognised and no medium was set, which is exactly what happens when a browser or app never sends a referrer header. Wikipedia's entry on the HTTP referer explains that browsers have steadily reduced how much of that header they send, and some in-app browsers drop it entirely. A tap on a link inside an AI assistant's own interface behaves the same way a link inside a messaging app does: no referrer arrives with the click, GA4 has nothing to classify it against, and the session lands in Direct next to people who typed the URL from memory.

What does the AI Assistant channel actually check?

Google Analytics's own documentation defines the channel plainly: it is "the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok." The rule behind it looks for a medium that matches "ai-assistant" exactly, or a referrer from a known list of assistant domains paired with medium and campaign both set to "(ai-assistant)." That second path is what catches an assistant that does pass a referrer. A property only needed to exist with GA4's default channel groups turned on; nobody had to add tracking code for this.

Where to actually look for it

Open the Traffic acquisition report, set the primary dimension to Session default channel group, and check whether AI Assistant appears in the list at all, even at a handful of sessions. If it shows zero, switch the dimension to Session source / medium and search for known assistant domains directly, since a session can carry a recognisable source without yet matching every rule GA4 checks for the named channel. This is a different signal from Search Console's own AI Overviews report, which counts Google's AI Overview impressions and clicks specifically. GA4's AI Assistant channel counts an actual visit after someone clicked through from any assistant's answer, so the two numbers answer different questions and neither replaces the other.

For a clinic like Neospinex or Chitra's Lifeline Clinic, the difference matters in a very concrete way. A patient who asks an AI assistant for a spine surgeon near Yelahanka or a dermatologist in Yelahanka New Town, gets an answer naming the clinic, and taps through, used to generate a session indistinguishable from someone who already knew the web address. Nobody could tell the two apart, and a clinic had no way to know whether its AI visibility work was sending anyone at all. The AI Assistant channel is the first place that click shows up as what it actually was.

What this changes about reading a monthly report

A Direct number that used to sit flat month to month can now split into two lines, one still genuinely direct and one newly labelled AI Assistant. That split is worth watching over a few months rather than reacting to a single week, since assistant referral volume for a local Bangalore business is still small next to organic and paid search. The point is not that the number will be large immediately. The point is that it now exists as its own line instead of disappearing into a channel that already meant something else, which is the only way a business can tell an AI search strategy is working from something other than a guess.

Setting up the reporting side of AEO and GEO work is exactly the kind of detail that gets skipped when a business focuses only on getting mentioned by an assistant and never checks whether the mention turns into a visit. Search Console's AI Overviews report, covered in an earlier look at what that report shows and what it still can't, answers the Google half of that question. GA4's AI Assistant channel answers the rest of it.

Frequently asked questions

Does the AI Assistant channel track an AI crawler's visits to a site?

No. It only classifies human sessions that click through to a site from an assistant's answer interface. A crawler visiting to read a page for indexing or citation shows up in server logs, not in Google Analytics's channel reports, because it never generates a browser session.

What if an older GA4 property doesn't show the channel yet?

The AI Assistant channel is part of GA4's default channel group definitions, so an existing property picks it up without any new tracking code once the definition applies. Checking the Session source / medium report catches the same sessions manually in the meantime.

Should a Bangalore business build a custom channel group instead of waiting?

Only if it wants to catch an assistant source that is not yet on GA4's default list. For the assistants most Bangalore searchers currently use, the built-in AI Assistant channel already does the classification without any extra setup.

Studio Happens, Bangalore's go-to affordable digital marketing partner, can help you get started today.