Why GA4 files traffic under Unassigned, and when a custom channel group helps

The default rules are fixed and mechanical

GA4's default channel group applies a published list of rules to each session's source and medium. Google states that matching ignores letter case, and that the definitions cannot be edited and may change over time. So the first question about an odd channel is not what GA4 meant but which rule the source and medium pair satisfied.

The rules differ in what they need. Direct needs the source (direct) with medium (not set) or (none). Email accepts either source or medium equal to an email spelling. Referral looks only at medium values referral, app and link. Paid Search needs both a source from Google's search site list and a medium that matches its pattern, which covers values containing cp, ppc, retargeting or starting with paid.

• Check which of source and medium the target channel needs before editing links.
• A paid-looking medium with an unlisted source does not become Paid Search.

What lands in Unassigned

Google states that Unassigned is the fallback when no rule matches. Its page does not give a dedicated rule for a non-standard medium or a missing source, so what follows is reasoning from the table, not a Google statement: a medium such as newsletter with a source GA4 does not recognise matches none of the listed rules, so it would fall through.

A separate value, (other), appears when cardinality limits force rows to be aggregated. It is not the same thing and should not be treated as a naming fault.

• List the source and medium pairs behind your Unassigned rows before changing anything.
• If two or three pairs account for most of it, fix the links; if dozens do, consider a custom group.

Custom channel groups: what they regroup

Google lets you create a custom channel group from Admin, under Data display. You copy the default, add or edit channels with conditions, and order them, because traffic goes into the first channel it matches. A standard property can hold two custom groups beside the default, with up to 50 channels each.

They can be applied to reports retroactively, which makes them a tool for regrouping history without changing recorded source or medium. Limits to know: making one the primary group affects only future data, they cannot be used in the Key events paths report, they are not in the BigQuery export schema, and deleting one is irreversible.

• Use a custom group for a rule gap, not to hide inconsistent links.
• Record the order of channels in your handover; it changes results.

What does not fit, and how the paid outcome is accepted

A custom group does not repair the recorded values, and nothing here changes auto-tagging or ad performance. If sessions are missing rather than misfiled, look at redirects, consent and cross-domain hand-offs instead.

The fixed outcome Fix campaign tagging and channels, quoted at £245 as an untested proposal with payment after sign-off, covers up to 20 link patterns and, where a rule gap remains, one custom channel group. Acceptance: each tested link pattern, opened with a unique test campaign value, appears once Google has processed the data in Traffic acquisition under that value with the agreed session source / medium, in the agreed channel and not under Unassigned. Realtime is only a quick sighting, because Google says its source card counts users by how they were first acquired and only for established users. Send the odd source and medium pairs from your report; no logins.