GA4 pour AI Trafic

GA4 peut classify trafic with ordered custom channel rules; the premier matching channel wins. Evidence for this claim GA4 lets editors create custom channel groups from ordered rules, and a session is assigned to the first matching channel. Scope: GA4 custom channel groups; availability and limits depend on the property and product configuration. Confidence: high · Verified: 2026-07-14 Google Analytics: Custom channel groups Its session source and medium dimensions are the basic fields utilisé to inspect où visits originated. Evidence for this claim GA4 exposes session source and session medium as acquisition dimensions for analyzing where sessions originated. Scope: Observable acquisition metadata; traffic without a usable referrer or campaign tag can be unattributed or classified as direct. Confidence: high · Verified: 2026-07-14 Google Analytics: Traffic-source dimensions

TL;DR — GA4 peut now montrer vous visits from AI outils comme ChatGPT and Perplexity in two façons: a built-in AI Assistant channel que appeared in May 2026, and a custom channel groupe vous définir up yourself. The catch nobody warns vous à propos de: the order of votre channels matters — put votre AI channel ci-dessus Referral or votre AI visits obtenir miscounted. And aucun matter ce que vous définir up, a big chunk of AI trafic arrives with aucun source attached and lands in Direct, so treat the numbers vous voir as a minimum.

Ce que we’re en réalité setting up

Quand someone clicks a lien à l’intérieur ChatGPT, Perplexity, Gemini, or Claude, leur navigateur parfois indique votre site où ils came from — and parfois it doesn’t. Quand it fait, GA4 peut étiquette the visit as AI trafic. Ce article is à propos de getting GA4 to do que labeling bien, and alors building a report vous pouvez en réalité utiliser.

Là are two pieces:

1. The native AI Assistant channel. Google ajouté ce to GA4’s Par défaut Channel Groupe in May 2026. It’s automatic — vous don’t définir anything up — and it catches visits from recognized AI outils que arrive with a source attached.
2. A custom channel groupe. Vous construire ce yourself. It donne vous broader coverage and lets vous re-label old données aussi. It’s the même idea, simplement sous votre contrôler.

The premier vérifier: do vous déjà voir AI trafic?

Avant building anything, regarder. In GA4, go to Reports > Acquisition > Trafic acquisition and regarder at the Session par défaut channel groupe view. Si vous voir a row labeled AI Assistant, the native channel is live on votre property. That’s votre starting number.

The un rule que trips everyone up

Si vous construire a custom channel groupe, GA4 checks votre channels in order and arrête at the premier match. A visit from chatgpt.com counts as a “referral” — so si votre Referral channel sits ci-dessus votre AI channel, every AI visit obtient grabbed by Referral premier and jamais reaches the AI channel. Nothing errors. It simplement quietly miscounts.

The fix: drag votre AI channel ci-dessus Referral. That’s the whole trick.

Pourquoi votre AI number va regarder petit (and pourquoi that’s pas a bug)

A lot of AI outils — surtout leur phone apps — don’t réussir along où the visitor came from. Quand que se produit, GA4 has nothing to étiquette the visit with, so it dumps it into Direct, the même bucket as someone typing votre adresse by hand. Studies put the share of AI visits que vanish ce façon at somewhere entre 35% and 70%.

So the AI number vous voir is the floor, pas the ceiling. There’s aucun setting que recovers ceux hidden visits — it’s how the web fonctionne, pas a mistake in votre setup. (The deeper “why” behind que hidden trafic is its propre topic — ce article stays on the hands-on GA4 side.)

Vouloir the exact menu paths, the regex, the Explorations recipe, and the platform-by-platform UTM reality? Switch to the Avancé tab.

Custom channel definitions are ordered, so an précédent broad rule peut capture a session avant a plus tard AI-specific rule. Evidence for this claim GA4 lets editors create custom channel groups from ordered rules, and a session is assigned to the first matching channel. Scope: GA4 custom channel groups; availability and limits depend on the property and product configuration. Confidence: high · Verified: 2026-07-14 Google Analytics: Custom channel groups Source and medium analysis remains limited to acquisition information que reaches GA4. Evidence for this claim GA4 exposes session source and session medium as acquisition dimensions for analyzing where sessions originated. Scope: Observable acquisition metadata; traffic without a usable referrer or campaign tag can be unattributed or classified as direct. Confidence: high · Verified: 2026-07-14 Google Analytics: Traffic-source dimensions

TL;DR — Two layers: GA4’s native AI Assistant channel (Par défaut Channel Groupe, ajouté May 13, 2026 — automatic, referrer-only, pas retroactive, narrower recognized-source liste) and a custom channel groupe vous construire (broader, fonctionne on historical données, costs un of votre 2 standard-property custom-group slots). Channel order is load-bearing: GA4 assigns trafic to the premier channel whose definition it matches, so AI doit sit ci-dessus Referral or AI sessions obtenir silently absorbed into Referral. Setup is step un — the payoff is a Free Formulaire Exploration cross-tabbing Session source/medium × Landing page × clé events, and an AI segment vous pouvez reuse à travers quelconque report. UTM behavior is platform-specific: ChatGPT increasingly appends utm_source=chatgpt.com; Perplexity, Gemini, and Claude généralement don’t. Combining with Search Console is a manual URL-level join (GSC impressions × GA4 sessions on the même landing page), pas a native report — and GA4 can’t isolate AI Overviews from Organic Search at tout. Everything ici measures the referred slice; 35–70% arrives with aucun referrer and stays in Direct.

The two layers, and ce que chaque un en réalité covers

Since May 2026 là are two distinct façons to voir AI trafic in GA4, and it’s worth being precise à propos de ce que chaque fait.

Couche 1 — the native AI Assistant channel. On May 13, 2026, Google ajouté an AI Assistant channel to GA4’s Par défaut Channel Groupe. Google’s description: “AI Assistants is the channel by qui utilisateurs arrive at votre site from sources comme ChatGPT, Gemini, Deepseek, Copilot, or Grok.” Mechanically, quand a session’s referrer matches Google’s internal liste of recognized AI Assistant sources, GA4 assigns medium ai-assistant and campaign (ai-assistant) and routes it to ce channel. Three choses to know: it’s automatic (nothing to configurer), it’s referrer-only (aucun referrer, aucun classification), and it is pas retroactive — it classifies going forward from rollout, pas votre historical sessions. The recognized-source liste aussi isn’t entièrement publié, so treat it as a moving target.

Couche 2 — a custom channel groupe vous construire. Ce is où vous obtenir contrôler: broader domain coverage, the ability to re-segment historical données the native channel skips, and a channel que behaves exactly how vous define it. The cost is un of votre 2 custom channel groupes on a standard property (GA4 360 obtient 5; the predefined groupe doesn’t count contre the limite), and chaque groupe permet up to 50 channels. La plupart practitioners run les deux — the native channel pour a zero-maintenance baseline, a custom groupe pour the fuller picture.

The un chose neither couche peut do: separate Google’s AI Overviews / AI Mode clicks from regular blue-link Organic Search. Google’s channel definitions fold AI-feature clicks into Organic Search, and the referrer is indistinguishable from a normal Google click — so aucun regex and aucun custom channel peut pull les out. That’s a boundary condition to state and déplacer past; the pourquoi behind it is a whole topic of its propre.

The dark-traffic floor, stated une fois

Avant configuring anything, définir the expectation: a grand share of AI-driven visits — studies put it at 35% to 70% (Loamly’s 446 405-visit sample puts the élevé fin at 70,6%) — arrive with aucun referrer at tout and land in Direct by construction. That’s pas a detection échec GA4 pourrait fix; Direct is défini as the “no signal at all” bucket, so referrer-stripped AI visits fall là the même façon a typed-in URL fait. Nothing vous construire in ce article recovers ceux. The dark-traffic mechanism (referrer policies, noreferrer, in-app navigateurs, copy-paste) is covered in depth by the attribution deep dive — I’m stating the headline une fois and moving straight to ce que vous peut instrument.

Session-scoped vs. first-user dimensions — pick the correct field avant vous construire

GA4 exposes AI-source données at two différent scopes, and mixing les up quietly changements ce que a report is en réalité telling vous.

• Session source / medium (session-scoped) — records the source and medium pour que spécifique visit. Ce is the field every configuration step in ce article uses: the custom channel’s Source-matches-regex condition, the Exploration in Step 4, and the landing-page report in Step 5. It réponses “did ce visit come from an AI outil,” qui is the question ce article’s setup is construit to réponse.
• Premier utilisateur source / medium (user-scoped) — records the source and medium of a user’s very premier visit, and jamais changements après que aucun matter how nombreux times ils retourner via a différent channel. GA4’s Utilisateur acquisition report is construit on ce scope; Trafic acquisition is construit on the session scope.

Pourquoi c’est important ici: pull votre AI channel into a Utilisateur acquisition report à la place of Trafic acquisition and you’re asking a différent question — “how nombreux of our utilisateurs were premier acquired via AI” — not “how nombreux visits ce period came from AI.” A returning utilisateur who premier arrived via organic search and plus tard clicks back in from ChatGPT montre up as AI trafic in the session-scoped view and as Organic Search in the user-scoped un. Neither number is incorrect; ils réponse différent questions, and citing un pendant que meaning the autre misleads whoever reads the report.

Every report ce article builds — the Exploration in Step 4, the landing-page report in Step 5, the conversion comparison in Step 6 — is deliberately session-scoped, parce que “which visits did AI send, and to which pages” is a session-level question. Si vous aussi vouloir the user-scoped réponse (“how nombreux of our utilisateurs’ first-ever touch was AI”), construire a second, clearly-labeled Exploration en utilisant Premier utilisateur source / medium à la place, and don’t merge the two into un table. Google’s traffic-source dimensions documentation covers the complet scope distinction à travers every acquisition dimension, pas simplement source/medium.

Step 1 — vérifier si the native channel is déjà live

Reports > Acquisition > Trafic acquisition, switch the principal dimension to Session par défaut channel groupe, and regarder pour an AI Assistant row. Si it’s là, the native classification is running on votre property. Wide availability rolled out via early June 2026 (the exact “wide availability” date is secondary-sourced — Google dated the classification logic to May 13 but didn’t separately date the availability milestone), so si vous don’t voir the row yet, it may encore be arriving.

Step 2 — construire a custom channel groupe

Admin > Données afficher > Channel groupes > Créer nouveau channel groupe. (GA4 shuffles its Admin layout periodically — si que chemin has déplacé, search Admin pour “Channel groupes.” Vérifier live avant vous rely on quelconque screenshot, notamment mine.)

1. Nom the groupe something comme “AI + Default” so vous know En un coup d’œil Ce que c’est.
2. Ajouter nouveau channel, nom it AI.
3. Définir the condition: Source → matches regex → paste an anchored, domain-scoped pattern (voir the Scripts tab — do pas utiliser the overly broad “any string containing ai” patterns floating autour secondary summaries; ils false-positive on domains comme mail.com and wikipedia.org).
4. Drag the AI channel ci-dessus Referral. Ce is the load-bearing step (suivant section).
5. Enregistrer.

Pris en charge match fields, si vous vouloir to obtenir fancy: Campaign ID, Campaign nom, Par défaut channel groupe, Manual ad content, Medium, Source, and Source platform. Pour a belt-and-suspenders setup, ajouter a second condition matching utm_source containing chatgpt to aussi catch ChatGPT Search’s self-appended tag (plus on que ci-dessous).

Step 3 — obtenir the channel order correct (the silent échec mode)

Ce is the unique la plupart important sentence in the whole setup, straight from Google’s docs: “Trafic is inclus in the premier channel whose definition it matches donné the current order of channels in the groupe.” Lire que à nouveau with AI trafic in mind. A session from chatgpt.com legitimately matches Referral (it’s a referring domain). So si Referral sits ci-dessus votre AI channel in the ordering, every unique AI session obtient claimed by Referral premier and jamais reaches votre AI channel.

There’s aucun error. Aucun warning. Aucun red flag in the UI. The report simplement quietly reads zero (or near-zero) AI trafic pendant que votre AI channel silently ne fait pashing — and you’ll spend an afternoon debugging a regex que was fine tout along. Drag AI ci-dessus Referral, enregistrer, and confirmer by checking que the AI row now has sessions in a Trafic acquisition report scoped to votre custom groupe.

Step 4 — the partie la plupart guides skip: construire an Exploration

A channel is a étiquette. It indique vous how beaucoup AI trafic vous got. It ne fait pas tell vous qui pages got it or si quelconque of it converted — and that’s the partie stakeholders en réalité care à propos de. Que lives in an Exploration.

Explore > Blank (Free Formulaire). Alors:

• Dimensions: ajouter Session source / medium, Landing page + requête string, and optionally Session par défaut channel groupe (or votre custom groupe). Drag Landing page into Rows and Session source/medium into a secondary row or a column.
• Metrics: ajouter Sessions, Engagement rate, and — the un que matters — votre Clé events (conversions). Revenue aussi, si vous have ecommerce or a valeur on votre clé events.
• Filter or segment to AI sources. Vous pouvez ajouter a filter (Session source/medium matches regex votre AI domains), but the meilleur déplacer is to construire a reusable segment (suivant section) so ce view drops into quelconque report, pas simplement ce un.

Now vous have a table que réponses réel questions: qui landing pages AI outils send trafic to, how engaged que trafic is, and ce que it converts.

Construire the AI segment une fois, reuse it everywhere

In the Exploration’s Segments panel, + > Construire a nouveau segment > Session segment. Condition: Session source / medium matches regex with votre AI pattern (and, si vous vouloir ChatGPT Search’s tagged trafic, an OR condition on utm_source containing chatgpt). Nom it AI Sources. Now vous pouvez:

• Drop it into quelconque Exploration alongside Organic Search, Paid, and Referral segments pour side-by-side comparison.
• Comparer AI’s engagement and taux de conversion contre votre autre channels in the même table — qui is far plus persuasive que quoting a conversion stat from someone else’s blog post.

A segment is plus flexible que a channel parce que it isn’t bound to un report or un channel-group slot. Construire les deux — the channel pour at-a-glance reporting, the segment pour analysis.

Step 5 — the landing-page-by-AI-source report (the la plupart actionable un)

Si vous construire un report from ce article, construire ce. Landing page in Rows, votre AI Sources segment applied, Sessions and Clé events as metrics. Ce que vous obtenir is a ranked liste of lune pages AI outils are en réalité driving personnes to — qui is a usable proxy pour qui of votre content is winning citations and retrieval in AI réponses.

Que faire with the output: double bas on lune page types que concentrate AI trafic. Quand Ahrefs ran ce analysis on our propre données, we trouvé que 80% of our AI search trafic went to our homepage, product pages, and free outils — pas our blog posts. That’s exactly the kind of insight ce report surfaces: it indique vous où to invest (plus free outils, stronger product pages) plutôt que guessing. Votre concentration va differ, but the report type is the même.

Step 6 — conversion and revenue reporting pour AI trafic

Session count is the vanity number; conversions are the un que obtient budget. Appliquer votre AI Sources segment to votre standard key-event / conversion reports, or construire the comparison directement in an Exploration with Sessions, Clé events, and (si vous have it) Revenue as metrics, segmented AI vs. Organic vs. Paid. The story que tends to land with stakeholders is taux de conversion, pas volume — AI trafic is frequently a petit share of sessions que punches bien ci-dessus its weight on conversions, so a table que montre “AI is 1% of sessions but converts at Nx organic” reframes the whole conversation. (The spécifique conversion-premium figures — the 23x and Loamly’s 10,21% vs 2,46% numbers — are owned by the attribution sibling; pull votre propre numbers from ce report plutôt que quoting theirs.)

Step 7 — UTM tagging: platform-specific, pas “AI strips everything”

The blanket claim you’ll lire everywhere — “AI platforms strip tout UTMs, so tagging is pointless” — is incorrect in les deux directions. The reality in 2026:

• ChatGPT increasingly appends its propre utm_source=chatgpt.com on some outbound liens, notably from ChatGPT Search. Ce is the rare cas of an AI platform making attribution easier — worth catching with a utm_source condition in votre channel or segment. (Moteur de recherche Roundtable reported OpenAI expanding ce behavior; the page 403’d during research, but multiple secondary sources corroborate the direction.)
• Perplexity, Gemini, and Claude généralement don’t ajouter or preserve UTMs on cited liens. Aucun vendor documents its outbound-link behavior, so ce is from independent testing, pas official docs — treat it as “here’s what testing shows,” qui is the honest framing pour tout of ce.
• None of it helps with liens vous don’t contrôler. Quand an AI outil cites vous, it cites l’URL canonique it trouvé — pas some tagged URL you’d comme it to utiliser. Vous ne peut pas UTM-tag votre façon into attribution pour citations.

Où UTM tagging fait encore earn its garder: liens vous placer yourself in votre propre outbound content (newsletters, syndication, citation-bait vous publish elsewhere), où vous contrôler l’URL and peut tag it — provided the destination platform doesn’t scrub it. Marginal, but réel. Simplement don’t expect it to solve the citation-attribution problem, parce que it structurally can’t.

Step 8 — combining with Search Console pour AI-features context

Google’s Gen AI performances reports (June 3, 2026) surface votre appearances in “AI Overviews, AI Mode, and generative AI fonctionnalités in Découvrir” — but impressions seulement: aucun clicks, aucun CTR, aucun position. So vous pouvez’t obtenir “AI Overview clicks” from GSC quelconque plus que vous pouvez from GA4.

The practical workaround is a manual URL-level join, and it’s worth being blunt que it’s manual:

1. In Search Console > Performances, filter by the AI-features search-appearance type and export the pages que apparaître (impressions).
2. In GA4, ouvrir votre landing-page report (Step 5) and pull sessions/clé events pour ceux même URLs.
3. Join the two exports on landing-page URL — pas on channel, parce que GA4 can’t isolate AI-feature clicks, so a channel join is impossible.

The output indique vous qui URLs are showing up in AI fonctionnalités (GSC impressions) and ce que ceux même URLs do in GA4 (sessions, conversions). Si you’ve lié GA4 and GSC via Admin > Product liens > Search Console liens, some of ce surfaces in GA4’s Search Console reports — but the AI-feature slice encore exige the manual join parce que neither product tags sessions as “came from an AI Overview.” Définir expectations accordingly: ce is a workflow, pas a button.

Cross-reference Bing Webmaster Outils’ AI Performances report (public preview, Feb 2026) the même façon — it exposes citations and the grounding requêtes Copilot searched to trouver vous. Copilot’s referrer behavior is inconsistent (Copilot web passes un intermittently; the Windows app jamais fait), so a GA4 regex under-counts Copilot aucun matter ce que — the Bing citation count is votre cross-check.

Où ce encore falls short

Several honest limites, alors hand off:

1. The 35–70% dark floor is untouched by everything ci-dessus. You’re instrumenting the referred slice bien; the referrer-less slice stays in Direct.
2. AI Overviews / AI Mode can’t be isolated — permanently merged into Organic Search by Google’s propre channel definitions.
3. Longer-range reports run into retention, pas simplement referrers. GA4’s event-level données retention (Admin > Données settings > Données retention) defaults to 2 months and tops out at 14 — an Exploration construit on event-scoped données can’t regarder back plus loin que que window, independent of anything AI-related. Votre property’s commencer date is a second hard boundary: there’s aucun AI trafic to report avant the property existed or avant vous commencé collecting. And in contexts où consent signals fall ci-dessous GA4’s reporting thresholds, low-count rows — a thin AI-traffic segment is a prime candidate — obtenir modeled or suppressed plutôt que affiché as zero. Don’t lire a manquant row as “no AI traffic”; lire it as “ci-dessous the reporting threshold, or outside the retention window.”
4. Channel-group edits peut modifier how a report reads, notamment pour past dates. Renaming, reordering, or ajout a rule to votre custom channel groupe peut modifier how already-collected sessions obtenir classified the suivant temps vous pull a report, since custom groupes are evaluated contre current rules at requête temps. A mid-quarter regex edit peut quietly shift a month-over-month AI comparison — remarque the date whenever vous edit the groupe, the même discipline the regex modifier log ci-dessous déjà demande pour.
5. A conversion comparison from Step 6 is session-scoped counting, pas multi-touch attribution credit. The Exploration technique in ce article counts Sessions and Clé events directement. GA4’s separate Attribution reports appliquer a choisi attribution model (data-driven by par défaut) que peut assign AI a différent share of credit in journeys with plus que un touchpoint. Si vous besoin AI’s multi-touch credit plutôt que its session-level volume, pull que number from Attribution, pas from the Exploration technique in Steps 4–6.

Pour the complet “why it’s dark and what to do about the Direct baseline,” voir the AI trafic attribution deep dive; pour où GA4 sits à l’intérieur the broader five-layer measurement approach, voir the measurement and reporting hub. Ce article is the config; ceux propre the strategy.

AI summary

A condensed prendre on the Avancé version:

• Two layers. Native AI Assistant channel (Par défaut Channel Groupe, ajouté May 13, 2026 — automatic, referrer-only, pas retroactive, narrower/unpublished source liste) plus a custom channel groupe vous construire (broader coverage, fonctionne on historical données, costs un of 2 standard-property slots; 360 obtient 5).
• Premier vérifier: Reports > Acquisition > Trafic acquisition, Session par défaut channel groupe — regarder pour an “AI Assistant” row.
• Construire: Admin > Données afficher > Channel groupes > nouveau groupe; channel named AI; Source matches regex on AI domains (anchored, pas “any string with ai”).
• The load-bearing rule — channel order. GA4 assigns trafic to the premier channel it matches, so AI doit sit ci-dessus Referral or every AI session obtient silently absorbed into Referral with aucun error.
• Setup is step un. The payoff is a Free Formulaire Exploration: Session source/medium × Landing page × Clé events — and a reusable AI segment droppable into quelconque report pour side-by-side comparison vs. Organic/Paid.
• La plupart actionable report: landing-page-by-AI-source (proxy pour qui pages win citations/retrieval); conversion/revenue reporting reframes AI from a petit session share to a high-converting un.
• UTMs are platform-specific: ChatGPT increasingly appends utm_source=chatgpt.com; Perplexity/Gemini/Claude généralement don’t; none of it tags liens vous don’t contrôler.
• GSC combine = manual URL join (GSC AI-feature impressions × GA4 sessions on the même landing page); GA4 can’t isolate AI Overviews from Organic Search.
• Scope matters. Construire reports on Session source/medium (session-scoped — “did this visit come from AI”) pas Premier utilisateur source/medium (user-scoped — “was this user’s first-ever touch AI”). Ils réponse différent questions.
• Hard floor: 35–70% of AI visits arrive with aucun referrer and stay in Direct — everything ici measures the referred slice seulement.
• Autre limites: event-data retention (2–14 months) and property commencer date bound how far back an Exploration peut regarder; consent-based thresholding peut suppress a thin AI segment’s rows; custom channel-group edits peut re-classify past sessions on suivant lire, so log the date quand vous modifier un; and a session-scoped conversion comparison isn’t the même number as GA4’s model-based Attribution reports.

Documentation officielle

Primary-source documentation pour configuring GA4 and reading AI-feature données.

Google Analytics

• What’s nouveau in Analytics — AI Assistant channel — the May 13, 2026 entry announcing the AI Assistant Par défaut Channel Groupe channel.
• Par défaut Channel Groupe definitions — the authoritative per-channel rule table, notamment the AI Assistants channel and the Direct channel’s “no signal” definition.
• Créer, edit, and appliquer custom channel groupes — the mechanics doc: ajout channels, match conditions, the first-match ordering rule, and property limites (2 custom groupes on standard, 5 on 360).
• Analyze données with Explorations — the Explore workspace, Free Formulaire technique, dimensions, metrics, and segments.
• Traffic-source dimensions, manual tagging, and auto-tagging — the session-scoped vs. first-user (user-scoped) distinction behind the report-building remarque ci-dessus.
• Données retention — event-level retention windows (2–14 months) que bound how far back an Exploration peut regarder.
• Obtenir commencé with attribution — how GA4’s Attribution reports assign model-based credit, as distinct from the session-scoped counting ce article’s Explorations utiliser.

Recherche Google (pour the GSC join)

• Gen AI performances reports (June 3, 2026) — AI Overviews, AI Mode, and generative-AI Découvrir appearances, impressions seulement.
• AI fonctionnalités and votre website — how Google’s AI fonctionnalités surface votre content.

Bing / Microsoft

• Introducing AI Performances in Bing Webmaster Outils (public preview) — total citations, average cited pages, and the grounding requêtes Copilot utilisé to trouver vous.

Quotes from the source

On-the-record statements relevant to configuring GA4 pour AI trafic. Chaque lien is a deep lien que jumps to the quoted passage où lune page permet it.

Google — the native AI Assistant channel

• “You can now identify how users are discovering your site through chatbots like ChatGPT, Gemini, and Claude via a new AI Assistant channel in your Default Channel Group reports.” — GA4 “What’s new,” May 13, 2026. Jump to quote

Google — the AI Assistants channel definition

• “AI Assistants is the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok.” — GA4 Par défaut Channel Groupe definitions. Lire the definition

Google — the Direct channel (pourquoi referrer-less AI lands ici)

• “Direct is the channel by which users arrive at your site/app via a saved link or by entering your URL.” Its rule exige source (direct) and medium (not set) or (none) — i.e., aucun signal at tout. — GA4 Par défaut Channel Groupe definitions. Lire the definition

Google — the channel-ordering rule (the load-bearing sentence)

• “Traffic is included in the first channel whose definition it matches given the current order of channels in the group.” — GA4 custom channel groupes doc. Ce is pourquoi the AI channel doit sit ci-dessus Referral. Lire the doc

Google — Search Console Gen AI reports (impressions seulement)

• The June 2026 Gen AI performances reports cover “AI Overviews, AI Mode, and generative AI features in Discover” — impressions seulement, with aucun clicks, CTR, or position. — Recherche Google Central blog. Lire the announcement

Patrick Stox, Ahrefs — pourquoi so beaucoup AI trafic lands in Direct

• “Websites have control over what info they send. They can send the full path, just the origin, or nothing — it’s up to them. We report whatever referrer we’re told to report. If they don’t send us one, then it would go in the ‘Direct’ bucket.” — from my write-up on AI assistants breaking web analytics. Lire the post

Qui AI-traffic setup do vous besoin?

Fonctionner bas from ce que vous have today to the correct suivant configuration step.

SOP: définir up AI-traffic tracking in a GA4 property

A repeatable procedure pour standing ce up on un property (or the même steps per client). Budget ~20 minutes the premier temps.

1. Establish the baseline. Reports > Acquisition > Trafic acquisition → principal dimension Session par défaut channel groupe → remarque si an AI Assistant row exists and its current session count.
2. Créer the custom channel groupe. Admin > Données afficher > Channel groupes > Créer nouveau channel groupe. Nom it “AI + Default.”
3. Ajouter the AI channel. Ajouter nouveau channel → nom AI → condition Source matches regex → paste votre anchored AI-domain pattern (Scripts tab). Optionally ajouter an OR condition: Manual term / utm_source contient chatgpt to catch ChatGPT Search’s tag.
4. Order it. Drag the AI channel ci-dessus Referral. Enregistrer.
5. Vérifier the order worked. Ouvrir a Trafic acquisition report scoped to the nouveau groupe; confirmer the AI row now montre sessions (pas zero). Si it’s zero and vous know vous have AI referrals, re-check the ordering premier, the regex second.
6. Construire the reusable AI segment. Explore > Blank > Segments > + > Session segment → Session source / medium matches regex (même pattern) → nom it AI Sources.
7. Construire the landing-page Exploration. Free Formulaire → Rows: Landing page + requête string → Metrics: Sessions, Engagement rate, Clé events → appliquer the AI Sources segment. Enregistrer it.
8. Ajouter the conversion comparison. Duplicate the Exploration; ajouter Organic Search and Paid segments alongside AI Sources; comparer Clé events and taux de conversion side by side. Ce is votre stakeholder view.
9. Définir up the GSC cross-reference. Admin > Product liens > Search Console liens (lien si pas déjà). Establish the monthly manual join: export GSC AI-feature impression pages, match to GA4 landing-page sessions/conversions on the même URLs.
10. Document the floor. In whatever report vous share, ajouter a one-line caveat que 35–70% of AI trafic is referrer-less and invisible ici, so ces are minimums.

Recurring maintenance (quarterly): re-check the regex contre newly prominent AI platforms, confirmer GA4’s Admin paths haven’t déplacé, and re-verify the channel order survived quelconque channel-group edits.

Ce que pas to do

The recurring mistakes que faire GA4 AI tracking misleading — chaque with pourquoi it’s incorrect and Que faire à la place.

1. “GA4 tracks all AI traffic automatically since the May 2026 update.” Pourquoi it’s incorrect: the native AI Assistant channel seulement catches sessions que arrive with a recognized referrer. The 35–70% dark-traffic floor is complètement untouched by the mettre à jour, and the recognized-referrer liste is narrower and pas entièrement publié. Do à la place: treat the native channel as a floor-of-a-floor, watch votre Direct baseline as the réel diagnostic, and jamais report the AI Assistant number as “our AI trafic” sans the caveat.

2. Leaving the AI channel ci-dessous Referral. Pourquoi it’s incorrect: GA4 arrête at the premier matching channel. chatgpt.com is a valid referral, so an AI channel placed ci-dessous Referral catches nothing — silently, with aucun error. You’ll think votre regex is broken. Do à la place: drag AI ci-dessus Referral and vérifier the AI row has sessions avant trusting the report.

3. En utilisant an over-broad regex comme “any string containing ai.” Pourquoi it’s incorrect: patterns que match quelconque substring ai false-positive on mail.com, wikipedia.org, retail.com, and dozens plus, inflating votre AI number with non-AI trafic. Do à la place: utiliser anchored, domain-scoped alternation (chatgpt\.com|perplexity\.ai|…) — voir the Scripts tab. Vérifier it in the live GA4 UI avant publishing it to a client.

4. Stopping at the channel groupe and appel it fait. Pourquoi it’s incorrect: a channel is a étiquette with aucun analysis behind it. It indique vous how beaucoup AI trafic arrived but pas qui pages got it or si it converted — the questions que en réalité drive decisions. Do à la place: construire the landing-page Exploration and the conversion comparison. Setup is step un, pas the finish line.

5. Assuming “AI platforms strip all UTMs, so tagging is pointless.” Pourquoi it’s incorrect: it’s platform-specific. ChatGPT increasingly appends its propre utm_source=chatgpt.com; Perplexity, Gemini, and Claude généralement don’t ajouter UTMs; and none of it s’applique to liens vous don’t contrôler (AI cites votre URL canonique, pas a tagged un). Do à la place: ajouter a utm_source contient chatgpt condition to catch the tagged trafic, and tag seulement the outbound liens vous en réalité contrôler.

6. Expecting GA4 to filter to “traffic from AI Overviews.” Pourquoi it’s incorrect: AI Overview and AI Mode clicks are permanently merged into Organic Search by Google’s propre channel definitions — the referrer is indistinguishable from a normal Google click, so aucun regex or custom channel peut separate les. Do à la place: accept the boundary; utiliser the manual GSC-impressions × GA4-sessions join on landing-page URL to obtenir some AI-features context.

GA4 AI-traffic setup checklist

A réussir to confirmer votre AI tracking is configuré and en réalité reporting:

• Vérifié Trafic acquisition (Session par défaut channel groupe) pour a native AI Assistant row and noted the baseline.
• Créé a custom channel groupe with an AI channel (Source matches regex).
• Regex is anchored and domain-scoped — aucun “any string containing ai” patterns que false-positive on mail.com / wikipedia.org.
• The AI channel sits ci-dessus Referral in the channel order.
• Verified the AI row montre sessions (pas zero) après fixing the order.
• Optional: ajouté a utm_source contient chatgpt condition to catch ChatGPT Search’s self-appended tag.
• Construit a reusable AI Sources segment (pas simplement a channel).
• Construit a landing-page × AI-source Exploration (Landing page + Session source/medium × Sessions + Clé events).
• Construit the conversion comparison (AI vs. Organic vs. Paid, clé events + taux de conversion).
• Lié GSC (Admin > Product liens) and established the manual AI-feature impressions × GA4 sessions join on landing-page URL.
• Cross-checked Bing Webmaster Outils AI Performances citations pour Copilot (qui under-counts in a GA4 regex).
• Documented the 35–70% dark-traffic floor caveat on quelconque shared report.
• Confirmed you’re pas claiming to isolate AI Overviews (merged into Organic).

GA4 AI-traffic cheat sheet

The two layers

Menu paths (vérifier live — GA4 Admin shifts)

The rule que breaks setups

• GA4 assigns chaque session to the premier channel it matches → AI doit sit ci-dessus Referral, or AI sessions are silently absorbed into Referral.

UTM behavior by platform

Fast facts

• Custom channel groupes: 2 on standard properties, 5 on GA4 360; 50 channels per groupe.
• GSC Gen AI reports = impressions seulement (aucun clicks/CTR/position).
• AI Overviews / AI Mode = merged into Organic Search, pas separable in GA4.
• Dark-traffic floor: 35–70% of AI visits arrive referrer-less → Direct.

The regex (anchored, pas broad)

The AI channel’s condition is Source matches regex. Do pas reproduce the loose “any string containing ai” patterns que circulate in secondary summaries — ils false-positive on mail.com, wikipedia.org, retail.com, and plus. Anchor to réel domains with escaped dots and alternation.

Minimal, high-signal (the platforms que en réalité send trafic):

(chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com)

Fuller coverage (ajouter the long tail as ils grow):

chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|deepseek\.com|grok\.com|x\.ai|meta\.ai|chat\.mistral\.ai|you\.com|phind\.com|poe\.com|pi\.ai

Toujours vérifier the pattern contre votre propre Referrals report premier — vérifier Reports > Acquisition > Trafic acquisition, ajouter Session source as a secondary dimension, and voir qui AI hostnames en réalité apparaître in votre données avant hard-coding a liste. Alors confirmer the pattern behaves in GA4’s live channel-group UI (the field’s regex flavor and cas handling peut surprise vous).

Tester cas avant vous enregistrer the pattern. Ce liste is dated to 2026-07-18 — AI platforms launch and rename souvent, so re-derive it from votre propre Referrals report plutôt que trusting quelconque static liste forever:

Run chaque row via GA4’s channel-group UI (or a regex tester en utilisant the même flavor) avant saving — a pattern que passes votre read-through but fails un of ces rows va misclassify live trafic.

Garder a modifier log. Every temps vous ajouter, supprimer, or re-anchor a domain in the pattern, remarque the date and ce que modifié suivant to votre channel-group documentation. Nouveau AI platforms apparaître and some fold or rebrand; a dated log is ce que lets vous (or whoever inherits ce property) tell “AI traffic dropped” from “we stopped matching a domain que renamed itself” months plus tard. It’s the même discipline the Avancé lens’s “Where this still falls short” section demande pour quand vous edit the channel groupe itself.

Voir the referrer an AI click en réalité sent — Chrome DevTools Console

Attribution problems are usually referrer problems. To voir exactly ce que a réel click from an AI outil handed votre page, click via from the AI réponse to votre site, ouvrir DevTools > Console, and run:

// What referrer did this navigation carry?
console.log("referrer:", document.referrer || "(empty — no referrer sent)");

// Any UTM tags on the landing URL? (catches ChatGPT's utm_source=chatgpt.com)
console.log(
  "utm params:",
  Object.fromEntries(new URLSearchParams(location.search).entries())
);

An vide document.referrer is the dark-traffic cas in miniature: que visit va land in Direct aucun matter ce que channel groupe vous construire. A populated utm_source (souvent chatgpt.com) is the cas votre utm_source channel condition catches.

A bookmarklet to vérifier referrer + UTMs on quelconque page

Drop ce into a bookmark’s URL field; click it après arriving from an AI outil to obtenir a one-glance readout sans opening DevTools:

javascript:(function(){var r=document.referrer||"(empty)";var u=location.search||"(none)";alert("Referrer:\n"+r+"\n\nQuery/UTMs:\n"+u);})();

Extract AI-referrer hostnames from votre GA4 export (shell)

Si vous export a Trafic acquisition report (or requête the GA4 Données API), ce pulls the distinct source hostnames que regarder comme AI platforms so vous pouvez construire a data-driven regex au lieu de guessing:

# sources.csv: one Session source per line (from a GA4 export)
grep -Ei 'chatgpt|openai|perplexity|claude|gemini|copilot|deepseek|grok|meta\.ai|mistral|you\.com|phind|poe|pi\.ai' sources.csv \
  | sort -u

Feed the deduped liste back into the alternation pattern ci-dessus — que façon votre regex matches what’s genuinely in votre données, escaped-dot by escaped-dot.

Outils pour measuring AI trafic

• GA4 — Reports > Acquisition > Trafic acquisition — the native AI Assistant channel baseline and votre custom-channel-group view.
• GA4 — Explore (Explorations) — Free Formulaire reports pour landing-page × AI-source and conversion cross-tabs; où the réel analysis se produit.
• GA4 — Admin > Channel groupes — construire and order votre custom AI channel (mind the above-Referral rule).
• Recherche Google Console — Performances (Gen AI reports) — AI Overviews / AI Mode / Découvrir impressions to join contre GA4 landing pages (impressions seulement).
• Bing Webmaster Outils — AI Performances report — Copilot citations and grounding requêtes; the cross-check pour Copilot trafic a GA4 regex under-counts.
• Ahrefs Web Analytics — a purpose-built alternative with its propre AI channel, si vous vouloir a second lire que isn’t dependent on GA4’s channel model. Même underlying dark-traffic limite s’applique to quelconque analytics outil.
• Chrome DevTools Console — inspect document.referrer and the landing URL’s UTMs on a réel AI click (voir Scripts).

Vérifier AI-source classification avant publishing a report

Tester to run: Utiliser a tagged tester lien or a controlled referrer fixture que matches chaque custom channel rule, alors inspect le résultating source/medium and channel in GA4. Attendu result: Recognized AI sources enter the intended custom channel sans swallowing unrelated referral or organic sessions. Échec interpretation: A regular expression is aussi broad, aussi narrow, or evaluated in the incorrect channel-rule order. Monitoring window: Après GA4 processes the tester event. Rollback trigger: The rule reclassifies a material définir of connu non-AI sources.

Vérifier report totals reconcile

Tester to run: Comparer the custom AI channel report with an exploration filtered by the même source/medium definitions and examiner a sample of underlying sources. Attendu result: The même défini referred sessions apparaître in les deux views, with differences explained by report scope, date, or processing. Échec interpretation: Filters, attribution settings, or channel definitions ne faites pas match. Monitoring window: Après the selected reporting period has processed. Rollback trigger: The nouveau report ne peut pas be reconciled or removes established historical channel context.

Ressources utiles

My connexe writing

• How to Track and Analyze Votre AI Trafic — my/Ahrefs’ walkthrough of setting up AI-traffic tracking, notamment channel-group and reporting steps.
• AI Assistants Are Breaking Web Analytics and Hurting Leur Future — the per-platform referrer testing behind pourquoi so beaucoup AI trafic lands in Direct.
• Google Made It So Vous pouvez’t Track Clicks From AI Mode (Partially Fixed) — the noreferrer behavior I reported, and pourquoi Google’s propre AI can’t be isolated in GA4.
• 80% of Our AI Search Trafic Goes to Our Homepage, Product Pages, and Free Outils — a worked exemple of exactly the landing-page-by-AI-source insight ce article teaches vous to construire.

My speaking

• How Search Fonctionne (SlideShare) — my walkthrough of exploration, rendering, indexation, and ranking, pour context on où AI-search measurement fits. (My standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)

Official

• GA4 — What’s nouveau (AI Assistant channel) and Custom channel groupes.
• Recherche Google Central — Gen AI performances reports.

From autour the industry

• Google Analytics Adds AI Assistant As Par défaut Channel Groupe (Moteur de recherche Journal) — coverage of the May 13, 2026 rollout.
• How to Track AI Trafic in GA4 (Orbit Media, Andy Crestodina) — a solid practitioner walkthrough of the channel-group approach.
• Tracking AI Trafic in GA4: A Step-by-Step Guide (Two Octobers) — step-by-step channel-group setup.
• How to Track AI and LLM Chatbot Trafic in GA4 (Tripledart) — un autre configuration référence.
• AI Trafic in Google Analytics 4 (Analytics Mania) — channel-group setup (arrête avant Explorations/conversions, qui is où ce article picks up).
• The AI Trafic Attribution Crisis (Loamly) — the 446 405-visit study behind the 70,6% referrer-less figure.
• r/GoogleAnalytics — community debugging pour channel groupes and Explorations.

Stats worth citing

• 35–70% of AI visits arrive with aucun referrer and land in Direct — the hard floor every GA4 configuration runs into. The 70,6% élevé fin comes from Loamly’s 446 405-visit sample. Source
• 80% of Ahrefs’ AI search trafic went to the homepage, product pages, and free outils — a worked exemple of ce que a landing-page-by-AI-source report surfaces (page- type concentration vous pouvez act on). Source
• Native AI Assistant channel ajouté May 13, 2026 to GA4’s Par défaut Channel Groupe — automatic, referrer-based, and pas retroactive. Source
• Custom channel groupe limites: 2 on standard GA4 properties, 5 on GA4 360, up to 50 channels chaque — the budget you’re spending quand vous construire an AI channel. Source
• GSC Gen AI reports are impressions-only (aucun clicks, CTR, or position), qui is pourquoi combining with GA4 is a manual URL-level join plutôt que a native report. Source

Testez vos connaissances: GA4 pour AI Trafic

Five rapide questions on configuring GA4 to voir AI trafic. Pick an réponse pour chaque, alors vérifier.

Journal des modifications