Find AI-source sessions, inspect entry pages and useful outcomes, and troubleshoot attribution in GA4 with a precise regex, optional channel group, and hypothetical walkthrough.
To track AI traffic in GA4, start with Traffic acquisition, inspect Session default channel group, and compare the assistant sources in Session source / medium. GA4 now has an AI Assistant channel, so a custom channel group is an optional reporting tool rather than a prerequisite.
This guide takes you from finding ChatGPT, Perplexity, Claude, and Gemini sessions to checking their landing pages and useful outcomes. You will build an auditable source filter, create an optional channel group, and validate the setup without confusing source labels with proof of a recommendation.
GA4 documentation checked on 12 October 2026. Configuration examples and the numerical walkthrough are illustrative, not results from a live analytics property.
What Counts as AI Traffic in Google Analytics?
For website reporting, distinguish three activities: a person clicking a website link in an assistant answer, an automated visit carrying an assistant referrer, and a crawler fetching content. Keep them separate when evaluating acquisition. A crawler request may never execute your GA4 tag, while a source label alone cannot establish who generated a recorded session.
Google’s current rules classify recognized assistant referrers under AI Assistant, with medium ai-assistant and campaign (ai-assistant). Non-ad clicks from Google’s AI Overviews and AI Mode belong to Organic Search. Older data, unrecognized sources, or manually tagged links may have different values. See Google’s default channel definitions.
Do not filter only for
/ referralwhen checking AI traffic. Inspect the source and channel together, and compare equivalent dates before interpreting a change.

Find AI Traffic in GA4: The Quick Check
Start with the existing acquisition report before changing any settings. Use a completed reporting period, note the property’s time zone, and check the same destination and dates throughout the exercise. A channel total is the starting point; source-level rows explain which assistants contributed to it.
- Open the correct GA4 property and choose the reporting dates.
- Go to Reports → Acquisition → Traffic acquisition. If the report is absent, an Editor or Administrator can add it to the reporting collection.
- Choose Session default channel group and look for AI Assistant.
- Switch to Session source / medium, or add it as a secondary dimension. Search for an observed source such as
chatgpt.comorperplexity.ai. - Record the sessions, engaged sessions, and key events for each source. Review the landing pages using the Exploration below.
Use session-level dimensions for session acquisition. User acquisition answers a different question about first-time acquisition, so its totals should not be treated as an interchangeable version of this report. Google’s Traffic acquisition instructions explain the report and its navigation.
If the AI Assistant row is empty, check individual sources before concluding there are no AI visits. A missing row can reflect your dates, the collected source values, or a lack of matching sessions. It is not evidence that your site has never appeared in an AI answer.

Assistant Domains to Check in Your Reports
The table lists assistant web hosts to investigate. These are not a guaranteed list of emitted referrers: apps, redirects, link tags, and browser policies can change what reaches your site. Confirm the actual Session source and Page referrer in your own data before extending a rule. Google’s recognition list can also differ from your custom list.
| Assistant | Hosts to inspect | Important check |
|---|---|---|
| ChatGPT | chatgpt.comchat.openai.com (legacy) |
Check the actual source and any preserved campaign tags on a search or citation click. |
| Perplexity | perplexity.ai |
Inspect the source received from a web citation click; do not assume the app passes the same value. |
| Claude | claude.ai |
Check a click from a linked answer, including any redirect. |
| Gemini | gemini.google.com |
Keep Gemini separate from ordinary Google Search and Google AI Overviews. |
| Microsoft Copilot | copilot.comcopilot.microsoft.com |
Microsoft documents migration to copilot.com. Retain older observed sources when comparing historical data. |
| DeepSeek | chat.deepseek.com |
Use the chat host as a starting point, then verify the source in your property. |
| Grok | grok.com |
A generic x.com source cannot identify a Grok click separately from other X activity. |
| Meta AI | meta.ai |
Do not classify all Facebook, Instagram, or WhatsApp traffic as Meta AI. |
| Mistral assistant | chat.mistral.ai |
Inspect the assistant host; the corporate domain alone is too broad. |
Provider links in the first column establish product hosts, not a promise about every outbound click. A source is a processed attribution value; Page referrer is an event-level URL when collected. A tagged source such as chatgpt is not the same string as chatgpt.com. Add non-domain aliases only after checking their origin. Google’s page_referrer reference and campaign tagging guide explain these inputs.

A Copyable Regex for Assistant Source Domains
Use this starter pattern with Source → matches regex in a custom channel, or Session source → matches regex in an Exploration. It matches exact domain boundaries and subdomains of the listed assistant hosts.
^([a-z0-9-]+\.)*(chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.com|copilot\.microsoft\.com|chat\.deepseek\.com|grok\.com|meta\.ai|chat\.mistral\.ai)$
Select and copy the entire line, including ^ and $. This is our conservative starter definition, not Google’s complete assistant recognition list. It intentionally excludes generic google.com, bing.com, openai.com, x.com, and facebook.com.
It matches chatgpt.com and www.perplexity.ai, but excludes notchatgpt.com, chatgpt.com.example.org, and a full URL such as https://chatgpt.com/. Do not paste it unchanged into a Page referrer URL filter. GA4 uses full regex matching by default; case sensitivity can differ by context, so inspect your source strings and test your condition. See Google’s regex reference.

Create an Optional “AI Assistants” Channel Group
A custom definition is useful when you need a maintained source roster, historical comparison, or a grouping specific to your organization. Creating it does not recover lost referrers or validate the visits.
- With Editor or Administrator access, open Admin → Data display → Channel groups.
- Select Create new channel group, using the default group’s channels as the starting point. Name the group AI source review.
- Choose Add new channel; name the channel AI Assistants.
- Add a condition group, choose Source, select matches regex, and paste the domain pattern above.
- Select Save channel. Choose Reorder, move your new channel above the existing AI Assistant and Referral channels, and click Apply.
- Select Save group. In Traffic acquisition, choose the session dimension for your new group and inspect its AI Assistants row.
The first matching channel wins. Custom group definitions can reclassify available historical report data; the primary channel group has different forward-looking behavior. Keep the primary group unchanged for this exercise. Google’s custom channel group guide describes ordering, permissions, and limits.
The source-only rule is deliberately easy to audit. If you need only certain mediums, add an explicit medium condition after inspecting real data. Do not require referral alone, because that would exclude sources recorded with ai-assistant. If paid links share the same sources, define how your paid channels should take precedence and document that choice.

Build an AI Traffic Exploration by Landing Page
Use this suggested table to answer two practical questions: which assistant sources are recorded, and which entry pages receive those sessions?
- Open Explore → Free form. Name the Exploration AI sources and landing pages, select dates, and use the Table visualization.
- Import dimensions: Session source, Session medium, Session source / medium, Session default channel group, and Landing page + query string.
- Import metrics: Sessions, Engaged sessions, Engagement rate, Key events, and Session key event rate where available. Add revenue only when your implementation collects it meaningfully.
- Put Session source / medium and Landing page + query string in Rows; put your chosen metrics in Values.
- Add a filter on Session source → matches regex using the pattern above. Save this as your audited source view.
- Duplicate the tab, remove that source filter, and filter Session default channel group → exactly matches → AI Assistant to compare Google’s grouping.
Use two tabs rather than applying both filters to one table: Exploration filters combine with AND, which could hide sources present in only one definition. Importing a dimension or metric makes it available; you must also place it in Rows, Values, or Filters. If GA4 flags incompatible fields, simplify the table before interpreting empty cells. Google’s Free-form Exploration documentation explains the setup.

Sort by Sessions to find entry pages, then examine meaningful key events. A large automated test, or repeated visits to one page, can dominate the totals without demonstrating customer demand. Keep test activity separate before comparing assistant performance with search or social acquisition.
Choose an Outcome That Fits the Landing Page
Track the completed action, not just the invitation to act. For a software demo page, a successful request is more informative than a button click. For a support article, a helpful next-page visit may be relevant, but it is not a sale. Define the outcome before comparing sources so you do not select whichever metric makes a channel look strongest.
GA4 calls an important measured action a key event. Confirm that the intended event fires when the action succeeds, and select that event when the report provides an event selector. An all-events total can combine purchases, sign-ups, and other actions with different meanings.
Keep event occurrences separate from sessions containing an event. Repeated actions can produce several events in one session. Use Session key event rate for the proportion of sessions with the selected outcome; do not calculate that rate by dividing an unverified event total by Sessions. Validate lead suitability or fulfilled purchases in the relevant business system.
If your Exploration only offers a rate for all key events, label it that way. Use the selected-event rate in Traffic acquisition when available for the specific outcome. Do not filter the whole source table to Event name = generate_lead and then treat its remaining Sessions as all arriving visits: that can remove sessions without the action and distort the denominator.

A Hypothetical Walkthrough: From AI Source to a Decision
Imagine a booking-software company checking visits to its demo page during a completed 28-day period. The team fixes the market and device scope, excludes its known tests from this analysis, and uses an accepted demo request as the selected key event. The numbers below are entirely hypothetical, not SEOVisitor results or benchmarks for either assistant.
| Measure | ChatGPT source cohort | Perplexity source cohort |
|---|---|---|
| Sessions | 100 | 40 |
| Engaged sessions | 70 | 32 |
| Engagement rate | 70% | 80% |
| Sessions with an accepted demo request | 8 | 2 |
| Selected session key event rate | 8% | 5% |
| Qualified requests in business records | 5 | 1 |
In this simplified example, each requesting session contains one accepted request, and the business deduplicates and qualifies the records using the same criteria. The ChatGPT cohort’s selected session key event rate is 8 ÷ 100 = 8%. Perplexity has the higher engagement rate, but that alone does not make it the more valuable source.
Investigate the Page Before Choosing a Channel Winner
The analyst checks the exact source strings, landing-page rows, and selected event first. Next, the team reviews rejected requests. Suppose the fictional demo page does not explain which business sizes the product serves, and some enquiries come from companies it cannot support. That is a page-qualification hypothesis, not proof that an assistant sent unsuitable people.
The proposed action is to clarify eligibility near the demo invitation and verify the form’s success event. The next review keeps the same source definition, page, qualification criteria, and follow-up window. A before-and-after change would still be observational: a different audience, promotion, or season could affect it. These small fictional totals do not establish statistical significance.

This workflow turns an AI-traffic report into a specific next step without claiming that the source caused the outcome. For broader cross-channel comparisons, use the same measurement discipline and compare equivalent page purposes rather than pooling every visit.
Why AI Visits Can Appear as Direct
GA4 reports (direct) / (none) when it lacks usable source information. Someone may copy a link into a new tab, open it from an app that does not pass a referrer, or reach your site through a redirect that loses tags. Google’s Direct traffic explanation covers missing attribution and redirect issues.
Link-level noreferrer and referrer policies can also suppress the referring origin. A policy that sends only the origin may preserve the domain while hiding the conversation path. These behaviors are documented in the MDN Referrer-Policy reference.
Do not relabel every Direct session as AI traffic. Without a captured referrer or trustworthy campaign tags, its origin is unknown. A custom channel rule cannot reconstruct a missing source. When you control a genuine shared link, use consistent campaign tags and verify they survive redirects; avoid rewriting unknown traffic just to make the AI report larger.
Inspect campaign parameters on the final landing URL or the collected Page location. Google’s UTM documentation notes that UTM parameters are omitted from Landing page + query string and Page path + query string. Use campaign dimensions to analyze those values instead of assuming a clean landing-page row means the tags were lost.

Check That Your Tracking Setup Works
Use a test property or a clearly isolated destination when possible. Write down the test time, browser or app, initial link, final landing URL, and expected source. Then follow the same route a visitor would use.
- Check collection. Confirm the correct Google tag runs on the destination and records a page view. Use Realtime or DebugView to inspect collection; Google provides tag troubleshooting guidance.
- Check the link path. Open an actual citation link from an assistant’s web answer. Inspect the landing URL for preserved campaign tags and, when available, the page_referrer parameter on the collected page view.
- Check processed acquisition. Revisit Traffic acquisition and the Exploration using the same dates and property timezone. Google notes that processing can take 24–48 hours and recent data can change; see data freshness.
- Check classification. Compare the actual source and medium with the pattern, then compare the custom channel with the default AI Assistant channel. Investigate differences instead of forcing the totals to match.
Use a clean browser session for a controlled check, while following your site’s consent choices. One successful click confirms one collection path; it does not validate every assistant, browser, app, or returning-session attribution path. Realtime activity alone is not a final session-acquisition verdict.
For DebugView, enable debug mode for your test device with Google Tag Assistant or preview mode, then select that device in Admin → Data display → DebugView. Google’s DebugView instructions explain device selection and privacy controls that can prevent events from appearing.

Useful negative checks include confirming that ordinary Google Search, Facebook, and lookalike domain names stay outside the source pattern. Record any genuine new source before editing the list, then retain the previous definition and the change date for comparison.
Keep Automated Attribution Tests Separate
A manual citation click tests one real browser path. An automated campaign with a selected referrer tests a different input: whether your collection and reporting rules handle that labelled activity. It cannot establish how an assistant’s app passes referrers or prove that people discovered the site through an answer.

If you’re looking to buy AI traffic, SEOVisitor’s AI traffic service lets you create a separate website campaign around your selected AI source and destination page.
Use a separate test property or a clearly identifiable test destination and period whenever possible. If source labels alone are shared with earned traffic, they cannot reliably distinguish the two. Document what the test actually checks before spending money, and keep its configured engagement out of reports about audience interest.

Troubleshoot Missing or Inconsistent AI Traffic
Diagnose the first point where the evidence stops: collection, source capture, channel matching, or reporting. The table gives a next check for each symptom. Changing a classification rule is appropriate only when you have identified the actual input; it is not a remedy for missing data.
| Symptom | Next check | Action |
|---|---|---|
| No AI Assistant row | Session source / medium, dates, and filters | Inspect individual assistant sources; do not require referral as the only medium. |
| A source is absent from the custom group | Exact source string and channel order | Check domain versus UTM alias, rule scope, and earlier matching channels. |
| An expected visit is Direct | Final URL, captured referrer, and consent path | Investigate missing attribution; leave the origin unknown if there is no evidence. |
| Explore and Reports disagree | Dates, scope, filters, retention, and data quality | Align the definitions, then document any remaining reporting limitation. |
| Test events appear only in DebugView | Internal and developer traffic filters | Review the filter state with the property administrator before changing it. |
| Many visits, few useful outcomes | Destination, event implementation, and verified results | Separate tests and check the page’s task; do not treat source labels as a quality certificate. |
Google documents why Reports and Explorations can differ, including retention, filtering, and processing. Check the data quality indicator before presenting a small difference as a trend. A missing historical period in Explore is not proof that no sessions occurred.
An active exclusion can permanently discard incoming data. Google’s internal traffic filter guidance explains that risk. For this exercise, review configuration with an authorized administrator; do not disable privacy controls or change production collection merely to make a test visible.
Maintain a Useful AI Traffic Report
Keep a short change log containing the source pattern, channel order, selected outcome, reporting period, and known test activity. Save the previous definition before adding a host or alias so that a later increase can be distinguished from a reporting change.
Review the same landing pages over comparable completed periods, and include absolute session and outcome counts alongside rates. If activity is sparse, keep collecting evidence rather than declaring a winning assistant. The report should answer what was recorded, which pages received it, and what to investigate next—not claim to measure every AI mention or prove incremental sales.

Frequently Asked Questions
Quick answers to common questions about track AI traffic in GA4
Yes. Start with GA4's AI Assistant channel and inspect Session source / medium. Create a custom group only when you need a maintained source definition or a separate reporting view.
No. A source label describes recorded attribution, not verified visitor identity or a recommendation. Separate genuine citation clicks, controlled tests, and automated campaign visits when evaluating outcomes.
Not from the source domain alone. A referrer may reveal only the assistant's origin, and GA4 does not provide a conversation or prompt report. Use a separately documented observation without claiming it covers all visits.
Check the exact received value, rule scope, dates, and channel order. The domain-only pattern does not match a full referrer URL or a UTM alias such as chatgpt. Verify the origin before extending the rule.
No. Keep automated attribution tests in a separate property or identifiable destination and period. They can check a reporting input, but they do not demonstrate independently earned assistant referrals or customer demand.
No. Google's default definitions place non-ad visits from AI Overviews and AI Mode in Organic Search. Gemini is a separate assistant source; do not group all Google traffic under AI Assistant.
Google omits UTM parameters from that dimension and Page path + query string. Check Page location and the relevant campaign dimensions instead of concluding that a clean landing-page row means the tags were lost.
Comments
Leave a Comment