Why Your Direct Traffic Grew 40%: Between 35% and 70% of AI-assistant sessions arrive with no referrer and quietly inflate Direct in GA4. This self-audit recovers them, then connects them to revenue causally.
Read the full article below for detailed insights and actionable strategies.
Key insight
Average ad spend misallocated due to broken attribution across DTC brands
If your Direct traffic climbed 40% or more with no brand campaign to explain it, AI assistants are the most likely source. Between 35% and 70% of sessions that begin in ChatGPT, Copilot, or a similar assistant arrive with no referrer at all, so GA4 files them under Direct or Unassigned. GA4 shipped a native AI Assistant channel on May 13, 2026, but it catches only part of that flow and misses Perplexity entirely. Below is the audit recipe, plus the causal step most guides skip.
Why do AI referrals land in your Direct bucket?
In practice, three patterns do the damage.
First, assistants are apps, not pages. A tap inside the ChatGPT or Copilot app often opens an in-app viewer or hands off to the browser in a way that drops the referrer, so the session starts with no source information at all.
Second, people copy links. A user asks for recommendations, copies a URL out of the answer, and pastes it into a fresh tab or sends it to a colleague. That visit arrives with no referrer, exactly like dark social sharing in WhatsApp or Slack, which has inflated Direct for years. The assistant did the work; your Direct line gets the credit.
Third, assistants do not append your UTM parameters. A click that starts inside an answer carries none of your campaign tags, so your carefully tagged paid and email buckets never see it.
The volume behind this stopped being rounding error a while ago. Published industry analyses of the 2025 holiday season put AI-referred retail traffic up nearly 7x year over year (+693%). When a channel grows that fast while hiding inside Direct, every downstream report bends: branded search looks stronger, Direct looks healthier, and the assistant that actually sent the visit gets nothing. On the paid side, OpenAI now sells ads against these same answers, and those clicks have their own blind spot, which we cover in the ChatGPT ads measurement gap.
None of this means assistants are stealing credit maliciously. It is a plumbing problem: the web's referrer system was built for page-to-page clicks, and assistant-to-site journeys break it in several different places. The effect on your reports, though, is the same as if a paid channel ran untagged for a year.
What does GA4's AI Assistant channel actually catch?
See also: GA4 Unassigned Traffic Isn't Random: Why It Systematically Penalises Your Newest Channels
On May 13, 2026, GA4 added a native AI Assistant channel to its default channel groups. It re-buckets sessions whose referrer matches Google's list of known assistant domains. That is real progress: for the first time, a slice of AI-originated traffic gets its own line instead of disappearing into Referral.
Two gaps remain. The channel misses Perplexity entirely, so a meaningful assistant source never gets classified at all. And it can only classify sessions where a referrer survives, which excludes the 35% to 70% of assistant sessions that arrive with none. Treat the channel as a floor, not a ceiling.
To see it in your own property, open Reports, then Acquisition, and look for AI Assistant in the default channel group from mid-May 2026 onward. If it is absent or tiny while your post-purchase surveys say otherwise, you are looking at the undercount, not at the truth.
It is also one change among many. Between consent enforcement, platform reporting overhauls, and new channels like this one, 2026 has rewritten most acquisition reports. The 2026 attribution changelog keeps the full list straight.
How do you find the AI sessions hiding in Direct?
Set aside 45 minutes and work through four steps in order.
Step 1: Quantify the spike against a clean baseline
In GA4, trend direct traffic by week for at least 12 months and compare it against your pre-AI baseline. The cleanest comparison window is the 2025 holiday season against 2024, because industry analyses of that period put AI referral growth at nearly 7x year over year (+693%). Direct up roughly 40% while brand search volume stays flat is the classic signature of assistant-driven inflation.
Control for the obvious confounds before blaming assistants: big promotions, PR moments, and app deep-link campaigns also move Direct. The assistant signature is growth that persists after those spikes are excluded.
Step 2: Isolate AI-shaped sessions inside Direct
AI-referred visits behave differently from classic Direct. They skew toward new users, because assistants answer discovery questions. They land deep, on product, comparison, and editorial pages, not the homepage. And they often engage better than typed-in Direct, because the user arrives pre-qualified by a conversation. Build an exploration with session source equal to (direct), filtered to new users on deep landing pages. What surfaces there is your hidden assistant cohort.
Step 3: Build a regex channel group for the referrers that survive
In GA4 Admin, open Channel groups and create a custom group. Add a rule that matches Session source against the known assistant domains, for example:
chatgpt|chat\.openai|gemini\.google|copilot\.microsoft|claude\.ai|perplexity\.ai|poe\.com
Place the rule above Referral. This recovers what the native channel misses, including Perplexity, for every session where a referrer exists. This is exactly where every competitor guide stops: a tidy new bucket and a sense of accomplishment.
Step 4: Triangulate with a post-purchase survey
Ask every buyer "How did you first hear about us?" with "An AI assistant" as an explicit option. The survey share will exceed anything GA4 can show you, because it captures the no-referrer majority. Compare the survey share against your regex bucket to bound the true figure. The full method is in the triangulation playbook.
| Audit check | Where in GA4 | Positive signal | Dated benchmark |
|---|---|---|---|
| Direct spike vs baseline | Acquisition reports, weekly trend | Direct up ~40% YoY, brand search flat | Industry analyses: AI referrals +693% YoY, Nov to Dec 2025 |
| No-referrer cohort | Exploration: (direct), new users, deep pages | Rising share of new-user Direct on product URLs | 35 to 70% of assistant sessions carry no referrer (2026 analyses) |
| Native channel gap | Default channel group | AI Assistant channel present, Perplexity absent | Channel launched May 13, 2026 |
| Regex recovery | Custom channel group | Referral sessions re-bucketed as AI | Applies to data from May 2026 onward |
An illustrative example: an anonymized Dutch skincare brand with €2.1M in annual revenue ran this audit in June 2026 and found Direct up 44% year over year, concentrated in new-user sessions on product pages. Its regex group recovered 3.1% of all sessions as AI referrals. Its post-purchase survey put the true share closer to 9%.
How do you connect the recovered traffic to revenue?
See also: How to Fix Klaviyo Over-Attributing Revenue on Shopify
Here is the step the guides skip. A regex bucket tells you how many sessions arrived. It cannot tell you what those sessions caused, and the two obvious ways of closing that gap are both wrong.
Crediting the AI bucket with every conversion it touches inside your attribution window overstates it, because many of those users would have found you anyway. Ignoring the bucket because last click files it under Direct understates it, because the assistant often started the journey. The right question is incrementality: how much revenue would disappear if this traffic stopped tomorrow?
Answering that needs a counterfactual, not a bucket. Export your GA4 data, annotate context like promotions and seasonality, and run a causal read that compares revenue against the baseline your own history implies. Note the window trap: when you re-bucket sessions retroactively, GA4 still credits conversions within its own attribution window settings, so run the read on the raw export, not the GA4 interface.
Causality Engine runs exactly this read: GA4 export in, causal read out, in 5 to 10 minutes, with no pixel and no annual lock-in, at €99 per read or €299 per month on Pro. See how a causal read works on real GA4 data and bring your recovered AI segment to it.
Be honest about the ceiling, though. Triangulation gives you a defensible range, not a precise user-level count. For budget decisions, a range tied to caused revenue beats a precise number tied to nothing.
Then act on the result. If the causal read shows the recovered AI traffic genuinely adds revenue, fund the surfaces that feed it: answerable content, clean product data, and the assistant channels themselves. If it shows the traffic mostly harvests demand you already had, say so, and stop paying a premium for it.
Key takeaways
- Between 35% and 70% of AI-assistant sessions arrive with no referrer and land in Direct or Unassigned, which is why your Direct line grew.
- GA4's native AI Assistant channel (May 13, 2026) catches only part of the flow and misses Perplexity entirely; treat it as a floor.
- Audit in order: quantify the spike vs baseline, isolate AI-shaped sessions in Direct, build a regex channel group, then triangulate with a post-purchase survey.
- Industry analyses of the 2025 holiday season put AI-referred traffic up nearly 7x year over year (+693%), so the hidden share is now material to revenue.
- Buckets count sessions; only a causal read connects recovered AI traffic to caused revenue.
Further reading
Get attribution insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Key Terms in This Article
Attribution Window
Attribution Window is the defined period after a user interacts with a marketing touchpoint, during which a conversion can be credited to that ad. It sets the timeframe for assigning conversion credit.
Counterfactual
Counterfactual is a hypothetical outcome that would have occurred if a subject had received a different treatment.
Direct Traffic
Direct Traffic refers to website visitors who arrive by typing the URL directly into their browser or through bookmarks. They do not come from search engines or referrals.
Incrementality
Incrementality measures the true causal impact of a marketing campaign. It quantifies the additional conversions or revenue directly from that activity.
Landing Page
Landing Page: A single web page that appears after clicking a search result, marketing promotion, email, or online advertisement.
Product Page
Product Page is a webpage dedicated to a single product. It includes images, descriptions, pricing, and purchase options.
Product Pages
Product Pages are individual pages on an e-commerce site that describe a specific product. They provide detailed information to shoppers.
UTM Parameters
UTM Parameters are URL tags marketers use to track campaign effectiveness across traffic sources. They provide data for accurate campaign tracking and attribution in analytics platforms.
Related Articles
Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.
Ready to see your real numbers?
Own the budget? Upload your GA4 export and see which channels drive incremental sales, with confidence intervals, in minutes. Have to defend it? Start with the live demo and take the read to your CFO.
Full refund if you don't see value.
Stay ahead of the attribution curve
Weekly insights on marketing attribution, incrementality testing, and data-driven growth. Written for the person who owns the budget and the person who has to defend it.
No spam. Unsubscribe anytime. We respect your data.
Frequently Asked Questions
Why is my direct traffic growing in GA4?
The most common 2026 cause is AI assistants. Between 35% and 70% of sessions that start in ChatGPT, Copilot, or similar tools arrive with no referrer, so GA4 files them as Direct or Unassigned. Dark social sharing after assistant conversations adds more. A Direct spike with flat brand search is the classic signature.
When did GA4 add an AI Assistant channel?
On May 13, 2026, GA4 gave AI assistants their own native channel in the default channel groups. Sessions get re-bucketed when the referrer matches a known assistant domain, but the channel catches only part of AI traffic and misses Perplexity entirely, so Direct still hides a meaningful share of assistant-driven visits.
How do I build a regex channel group for AI referrals in GA4?
In GA4 Admin, open Channel groups, create a custom group, and add a channel whose Session source matches a regex such as chatgpt|openai|gemini|copilot|claude|perplexity|poe. Place it above Referral. This recovers sessions where the referrer survives; the no-referrer share stays in Direct regardless.
What percentage of AI referral traffic has no referrer?
Published 2026 analyses put the no-referrer share of AI-assistant sessions between 35% and 70%, depending on the assistant, device mix, and whether users copy links instead of clicking. Plan around the middle of that range and verify with your own landing-page and new-user segments in GA4.
Can I just trust the AI Assistant channel numbers?
Not alone. The channel misses Perplexity entirely and every session where the referrer was stripped, so it undercounts. Use it as a floor, recover more with a custom regex channel group, triangulate with a post-purchase survey, and treat the combined estimate as your working range.
How do I prove recovered AI traffic actually drives revenue?
Counting sessions is not causation. The proof is a causal read on your GA4 export, with context like promotions and seasonality annotated, comparing revenue against a counterfactual baseline. Causality Engine does this in 5 to 10 minutes for €99 per read, with no pixel or annual contract required.