Definition
Every visit an analytics tool records carries traffic values: where it came from (source), what kind of channel it was (medium) and, when tagged, which campaign. Those values are detailed and inconsistent, with hundreds of sources and whatever medium values people typed. A channel grouping is an ordered set of rules that maps each combination to one of a small number of channels, so that reports can compare paid search with email with organic social at a glance.
The rules run in order and the first match wins. If nothing matches, the visit goes to a catch-all, which in GA4Google's event-based analytics platform. is called Unassigned. Because a property can hold a default grouping and custom ones side by side, the same visit can carry different channel labels depending on which grouping a report uses.
Default and custom groupings
The default grouping is supplied by the tool. Google documents the rules of GA4's default channel group and updates them from time to time; they match on the medium value, on whether the source is on Google's lists of search or social sites, on campaign names for some of Google's own campaign types and on the source platform. The default group cannot be edited, which keeps it comparable across properties.
A custom channel grouping is the business's own rule set, usually started as a copy of the default and then changed: separating brand from non-brand search, splitting partners from affiliates or giving a marketplace its own channel. Custom groupings can be used in standard reports, explorations and attribution reports, and the GA4 attribution settings guide covers how they sit beside the reporting attribution model and the limits on how many a property may hold. A small number of well-named groupings that everyone uses is more useful than one per stakeholder.
In practice: how source and medium values decide the channel
The medium value does most of the work. A visit tagged with a medium the rules recognise as email lands in Email; one tagged with a recognised paid medium and a known social source lands in Paid Social. The source then separates search engines from social networks for the paid and organic channels. Campaign values matter only for a few special cases.
Two consequences follow. First, the tagging convention has to use the vocabulary the grouping expects. The guide to UTM and naming conventions explains why the parameters are read literally, case included, and the UTM and naming convention templates map each allowed medium value to the channel it should land in, so new values are added deliberately. Second, traffic the business does not tag by hand needs its own route into the right channel: ad platform auto-tagging for Google Ads clicks, for instance, rather than manual tags that may contradict it.
The same idea extends beyond analytics. CRM systems that record where each contact came from benefit from deriving the channel from stored raw parameters with a documented rule, and the CRM fundamentals guide for marketers recommends that over asking salespeople to pick a source from a list.
Unassigned traffic and how to fix it
Unassigned is where visits go when their values match no rule. A small, stable share is normal. A large or growing share almost always means someone is tagging links with a medium outside the expected vocabulary, a platform's name in place of its type, or a team's own label for a campaign. The attribution model then credits those visits faithfully to a bucket that describes nothing.
The fix is upstream. Find the source and medium combinations inside Unassigned, correct the convention or the links that produced them, and record the date of the correction so that later comparisons can be annotated. Where a value is used deliberately and the default rules will never recognise it, a custom grouping can give it a home. The analytics implementation audit scorecard scores the channel grouping directly, with a large unassigned share as the failing state, and the Google Analytics 4 section places channel groups among the settings to understand before reading acquisition reports.
A print studio finds its missing email traffic
Quireleaf Print Studio sent a fortnightly newsletter to about 4,800 subscribers and saw Unassigned grow from 3% of sessions to 17% over six months, while the Email channel showed almost nothing. The newsletter links had been tagged with the medium "newsletter", which the default rules did not recognise as email. The studio changed the convention so that every newsletter link used "email" as the medium and "newsletter" as the campaign, updated its email template, and noted the date of the change in its measurement log. In the next month Unassigned fell to 2%, and Email showed 1,150 sessions and 38 orders.
Related terms
UTMURL tags identifying traffic source. parameters supply most of the source, medium and campaign values the grouping reads. GA4Google's event-based analytics platform. provides a default channel group and lets properties add custom ones. AttributionAssigning conversion credit to touchpoints. credits conversions to channels after the grouping has labelled each touchpoint, so a misfiled channel receives credit it did not earn. Auto-TaggingA Google Ads setting that adds a click identifier (GCLID) to every ad click's landing URL. passes Google Ads click detail automatically, which keeps paid search traffic in the right channel without manual tags.
Common confusions
- Channels are a property of the traffic. They are labels a rule set assigns, and different rule sets label the same visit differently.
- Unassigned traffic is untracked. It is tracked; its values simply match no rule.
- The default grouping can be edited. It cannot; a custom grouping is copied from it and changed.
- A custom grouping fixes bad tags. It can relabel values the business uses on purpose; mistaken tags are fixed in the convention and the links.
- Any medium value will do as long as it is consistent. Consistency is necessary, and the value must also be one the grouping's rules recognise.
