70.6% of AI referrals to your WooCommerce store arrive with no referrer header — invisible to GA4 by default (Loamly, February 2026). The third that does survive lands in Direct or Referral, with no label that says “AI.” GA4’s default channel group still has 18 channels and zero AI Assistants channel as of May 2026.

A custom channel group fixes the reporting for the visible two-thirds. The hidden third needs server-side capture or it stays in Direct forever. Here’s the 2026 regex that actually holds, the GA4 admin steps to ship it, and what to do about the floor the regex can’t reach.

Why GA4 Still Has No Default AI Channel in 2026

GA4’s channel grouping logic was last meaningfully updated for “Organic Shopping” and “Cross-Network.” There is still no default channel for AI Assistants — and the AI mix has fragmented to the point where any single 2024-era rule covers, at best, two-thirds of it.

The 2026 share-shift data tells the story. ChatGPT held 64.5% of Gen AI traffic share in January 2026, down from 86.7% a year prior. Gemini’s share rose from 5.7% to 21.5%. DeepSeek entered the chart at 4.2%. Grok crossed 3%. A regex written for ChatGPT alone in 2024 now misses a third of AI traffic outright.

If your AI regex hasn’t been touched since 2024, it’s miscategorising one in three AI sessions.

Meanwhile, AI traffic itself is no longer rare. 63% of websites already receive at least one visitor from an AI chatbot (Ahrefs, 2025), and Adobe Analytics’ holiday data shows AI-referred traffic to e-commerce stores grew 7x in 2025. For WooCommerce, this is the channel that’s actually growing while paid social plateaus.

The 2026 Regex That Actually Holds

Here is the current Source-based regex covering the platforms with non-trivial share as of May 2026:

^(chatgpt.com|openai.com|chat.openai.com|gemini.google.com|bard.google.com|perplexity.ai|claude.ai|anthropic.com|copilot.microsoft.com|bing.com/chat|deepseek.com|grok.com|x.ai|meta.ai|you.com|poe.com|character.ai)$

A few structural choices matter, because the regex you find on most blogs is missing them:

• Anchored at both ends (^ and $). Without anchors, the pattern pulls in any URL that contains “chatgpt” as a substring — including news articles about ChatGPT.
• Explicit subdomain entries for chat.openai.com and bing.com/chat. Some traffic still routes through the old hostnames.
• Both gemini.google.com and bard.google.com. The redirect is mostly clean, but old saved chats still resolve via bard.
• x.ai included alongside grok.com. Different surface, same product, both show up in real data.

Deliberately excluded: search engine “AI Overview” traffic. That arrives as google.com or bing.com referrer and belongs in Organic Search, not AI Assistants. Mixing them ruins both buckets.

You may be interested in: Gemini Just Overtook Perplexity in AI Referrals — and Your WooCommerce Store’s “Direct Traffic” Bucket Is Hiding Them

How to Build the Channel Group in GA4 (Step by Step)

The setup lives in Admin, not in Reports. Five minutes if you have edit access on the property:

1. Open Admin in your GA4 property. Under Property settings, click Channel groups. (If you don’t see it, you need Editor or higher.)
2. Click “Create new channel group.” Name it something obvious like “WooCommerce + AI” so it doesn’t get confused with Default.
3. Click “Add new channel” and name it AI Assistants. Position it above Referral in the list — order matters because GA4 evaluates rules top-down and stops at the first match.
4. Set the rule: Source matches regex → paste the pattern from above. Leave Medium and Campaign empty.
5. Save the channel group. Then go to your reports and switch the channel grouping selector to your new group.

The change is retroactive. GA4 reclassifies historical sessions the moment you save the rules — you’ll see your last 14 months of AI traffic immediately.

One WooCommerce-Specific Step Most Guides Skip

If you import GA4 conversions into Google Ads, the channel group change does not flow through. Google Ads runs its own attribution model. You need to also export the channel-group dimension to BigQuery (or use the Looker Studio connector) if you want AI Assistants visible in any cross-platform report. Otherwise the AI revenue line shows up in GA4 and nowhere else. For the underlying mechanics on why those two numbers diverge, see GA4 Key Events vs Google Ads Conversions: Why Your Numbers Never Match.

The Floor the Regex Can’t Reach

Here is the limitation most guides bury or skip entirely. Even with a perfect regex, your AI Assistants channel will only contain sessions that arrived with a usable referrer header. The rest — somewhere between 35% and 70% depending on the month and the platform — arrive with no referrer at all. They land in Direct.

Clickport’s April 2026 analysis of 371,847 sessions found 35.7% of AI-classified sessions arrived UTM-only with no HTTP referrer. Loamly’s February 2026 cohort puts the no-referrer share at 70.6% on aggregate. Either way, the floor is large enough to matter for any WooCommerce store running paid acquisition alongside content.

Four documented mechanisms strip the referrer before it reaches GA4:

1. Strict-origin-when-cross-origin is the default Referrer-Policy on chatgpt.com. When the request crosses to your domain, Chrome and Edge strip everything past the origin — and on a same-origin policy, that’s the entire referrer.
2. rel=”noreferrer” on inline citations in some paid-tier output. The full link is sent, but the browser is told to send no Referer header at all.
3. WKWebView (iOS) and Custom Tabs (Android) — the in-app browsers used by mobile AI apps. They sandbox referrer headers by default. Mobile is now half of all AI sessions in some verticals.
4. Clipboard copy-paste. The user copies the URL out of the AI response and pastes it into a fresh tab. There is no referrer because there is no referring page.

None of these is a bug. They are intended behaviour by Apple, Google, OpenAI and the standards bodies. No client-side fix exists.

You may be interested in: ChatGPT Atlas and Perplexity Comet Are Already in Your WooCommerce Analytics

How to Recover the No-Referrer Third

The fix is server-side, first-party, and runs before any browser policy gets a chance to strip headers. Capture the referrer at the very first request from your subdomain, persist it as a first-party cookie, and stamp it on every event you send to GA4, Google Ads, and Meta CAPI. A client-side referrer policy cannot reach a value that was already captured server-side.

For WooCommerce specifically, you also want that AI source flag on the order itself — not just the session. That way, even if the customer comes back via Direct three days later, the conversion still carries the AI signal. Which means Smart Bidding can finally optimise for it.

Transmute Engine™ is a first-party Node.js server that runs on your subdomain (e.g., data.yourstore.com) — the inPIPE WordPress plugin captures WooCommerce events and sends them via API to the Transmute Engine server, which captures referrer at first request, stamps an ai_source flag on the order, and routes the AI attribution simultaneously to GA4, Google Ads Enhanced Conversions, and Meta CAPI. The channel group becomes the reporting view; the server is what makes the attribution real.

Key Takeaways

• The 2026 regex must include Gemini, DeepSeek, Grok and Claude — ChatGPT-only patterns now miss roughly a third of AI traffic.
• GA4 channel group rules are retroactive — the moment you save them, your last 14 months of AI sessions get reclassified.
• Anchor your regex with ^ and $ to avoid pulling in news articles and unrelated subdomains.
• Position AI Assistants above Referral in the channel list — top-down evaluation stops at first match.
• The regex only sees two-thirds of AI traffic. The other third has no referrer header at all and needs server-side capture, not a smarter rule.

Frequently Asked Questions

Audit your AI traffic capture this week — see how much is hiding in Direct, build the channel group, then layer in the server-side recovery. seresa.io