← Back to Blog
Founder ColumnGEOAI VisibilityAnalyticsAI AttributionAttribution
On May 13 and June 3, 2026, Google made historic AI-related updates to its two primary analytics platforms. Industry response was enthusiastic, but most coverage stopped at "how to use it" tutorials. This article is not a tutorial. It is a precise boundary analysis, designed to help you understand what these updates can and cannot do — and what those limitations mean for your AI measurement strategy.
Starting May 13, GA4 added an "AI Assistant" channel to its Default Channel Group. When GA4 detects a referrer from a recognized AI platform, it automatically categorizes that session under "AI Assistant" and assigns medium: ai-assistant and campaign: (ai-assistant).
This means you no longer need manual regex configurations to identify AI traffic — GA4 supports it natively. You can see the "AI Assistant" row directly in Reports → Acquisition → Traffic acquisition, alongside Organic Search, Social, Direct, and other channels.
But you need to understand four boundaries.
Boundary One: Not retroactive. The AI Assistant channel only applies to data from May 13, 2026, onward (the exact date depends on when the feature rolled out to your specific property — it was a phased launch). Historical ChatGPT traffic remains classified under Referral or Direct and will not be reclassified. This means you cannot use this channel for year-over-year comparisons. Keep your previous custom channel group configurations as a historical baseline.
Boundary Two: Referrer-dependent only. GA4 relies on the browser's referrer header to identify AI sources. When users click links from ChatGPT's iOS app, the referrer is frequently stripped (due to iOS privacy mechanisms and inconsistent in-app browser behavior). These visits appear in GA4 as (direct) / (none), not AI Assistant. This means a significant portion of AI-sourced visits are misclassified as Direct, preventing GA4 from capturing all actual AI referral traffic.
Boundary Three: Limited platform recognition. As of publication, public examples and early rollout observations suggest that GA4 mainly covers referrers from a subset of mainstream English-language AI assistants, but Google has not given marketers a stable exhaustive list to rely on. DeepSeek, Perplexity, Kimi, Doubao, Tongyi Qianwen, Zhipu GLM, Grok, and Mistral's LeChat should still be handled through custom channel groups.
Boundary Four: Google's own AI Overview is excluded. This is the most consequential boundary. When a user clicks a link from Google AI Overview or AI Mode, GA4 does not classify it as AI Assistant — it goes into Organic Search. This means the "AI Assistant" channel tracks only third-party AI platform referrals, not Google's own AI search products.
Boundary Four matters more than you think. In many product categories, Google AI Overview's reach far exceeds ChatGPT or Perplexity. If you look only at GA4's AI Assistant channel, you will underestimate AI search's total impact on your brand — because the largest AI search entry point (Google's own) is hidden inside Organic Search.
The reaction on Reddit's r/GoogleAnalytics and r/SEO can be summarized as "guarded optimism."
Most commenters welcomed the update — "Finally a native channel, no more regex gymnastics." A significant number took a pragmatic view — "This is just the tip of the iceberg; the dark traffic problem is still unsolved." Others raised pointed questions — "Is Google deliberately keeping its own AI Overview out? There's a conflict of interest here."
A frequently repeated operational warning: if you previously built custom AI traffic channel groups with regex, you now need to audit your configuration to avoid double-counting with the native channel.
On June 3, Google Search Console launched "Search Generative AI" performance reports. These reports are separate from standard search performance reports and specifically track website performance within AI Overviews, AI Mode, and AI features in Discover.
What the reports provide:
What the reports do not provide:
The impact of this limitation is profound. You can see that your site was cited 500 times in AI Overviews, but you do not know how many actual visits those 500 citations produced. You cannot calculate the ROI of AI visibility, cannot compare conversion efficiency against traditional organic search, and cannot determine whether investing in AI visibility optimization is worthwhile.
In other words, GSC gives you "being seen" data but withholds "being clicked" data. For conversion-oriented marketing teams, an impressions-only report is difficult to act on for budget decisions.
Current rollout status: Testing with a subset of site owners in the UK first, with plans for global expansion. If you do not see this report yet, it may not have reached your property.
Alongside the AI reports, Google introduced an "AI Visibility Toggle" that lets site owners choose whether their content appears in Google's AI search features. Google states that opting out does not affect traditional search rankings.
The toggle's backstory is regulatory pressure from the UK's Competition and Markets Authority (CMA), which required Google to give publishers choice regarding AI features.
On the surface, this is positive — site owners finally have agency. But the actual decision is fraught.
You want to know: "If I opt out of AI Overview, how will my traffic change?" But GSC does not give you click data. You can see you have 500 impressions in AI Overview, but you do not know how much traffic those impressions drive. If you opt out, you lose 500 impressions — but you do not know what those 500 impressions are worth.
This is a design that gives you an exit button without giving you decision-making information. Site owners are asked to make a potentially traffic-altering decision with incomplete information.
Since 2025, many site owners have observed a structural trend in standard GSC reports: impressions holding steady or growing, while clicks and CTR continue to decline.
The cause: AI Overview impressions are counted within total impressions (pushing the number up), but users find their answers directly in the AI summary without clicking through to the website (pulling clicks and CTR down). This is what the industry calls "The Great Decoupling" — impressions and clicks are no longer positively correlated.
The new AI reports at least separate AI-related impression data, helping site owners understand how much of their impression growth comes from AI features. But without click data, you still cannot quantify the magnitude of the decoupling.
With these boundaries understood, here are practical recommendations for maximizing the value of GA4 and GSC's AI features:
Google built an attribution channel for its competitors (ChatGPT, Claude) but not for its own AI Overview. This is not a technical limitation — it is a commercial choice tied to the foundation of search advertising pricing. In the next article, we analyze the business logic behind Google's attribution design.
A: No. The channel applies only to data from May 13, 2026, onward. Historical AI traffic remains in its original classification (typically Referral or Direct) and will not be reclassified. We recommend keeping previous custom channel group configurations as a historical baseline.
A: Yes, you need to audit it. If your custom group and the native AI Assistant channel both match the same source, you may get double-counting or priority conflicts. Check your custom group's priority settings to ensure no overlap, or adjust the custom group to cover only AI platforms that GA4 does not natively recognize.
A: Primary value is trend monitoring and brand visibility baseline. You can track whether your brand's AI citation frequency is growing, which pages are most frequently cited, and which countries and devices show the most AI visibility. But it cannot quantify actual traffic or conversions from AI citations — that requires server-side analysis and Citation SOV sampling.
A: Without click data, we recommend staying opted in. Opting out means giving up AI Overview impressions, but you cannot evaluate their actual traffic value. Unless you have a specific reason (content copyright protection, explicit preference against AI citation), keep it enabled and deploy independent AI visibility monitoring to assess real impact.
A: Approximately one and a half layers out of five. GA4 covers Layer 1 (trackable referrals, but with incomplete capture due to referrer loss). GSC covers the impression portion of Layer 2 (but no clicks). Layer 3 (Dark AI Traffic), Layer 4 (AI crawler intent), and Layer 5 (zero-click influence) are entirely outside GA4 and GSC's observation scope.
The discussion above reflects the article’s June 2026 publication context. Google’s current help pages describe a dedicated Generative AI performance report and AI inclusion controls. Check the report actually available to your verified property; availability and documentation can change. The dedicated report, ordinary Web performance totals and GA4 sessions describe different observation surfaces.
Use GSC Web clicks and impressions for the property-level search baseline. Read AI-specific impressions separately where available; do not add them to Web totals without a documented non-overlapping denominator. GA4 measures visits and events after arrival, subject to consent, referrer and tagging limits. Direct traffic is not evidence of an AI visit, and an impression is not an attributable enquiry.
For a buying decision, ask for the exact source of each metric, the date window and timezone, test exclusions and a deduplication rule. A server-confirmed form submission, a non-test contact and a qualified enquiry are separate states. Neither channel attribution nor a single AI answer proves incremental revenue.
References: Google: Generative AI performance report · Google: AI inclusion · Google: AI search
GEO service scope · request an audit
We audited attribution on the Global Gravity website, comparing September 22–October 19, 2026 with August 25–September 21, two 28-day windows. GA4 was filtered to the production domain and its www host, using Asia/Shanghai time. This is research on our own site, not a client performance case study.
Sessions rose from 1,464 to 2,192 (+49.7%), while engaged sessions fell from 314 to 206 (-34.4%). Looking only at total visits can mistake measurement noise for demand growth.
A separate aggregate filtered jointly to Singapore, desktop, Direct, Chrome 145.0.0.0, Macintosh and a 1366×1366 screen resolution returned 878 sessions, with zero engaged sessions and zero key events. This unusually consistent traffic warrants separate investigation, but does not identify a bot or justify relabeling Direct as AI traffic. The original data remains unchanged.
The independent aggregate for identifiable AI sources returned 11 sessions and 8 users, including 5 engaged sessions. The Chinese Beatbot case study received 5 sessions, 3 engaged, making it a concrete priority for improving the path from case study to relevant service and consultation. Engagement is not an inquiry, and page aggregates cannot reconstruct an individual's complete journey.
Our sequence is to separate traffic quality, improve the next steps on pages that actually receive visits, then match successful submission receipts individually to GA4 events where analytics consent was given. Page and source rows are not added to infer independent sessions. Without a new inquiry or AI citation evidence, the result remains unknown rather than becoming an invented growth claim.
This article is one evidence asset. AI Evidence Index connects articles, FAQ, products, technology, cases, llms files, and /ai/*.md.
Get an AI visibility audit covering citations, recommendations, and evidence gaps.
Get an AI visibility audit