Discussion
  • AI Search
  • SEO Analytics

GA4 added an AI Assistant channel in 2026. Have you compared it with your own referrer rules, and what does it miss?

Published 1 reply

Discussion starter: an SEO measurement question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    The GA4 AI Assistant channel is a useful default, but it is a partial view, and it is worth running your own referrer rules alongside it for at least a few months. Google’s help page names examples such as ChatGPT, Gemini, DeepSeek, Copilot and Grok, but does not publish the full list of sources, so you cannot be sure every assistant your visitors use is classified. By design it excludes Google’s own AI Overviews and AI Mode, which stay in organic search. And like any referrer-based method, it cannot see traffic that arrives without a referrer, which lands in Direct. Comparing it with your own rules shows which of these gaps matter for your site.

    What the channel captures and misses

    Traffic AI Assistant channel Where it goes instead
    Clicks from recognised assistants that pass a referrer Captured
    Assistants not on Google’s unpublished list Possibly missed Referral, or wherever your channel rules place them
    AI Overviews and AI Mode clicks Excluded by design Organic Search
    Clicks from apps and in-app browsers without a referrer Missed Direct
    Copied and pasted links from answers Missed Direct
    Agentic browsers acting for a user Unclear; depends on what they send Often Direct or ordinary referrals

    How to compare it with your own rules

    1. Build a custom channel group with an AI channel defined by your own rules: referrer domains for the assistants you care about, plus UTM sources that some assistants add to links, such as utm_source=chatgpt.com. Place the AI rule above Referral so it takes precedence.
    2. Run both side by side for at least a month. Report sessions, engaged sessions and conversions for GA4’s channel and yours.
    3. Break down by session source. Sources in your channel but not in GA4’s show what the default misses; sources in GA4’s but not yours show gaps in your own list.
    4. Decide which to use for reporting, and keep the other as a check. Many teams keep their custom definition for continuity with reporting that predates May 2026, and use the default channel as a cross-check.

    A continuity point:

    The default channel appeared in May 2026, so any report comparing AI traffic across that date mixes definitions. Annotate the date, and if you need a trend that spans it, use a custom definition that has been applied consistently.

    Estimating what neither can see

    Both definitions miss referrer-less traffic. To estimate it, look at Direct sessions landing on deep pages, such as specific articles, documentation or product pages, that people rarely type or bookmark. If Direct traffic to pages known to be cited by assistants rises faster than Direct traffic to comparable uncited pages, the difference is a reasonable, if rough, estimate of hidden AI traffic. Pair that with a “How did you hear about us?” option for AI assistants. Report identifiable AI traffic as a floor and the estimate as a range above it.

    Google’s AI features need separate treatment

    Because AI Overviews and AI Mode sit inside Organic Search, the AI Assistant channel says nothing about them. For those, use Search Console’s “Search generative AI performance” report for impressions, and remember that AI Mode clicks are counted within Search Console’s web totals with no separate click breakdown. If leadership asks for “all AI traffic”, explain that it has to be assembled from three pieces: the AI Assistant channel (or your own definition), an estimate of hidden assistant traffic in Direct, and Google’s AI features, which can be seen as impressions but not separated as clicks.

    Hypothetical example:

    A software company runs its own AI channel rules alongside GA4’s default for six weeks. The two agree closely on ChatGPT and Gemini. Its own rules also capture sessions from two smaller assistants and from links carrying an AI tool’s UTM source, which the default puts into Referral. Neither captures a rise in Direct sessions landing on documentation pages that Bing’s AI Performance report lists as frequently cited. The team reports AI Assistant sessions using its own definition, adds a line for estimated hidden assistant traffic with the method stated, and reports Google AI feature impressions separately from Search Console.

    Reading AI Assistant traffic once you have it

    Once the definitions are reconciled, the more interesting questions are about behaviour. Compare engagement and conversion rates for AI Assistant sessions with organic search and with referral traffic. Look at which landing pages receive AI traffic: they are usually deeper and more specific than organic landing pages, which tells you what assistants find useful on your site. Check new versus returning share, since AI referrals often bring first-time visitors. And segment by assistant, because the platforms differ in audience and intent. Small volumes make these comparisons noisy month to month, so read them over a quarter. The pattern many sites see is low volume, deep landing pages and above-average engagement, but check your own data before repeating that as a rule.

    Practical settings to check

    • Make sure UTM parameters survive redirects and consent flows, or AI traffic that is tagged will still be lost.
    • Check that referral exclusions and cross-domain settings do not overwrite AI referrers when users move between your domains.
    • Review the list of AI sources quarterly; new assistants and new domains appear regularly.
    • Exclude bot traffic from AI crawlers and user-triggered fetchers, which should not appear as sessions if your analytics filtering is working, but occasionally do.

    Use the GA4 channel as a convenient default, keep your own rules as the reference, reconcile the two regularly, and be explicit that both are floors. The traffic they miss, referrer-less assistant visits and Google’s own AI features, often matters as much as what they capture.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.