How to Track AI Assistant Traffic and Conversions in GA4

GA4 now has an AI Assistant default channel for recognized referrals from tools such as ChatGPT, Claude, Gemini, Copilot, DeepSeek, and Grok. Open Reports > Acquisition > Traffic acquisition, find the AI Assistant row under Session default channel group, then inspect Session source / medium, landing pages, and Key events to see what those visitors did. Google AI Overviews and AI Mode are excluded from this channel and remain part of Organic Search.

The channel is a better starting point than a homemade list of assistant domains, but it is not a complete measure of every AI-influenced visit. Referrer loss, direct navigation after an AI recommendation, and Google’s own AI Search surfaces can all sit outside the AI Assistant row.

Table of Contents

13 sections Show

What GA4 puts in the AI Assistant channel

Google introduced this default channel in May 2026. When GA4 recognizes an AI assistant referrer, it sets the medium to ai-assistant, the default channel to AI Assistant, and the campaign to (ai-assistant). The exact source should tell you which assistant sent a recognized visit.

The relevant dimensions have different scopes. Session default channel group describes the source of the current session and is the right starting dimension in Traffic acquisition. First user default channel group describes how a user first arrived, which is useful for acquisition history but not for counting every later assistant visit. An event-scoped channel in an attribution report answers yet another question about credit for a key event. Do not mix these in one spreadsheet as if they were interchangeable.

The quickest way to answer each question is:

• How many recognized assistant visits? In Traffic acquisition, select Session default channel group = AI Assistant and read Sessions.
• Which assistants sent them? Within that selection, inspect Session source / medium.
• Which page did they enter on? Add Landing page + query string or use a landing-page report with the same session-channel filter.
• Did they take a valuable action? Read Key events for the selected session channel and specific event.

Find AI Assistant sessions in Traffic acquisition

1. Sign in to the correct GA4 property and choose a complete date range.
2. Open Reports, then Acquisition > Traffic acquisition. Depending on the report collection, it may appear under Business objectives > Generate leads, as in the screenshot. If the report is absent from the navigation, an Editor can restore it to the collection.
3. Keep Session default channel group as the primary dimension and find AI Assistant. Use the table search or an include filter rather than assuming the row will be high enough to see without scrolling.
4. Record Sessions, Engaged sessions, Engagement rate, and Key events for the same date range. If the channel has very little traffic, examine raw counts before comparing percentages.
5. Repeat for the preceding complete period using the same reporting settings.

The AI Assistant row may be missing when no recognized referrer generated reportable traffic during the period. That is not evidence that no AI assistant mentioned your brand. It is evidence that this GA4 view has no classified sessions to display.

Identify the assistant and the landing page

Within the AI Assistant selection, add Session source / medium as a secondary dimension using the plus control next to the primary dimension, or switch the primary dimension to it. Google documents the Traffic acquisition report’s session-scoped source and medium dimensions. This is more informative than reporting a single combined AI Assistant total: a guide that attracts ChatGPT visits may not be the same guide that attracts Copilot visits.

The filtered BrandJet report showed separate chatgpt.com / ai-assistant, copilot.com / ai-assistant, gemini.google.com / ai-assistant, and perplexity.ai / ai-assistant rows when checked. The screenshot below keeps those real labels but hides all counts and rates. Your property may have a different set of sources.

Next, add Landing page + query string if your report offers it as a secondary dimension. If your current layout does not, use a landing-page report or Exploration and apply an AI Assistant session-channel filter. The point is to join the channel and entry-page question without pretending that the page was necessarily quoted in the answer. The visitor may have clicked a homepage or another URL.

For each leading landing page, record the assistant source, sessions, engaged sessions, key events, and a clear content action. A page with 20 visits and two qualified form submissions may deserve attention sooner than a page with 200 visits and no meaningful next step. At low counts, that is a triage observation, not a statistically reliable conversion-rate comparison.

Connect visits to conversions without inflating the claim

GA4 calls important business actions key events. Before reporting assistant conversions, verify that the event you care about is implemented and marked as a key event. A newsletter signup, demo request, or purchase may be a key event, but page views and automatic engagement events should not be casually presented as pipeline outcomes.

In Traffic acquisition, use the Key events metric and, where available, its event selector to isolate the action you mean. Document the event definition. For example, generate_lead should fire when a valid lead action completes, not when someone merely opens the form. Check duplicate firing and test traffic before using the number in a client report.

An AI Assistant session with a key event means GA4 assigned that session to a recognized assistant and observed the event. It does not prove that a specific AI answer caused the conversion or that the customer had no earlier touchpoints. Attribution reports may credit multiple channels differently, so do not compare event-scoped credited conversions directly with session-scoped key events without explaining the model.

Audit visits that do not appear in the channel

Do not create an “estimated AI traffic” number by reallocating Direct sessions. Direct means GA4 lacked a clear source; it does not mean the visit came from ChatGPT. An assistant may omit referral information, a browser may strip it, and a person may search or type your URL after reading an answer. None of those paths can be recovered reliably by guesswork.

If a known assistant domain appears under Referral or another channel, check the date, source / medium, manual UTM tags, redirect chain, and GA4 implementation. Google’s default channel group cannot be edited. You can create a custom channel group for internal analysis, but label it separately and keep the native AI Assistant result intact for comparisons over time.

Do not add UTMs to URLs you hope an assistant will cite and then assume every later visit will carry them. UTMs are useful for links you control, such as your own campaigns, not for reconstructing unknown third-party answer behavior.

Build a weekly assistant-traffic worksheet

Keep these fields in one review row per period:

• Reporting period: Start and end dates, property, and time zone.
• AI Assistant sessions: Current and previous complete-period counts.
• Source / medium: The assistant sources GA4 actually classified.
• Landing pages: Top entry URLs and their session counts.
• Key event: Exact event name, count, and whether its instrumentation was tested.
• Quality signal: Engaged sessions, form quality, or CRM qualification, as appropriate.
• Caveat: Referrer loss, low volume, or instrumentation change.
• Action: The content or conversion path to improve next.

Hypothetical example: GA4 reports 90 AI Assistant sessions this week versus 60 last week. A product comparison page receives 35 of the 90 sessions and records three demo-request key events. The safe summary is: “Recognized assistant referrals increased; the comparison page led those entries and GA4 observed three demo requests in the filtered sessions.” Do not say “three sales came from ChatGPT” unless your CRM confirms sales and the source actually was ChatGPT.

Keep Google AI Search and assistant referrals apart

Google AI Overviews and AI Mode are Search experiences. Google says their clicks remain in GA4’s Organic Search channel, not AI Assistant. Search Console’s dedicated Generative AI report measures impressions of links in those Google experiences. Its impression count cannot be divided into GA4 AI Assistant sessions to calculate a conversion rate.

Likewise, Bing Webmaster Tools’ AI citations are not GA4 visits. A single dashboard can show all three signals, but it needs separate labels and denominators. BrandJet’s AI search monitoring can add context about how your brand appears in generated answers, while GA4 remains the place to analyze recognized referral sessions and on-site actions.

FAQ

Where is AI Assistant traffic in GA4?

Open Reports > Acquisition > Traffic acquisition and look for AI Assistant under Session default channel group. Use a complete date range and a table filter if the row is hard to find.

Does GA4’s AI Assistant channel include Google AI Overviews?

No. Google’s default-channel documentation explicitly excludes AI Overviews and AI Mode. Their traffic remains within Organic Search.

Why are ChatGPT visits showing as Direct?

GA4 may not receive usable referral information for every visit. Direct is not proof of ChatGPT origin, so investigate the referrer and tracking path without reclassifying all Direct traffic as AI.

Can I measure AI Assistant conversions?

You can measure GA4 key events observed in sessions classified as AI Assistant. Verify the event setup and state the attribution scope. That is not the same as proving a particular AI answer caused a sale.

Should I build a custom channel group?

Start with Google’s native AI Assistant channel. Use a separate custom group only if you have a documented need to analyze sources that the default grouping misses, and keep the two definitions distinct in reporting.