Why 10–20% of Your GA4 Traffic Is 'Unassigned'

You open Reports → Acquisition → Traffic acquisition in GA4 and a fat slice labeled Unassigned sits near the top — sometimes bigger than Email or Paid Social. The spend was real and the clicks were real, but GA4 cannot tell you where that traffic came from.

What 'Unassigned' actually means in GA4#

GA4 sorts every session into a channel using the Default Channel Group — a fixed list of rules like Email, Paid Social, Organic Search, and Referral. Each rule is a pattern. The Email rule, for example, only matches when the source or medium reads email, e-mail, e_mail, or e mail.

When a session arrives, GA4 reads its utm_source and utm_medium exactly as you wrote them and checks them against every rule in order. If one matches, the session gets that channel. If none match, GA4 has nowhere to put it — so it lands in Unassigned. The traffic is not missing; it just failed the rules.

Unassigned vs (not set) — they are not the same#

These two get mixed up constantly, and the fix is different for each. The quick test: Unassigned has data that did not match; (not set) has no data at all.

Why your traffic falls through the rules#

Almost every Unassigned session traces back to a utm_medium value GA4 was never taught to recognize. The Default Channel Group only knows a short, specific list per channel. Anything outside that list has no home.

• Custom mediums with no rule — newsletter, qr, partner, podcast, influencer. Useful labels, but no Default Channel Group rule matches them, so they go Unassigned.
• Mismatched source/medium pairs — utm_medium=paid_social with a source GA4 does not see as a social platform can miss the Paid Social rule and fall through.
• Case and spacing drift — Email, EMAIL, and email are three different mediums in your reports, which splits one channel into several rows. See UTM case sensitivity in GA4.
• Typos in templates — cpc-fb, e-mail-blast, a trailing space. One wrong character is enough to miss a rule.

The reason this keeps happening is governance, not skill. Most teams use UTMs but never write the rules down: 67% use UTMs and only 58% have a documented strategy (SEMrush, 2024). Once more than two people build links, spelling and casing drift, and a slice of every campaign starts missing the channel rules.

Common values that GA4 sends to Unassigned#

Here is what the same intent looks like when it is written four different ways. Only the canonical token on the right matches a Default Channel Group rule.

How to recover Unassigned traffic#

You cannot rewrite the source/medium already stored on past sessions, but you can find the bad values, correct the links that produce them, and stop the leak going forward. Work in this order.

1. 1

   Find the real values behind Unassigned

   Open Traffic acquisition, then add Session source / medium as a secondary dimension and filter to the Unassigned row. You now see the exact strings GA4 could not classify.

2. 2

   Group the duplicates

   Cluster the case variants, typos, and synonyms — Email, EMAIL, newsletter all mean one channel. This is the audit step, and it is where most of the recovery happens.

3. 3

   Map each group to a canonical token

   Pick one value GA4 recognizes per group: email, cpc, paid_social, organic, referral. Lowercase, no spaces, no punctuation drift.

4. 4

   Fix the links at the source

   Update the email tool, ad platform, and link templates that generate the bad UTMs. Renaming inside GA4 alone does not fix the links still being created.

5. 5

   Add a custom channel group for legitimate customs

   For mediums you genuinely want — qr, partner, podcast — build a custom channel group so they get a named bucket instead of Unassigned.

6. 6

   Lock the taxonomy

   Write down the approved sources and mediums and build new links from that list, so the same value is written the same way every time.

Common mistakes that keep traffic Unassigned#

If a quarterly review is coming up, do the cleanup before the numbers get presented — a 17% Unassigned bucket makes every channel comparison unreliable. Here is how to audit your UTM data before a QBR.