On this page
Custom Channel Grouping (GA4)
Custom Channel Grouping (GA4)
A Custom Channel Group (CCG) is a user-defined set of rules that categorises traffic sources into named channels in Google Analytics 4, layered on top of the uneditable Default Channel Group. For ecommerce teams, CCGs are the primary mechanism for separating branded from non-branded paid search, prospecting from retargeting, affiliate from organic referral, and for capturing emerging traffic types such as AI-referred visits that the default taxonomy cannot cleanly classify.
How it works
GA4 evaluates channel grouping at query time, not collection time — meaning rules are applied when a report is run, not when the hit arrives. Each custom group is an ordered list of channels. When a session arrives, GA4 tests it against each channel's rule set from top to bottom and stops at the first match (first-match-wins). If no channel matches, the session is classified as Unassigned (Google Support article 13051316, 2026).
Rule conditions — each channel definition can use the following dimension fields, combined with AND/OR logic:
| Field | Notes |
|---|---|
| Source | Accepts partial match, exact match, regex |
| Medium | Accepts partial match, exact match, regex |
| Campaign name | Partial match, exact match, regex |
| Campaign ID | Exact match |
| Default channel group | Compare against GA4's built-in channel |
| Manual ad content | utm_content value |
| Source platform | The ad network (Meta Ads, Google Ads, etc.) |
Rules are not case-sensitive (Google Support 13051316, 2026). Order directly determines classification: more specific rules must sit above broader catch-alls.
Default channel grouping vs Custom channel grouping
GA4 ships with an uneditable Default Channel Group containing 19 named channels (as-of September 2026, per Analytics Mania). Custom Channel Groups are additive — they do not replace the default. A property can have one CCG set as its primary channel group (the editable default visible in standard reports); all others are available as secondary dimensions in explorations and custom reports.
Default channel list (as-of September 2026, per Analytics Mania and Google Support 9756891):
| Channel | Rule basis |
|---|---|
| AI Assistant | medium exactly "ai-assistant"; referrer matches ChatGPT, Gemini, DeepSeek, Copilot, Grok (added May 13, 2026) |
| Affiliates | medium matches "affiliate" or "affiliates" |
| Audio | medium matches audio/podcast patterns |
| Cross-network | Performance Max, Demand Gen, Smart Shopping |
| Direct | source "(direct)" AND medium in "(not set)"/"(none)" |
| Display | Display Network ads |
| source or medium matches email/e-mail/e_mail/e mail | |
| Mobile Push Notifications | mobile push message links |
| Organic Search | non-ad search results incl. Google AI Overviews and AI Mode |
| Organic Shopping | non-ad shopping site links |
| Organic Social | non-ad social links |
| Organic Video | non-ad video links (YouTube, TikTok, Vimeo) |
| Paid Other | paid ads not classifiable as Search/Social/Shopping/Video |
| Paid Search | paid search ads |
| Paid Shopping | paid shopping/retailer ads |
| Paid Social | paid social ads |
| Paid Video | paid video ads |
| Referral | non-ad links from other sites (medium in "referral"/"app"/"link") |
| SMS | text message links |
Special values:
- Unassigned — no channel rule matched
- (other) — row aggregated due to cardinality limits
Three scope dimensions are auto-generated by GA4 for each channel group (Google Support 9756891, 2026):
| Dimension | Attribution model | Scope |
|---|---|---|
| Default channel group | Property's model (DDA default) | Event |
| Session default channel group | Paid & Organic Last Click | Session |
| First user default channel group | Paid & Organic Last Click | User |
Property limits
Channels-per-group limit: Analytics Mania (Aug 2026) states standard properties may have "up to 25 channels" per custom group. Google's own Support article 13051316 (2026) states "50" for standard properties. Google primary source is the authoritative reference; the Analytics Mania figure may reflect an outdated limit or a misread of the 360-only context.
Per Google Support 13051316 (2026, as-of October 2026):
| Limit | Standard | GA4 360 |
|---|---|---|
| Custom channel groups per property | 2 | 5 |
| Channels per group | 50 | 50 |
Editors or Administrators at property level can create and edit channel groups.
Retroactivity
Custom channel groups apply retroactively — changes appear immediately across historical data because GA4 evaluates channel grouping at query time, not at data collection time. The underlying event data is not altered (Google Support 13051316, 2026; Analytics Mania, Aug 2026; FourFront, Jul 2026; Blend Analytics, May 2026).
Exception — Primary channel group: when a CCG is set as the property's primary channel group (the editable default), that change is forward-only and does not reclassify historical data (Google Support 13051316, 2026).
An earlier body of practitioner documentation (pre-2024) described CCG as NOT retroactive. That framing reflected the feature's early state or was incorrect. The current GA4 implementation (confirmed by Google's own support article and multiple 2026 practitioner sources) is definitively retroactive. Any pre-2024 guide claiming CCG is forward-only should be disregarded.
Static copy caveat: when a user copies the Default Channel Group as a template, that copy is static — it does not auto-update when Google later adds new channels (e.g., AI Assistant in May 2026). Manual updates are required (Analytics Mania, Aug 2026).
Where CCGs are and are not available
Available (Google Support 13051316, 2026):
- Primary dimension in User Acquisition and Traffic Acquisition reports
- Secondary dimension in standard reports (Events, etc.)
- Dimensions in custom reports and Explorations
- Audience definition conditions
Not available:
- Key events paths report
- BigQuery Export Schema — CCGs do not appear in the BQ export; this is a hard limitation for teams relying on BigQuery for downstream attribution analysis
- Cost/Click/Impression reporting does not support the "Manual ad content" field
Audience behaviour at edit time: if a CCG used in an audience definition is edited, user eligibility in that audience changes going forward only — existing members are not reclassified retroactively (Google Support 13051316, 2026).
Unassigned traffic — causes and how CCG helps
"Unassigned" is the value GA4 assigns when no channel rule matches a session. It is a data quality signal, not a legitimate channel. Common causes include (Analytics Mania, Sep 2026):
- Non-standard UTM medium values (e.g.,
utm_medium=pdf,utm_medium=mail) — the #1 cause; GA4 recognises only specific exact strings for email ("email", "e-mail", "e_mail", "e mail") - Incomplete UTM parameters (missing
utm_sourceorutm_medium) - Redirects stripping UTM parameters (link shorteners, forced HTTPS)
- Google Ads not linked or auto-tagging disabled
- GA4 config tag firing after event tags (tag ordering error in GTM or sGTM)
- Events from third-party streaming platforms (Amplitude, Segment) missing
session_id - Measurement Protocol events missing
session_id - AI tool traffic (ChatGPT, Perplexity) with partial UTMs — source present but medium missing
- Recurring subscription payments sent via Measurement Protocol (no active session — expected behaviour for subscription models)
- Bot traffic
- Data not yet processed (GA4 takes 24–48 hours; Unassigned spikes in fresh data often resolve)
- Audience triggers — known GA4 limitation, no fix available
Diagnostic method: in Traffic Acquisition report, add "Session Source / Medium" as secondary dimension, filter by "Unassigned" channel, and identify the specific source/medium pairs falling through (Analytics Mania, Sep 2026).
Creating a CCG rule to catch known non-standard values (e.g., utm_medium=e_mail → Email) can reduce Unassigned without fixing the underlying UTM (though fixing the UTM at source is preferable).
Ecommerce use cases
The ecommerce-specific value of CCGs is separating traffic sources that carry fundamentally different commercial intent, economics, and ownership — distinctions the default grouping deliberately obscures (Blend Analytics, May 2026).
1. Brand vs non-brand paid search — the most valuable split. "Branded paid search (ads triggered by your own company or product name) and non-branded paid search (ads triggered by generic, problem-based terms) do two different jobs, and grouping them into one 'Paid Search' line hides that" (FourFront, Jul 2026; Blend Analytics, May 2026). Branded search converts at higher rates and lower CPCs; blending produces averages that describe neither and make non-brand look better than it is. Implementation requires a campaign naming convention: create a "Branded Paid Search" channel with a campaign name regex matching brand terms, placed above a "Non-Branded Paid Search" channel for remaining cpc traffic.
2. Prospecting vs retargeting (paid social) — "A retargeting campaign converting at 8% is not evidence that paid social works. It is evidence that people who already know you will come back" (Blend Analytics, May 2026). Separate by campaign naming convention (e.g., campaigns containing "rtg" or "retargeting" → Retargeting bucket).
3. Shopping and Performance Max — different enough from standard search that averaging hides performance differences (Blend Analytics, May 2026).
4. Affiliate and partner traffic — different economics and different ownership; warrants its own bucket rather than sitting in Referral (Blend Analytics, May 2026).
Official AI Assistants example (Google Support 13051316, 2026): Google provides a CCG regex for classifying AI-referred traffic as a named channel:
^.*ai|.*\.openai.*|.*chatgpt.*|.*gemini.*|.*gpt.*|.*copilot.*|.*perplexity.*|.*google.*bard.*|.*bard.*google.*|.*bard.*|.*.*gemini.*google.*$
This channel must be placed above "Referrals" in rule order due to first-match evaluation.
2026 updates
May 13, 2026 — AI Assistant channel in Default Channel Group (GA4 changelog, 2026):
- New built-in channel covering ChatGPT, Gemini, DeepSeek, Copilot, Grok
- GA4 auto-assigns
medium = ai-assistantandcampaign = (ai-assistant)when referrer matches - Forward-only — does not reclassify historical AI traffic (which remains in Referral). Creates a series break in any analysis crossing May 13, 2026
- Google AI Mode (post-Google I/O 2026) generates traffic with
referrer = google.com→ classified as Organic Search, not AI Assistant. "The largest source of AI-generated search traffic in the world is invisible as a distinct channel in Google's own analytics platform" (Seresa, Jun 2026) - 35–70% of AI referral sessions arrive without a referrer header → land in Direct regardless of AI Assistant channel (Statcounter data cited by Seresa, Jun 2026, as-of 2026)
AI Assistant channel coverage: Google's primary documentation lists ChatGPT, Gemini, DeepSeek, Copilot, Grok as covered AI assistants. A separate Google blog post named ChatGPT, Gemini, Claude (Anthropic) at launch. Practitioner sources (Seresa) list Claude web interface as covered. The definitive live list is maintained by Google and not fully published; the exact list may differ between these sources and may expand over time.
June 11, 2026 — Source Group dimension (GA4 changelog, 2026):
- New dimension (not a CCG) that auto-consolidates fragmented source variants:
facebook,fb,m.facebook.com,l.facebook.com,Meta-facebook→ all mapped to "Facebook" - Platforms at launch (~10): Facebook, Instagram, TikTok, Pinterest, Amazon, YouTube, Google Search, Google Maps, ChatGPT, Perplexity
- Retroactive — populated across full property history; year-over-year comparisons on the new dimension shift without real market movement (Zenda, Jul 2026)
- Source Group is in the Advertising section; default channel grouping is unaffected — no traffic moves between channels
- Source Group normalises the source dimension only; broken UTMs still require fixing at source
- Paid vs organic must still be disambiguated via Source Platform dimension alongside Source Group
January 2026 beta — Per-conversion attribution settings: GA4 now allows independent attribution model settings per conversion (previously one model applied to all properties); directly relevant to CCG accuracy in multi-conversion-type ecommerce setups (Report Radar, Oct 2026).
Key terms
| Term | Meaning |
|---|---|
| Default Channel Group | GA4's uneditable built-in 19-channel taxonomy applied to all properties |
| Custom Channel Group (CCG) | User-defined rule set layered on top of the default; up to 2 per standard property |
| Primary Channel Group | A CCG set as the property's editable default (future data only) |
| First-match-wins | GA4 stops evaluating rules at the first channel whose conditions are met; rule order is critical |
| Unassigned | Catch-all value when no channel rule matches; a data quality signal |
| Source Group | New June 2026 GA4 dimension consolidating fragmented source variants; distinct from CCG |
| AI Assistant | New May 2026 default channel for traffic from recognised AI tools (medium = "ai-assistant") |
| Scope | Dimension level at which channel is evaluated: event (DDA model), session (last-click), user (first-click) |
(Next frontier concepts: AI Assistant Traffic, Source Group (GA4), Custom Channel Grouping Audit, Conversion Attribution Analysis (GA4), BigQuery Export (GA4), User ID (GA4))