<!-- Canonical: https://gavek.dk/learn/ai-referrals-in-ga4/; Language: en -->

[Home](https://gavek.dk/)/[AEO knowledge hub](https://gavek.dk/aeo/)/AI referrals in GA4: verify the AI Assistant channel and its limits

AEO · evidence and practical implementation

# AI referrals in GA4: verify the AI Assistant channel and its limits

Google’s current channel documentation includes AI Assistant. Check the actual property and source dimensions before creating custom rules or treating missing referrals as no AI influence.

## Start with the current default classification

Google documents AI Assistant for sources such as ChatGPT, Gemini, Deepseek, Copilot and Grok. Its documentation places Google AI Overviews and AI Mode within Organic Search rather than that assistant channel. Check the current definitions when implementing; older tutorials that say all AI traffic must be manually grouped may no longer match your property. Availability and historical classification should be verified in the property, not assumed from a guide.

## A practical inspection sequence

With authorised access, open the traffic-acquisition report and select Session default channel group for session-level review. Inspect Session source / medium and landing pages alongside the assistant channel. Compare a consistent date range and note filters, consent effects and collection changes. Use event-scoped attribution reports for key-event questions instead of mixing them with first-user acquisition numbers.

## Add a custom group only for a defined need

Default channel groups cannot be edited. A custom group can support an internal analysis, but first document the sources it should include, exclusions and rule precedence. Test actual observed source values; do not assume a static domain regex captures every app, link redirect or future platform. Preserve the default report for comparison and avoid relabelling Organic Search as purely non-AI traffic.

## Validate an outcome without inventing attribution

Where appropriate, test collection in an authorised test environment and inspect the consent state. A source may be absent because of browser behaviour, privacy controls, copied links or later branded search. Track successful enquiry receipt separately from a contact click. Keep an optional self-report alongside observed attribution, and show “not measured” if the integration or permission is missing. This guide is a procedure, not a claim that Gavek’s GA4 property has been inspected.

## Continue with the related decision

- [AEO learning paths](https://gavek.dk/aeo/)

- [A monthly AI visibility report: decisions, evidence and uncertainty](https://gavek.dk/learn/monthly-ai-visibility-report/)

- [Discuss the scope of AEO and AI-search work](https://gavek.dk/services/ai-search/)

### Sources, method and review information

Editorial publisher: Gavek. Reviewed 8 November 2026. Practical methods and clearly labelled examples are original editorial guidance, not customer results or a disclosed platform algorithm. Check sources when implementing.

- [Google Analytics · channel definitions](https://support.google.com/analytics/answer/9756891)

Your next move starts here

## Make search a more useful part of your growth.

Start with your website. Leave with a clearer picture of what to improve, what to measure and where to focus next.

[Discuss your SEO project ↗](https://gavek.dk/contact/)[Explore our services ↗](https://gavek.dk/services/)
