An AI mention is not a website session. GA4 can help measure visits with identifiable source information, but it cannot count every buyer influenced by an AI answer.

Step 1: inspect the source data

Open the Traffic acquisition report and inspect Session source / medium. Identify source values actually present in your property. Use a consistent period and check that GA4 collection and consent configuration are functioning as intended.

Do not assume every AI platform sends a referrer or uses the same domain forever.

Step 2: create a custom channel group

With the required editor permissions, open Admin → Data display → Channel groups. Copy an existing group, add an “AI assistants” channel and use the Source field with “matches regex.” The channel rule field is Source; the corresponding reporting dimension can be session-scoped.

Conservative starter regex

^(chatgpt\.com|chat\.openai\.com|perplexity\.ai|www\.perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai)$

This matches exact domain-shaped source values, not full URLs or source / medium strings. Add aliases only after inspecting your data. It deliberately avoids broad matches such as .*ai.*, which can capture unrelated sources.

Move the channel above other rules that would otherwise match the same sessions, such as Referral, and save the copied group. Keep your original group available for comparison.

Step 3: validate the output

Use the custom group in Traffic acquisition. Compare each matched source with the original report. A zero result may mean no matching recorded traffic, a wrong dimension or an unobserved source alias—not necessarily a tagging failure.

Test the regex against known positive and negative examples before applying it elsewhere. Do not add these domains to unwanted referrals to create a reporting channel.

Step 4: connect sessions to qualified demand

Review landing pages, engaged sessions and verified lead-submission events. Configure cross-domain measurement where your real booking journey requires it. Keep event totals separate from CRM-qualified leads and opportunities.

Frequently Asked Questions

Does this identify Google AI Overview clicks separately?

No. Do not relabel all Google organic traffic as AI traffic.

Can it recover missing referrers?

No. A reporting rule classifies recorded data; it cannot recreate an unrecorded AI touchpoint.

Next step

Want a clear view of how AI search visibility connects to the inquiries you actually receive?

Request a visibility and measurement assessment →

Sources and verification notes

The steps, examples and templates in this article are practical recommendations, not platform rules, survey data or measured client results. Hypothetical figures and examples are labelled as such. The sources below support the platform and technical facts only.

  1. Google Analytics Help: Custom channel groups
  2. Google Analytics Help: Regular expressions
  3. Google Analytics Help: Traffic acquisition report

Want to see how your brand ranks in ChatGPT right now?

Run a free AI Visibility Audit to see where your business appears across ChatGPT, Gemini and Perplexity—and where competitors are being recommended instead.

Get Your Free AI Visibility Audit