GA4 Unassigned Traffic: Why It Happens and How to Fix It with Custom Channel Groups
Open Reports → Acquisition → Traffic acquisition in GA4 and you may see a channel called Unassigned with a surprising share of your sessions. Those sessions are not lost. GA4 knows where they came from; it just couldn’t match them to any channel in its rules.
The trouble is that Unassigned traffic can’t be credited to Paid Social, Email or Paid Search, so those channels look weaker than they are, and any decision based on channel performance gets skewed.
This guide shows how to find what is causing it, fix it at the source, and use a custom channel group where your marketing doesn’t fit Google’s defaults.
How GA4 decides the channel
GA4 assigns every session to a channel using the Default channel group: a fixed list of rules based mainly on source, medium and campaign name. For example:
- Email needs a medium like
emailore-mail. - Paid Search needs a known search engine as the source and a paid-looking medium such as
cpcorppc. - Paid Social needs a known social site as the source and a paid medium.
If a session’s values don’t match any rule, it lands in Unassigned. So Unassigned is almost always a tagging problem, not a GA4 bug.
Step 1: Find the values behind Unassigned
- Open Traffic acquisition.
- Change the primary dimension to Session source / medium (or add it as a secondary dimension next to Session default channel group).
- Filter or search for rows where the channel is Unassigned.
You’ll usually see a handful of patterns repeating. Write them down: they are your fix list.
Step 2: Match the cause
| What you see | Why it’s Unassigned | Fix |
|---|---|---|
newsletter / email-blast, mailchimp / newsletter | Medium isn’t a recognised email value | Use utm_medium=email |
facebook / paid-social-ads, fb / cpc | Source or medium doesn’t match Google’s social lists or paid patterns | Use a recognised source (facebook, instagram) and utm_medium=paid_social or cpc |
google / adwords, bing / ad | Medium doesn’t match the paid search pattern | Rely on auto-tagging (GCLID / MSCLKID), or use utm_medium=cpc |
(not set) / (not set) | Session started without source data: events before session_start, consent pings, or Measurement Protocol hits without session info | Check tag order, Consent Mode, server-side events |
| Brand names, partner names as medium | Custom values Google can’t know | Pick a standard medium (referral, affiliate, display) |
| Many sessions from your own payment domain | Payment gateway starts a new session | Add it to List unwanted referrals |
Step 3: Fix the tagging at the source
A channel group can relabel sessions in reports, but it doesn’t fix the data in other tools, and it doesn’t stop new campaigns from being tagged inconsistently. The real fix is a UTM naming standard that everyone follows. If you are experiencing high unassigned volume triggered by consent pings, payment redirects, or cross-domain gaps, follow our complete triage in the GA4 (Unassigned) Traffic Fix Guide:
- Lowercase everything.
Facebookandfacebookare different values in GA4. - One word per medium:
cpc,paid_social,email,affiliate,display,referral,sms. - One spelling per source:
facebook(notfb,meta,Facebook-Ads). - Never tag internal links with UTMs. That starts a new session and overwrites the real source.
A shared template helps: the UTM Maker builds consistent links, and the UTM Analyzer checks existing ones for mistakes.
Step 4: Build a custom channel group
When your marketing has channels Google doesn’t know about (an affiliate network, a partner newsletter, an SMS tool, AI chat assistants as a referral source), a custom channel group lets you define your own rules.
- Go to Admin → Data display → Channel groups.
- Copy the default channel group rather than starting from scratch, so the standard rules stay in place.
- Add your own channels, for example:
- SMS: medium exactly matches
sms. - Affiliates: medium matches
affiliateor source contains your affiliate network. - AI assistants: source matches regex
chatgpt|perplexity|copilot|gemini.
- SMS: medium exactly matches
- Reorder the channels. GA4 uses the first rule that matches, so specific rules must sit above broad ones.
- Save, then choose the new group in reports (for example in Traffic acquisition, or as a dimension in Explorations).
Two useful properties of custom channel groups:
- They apply to historical data in reports, so you can see past months with the new rules.
- They don’t change the raw data. You can adjust the rules at any time without losing anything.
Step 5: Watch it over time
After fixing tags and adding your group:
- Check the share of Unassigned once a week for a month. It should fall steadily as new campaigns use the standard.
- Add Unassigned to your monthly reporting checklist, so a new team member or agency using their own UTMs gets caught early.
- If
(not set)stays high, look at Consent Mode and server-side events next: those are configuration issues, not naming issues.
Need cleaner attribution?
If channel reports drive budget decisions and you can’t trust them, I set up GA4 properties, UTM standards and channel groups as part of a full measurement setup. See the GA4 & GTM service or book a free tracking audit.
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.

