GA4 assigns revenue to channels using the traffic-source information available on the converting session or attributed touchpoint. When that information is incomplete or does not match channel rules, revenue can land inUnassigned. That is usually a tagging, redirect, or channel-grouping problem worth investigating.
How GA4 default channel groups work
GA4'sDefault Channel Groupis a system dimension that maps each session to a named channel. Organic Search, Paid Search, Email, Direct, Referral, Organic Social, and so on, based on rules that evaluateutm_source,utm_medium, and sometimesutm_campaign. These rules are applied at query time, not at collection time, which means changing your custom channel groupings affects historical data.
TheUnassignedchannel is the channel of last resort. A session lands in Unassigned when no default channel rule matches its source/medium combination. This often points to UTM hygiene problems, missing attribution context, or a channel pattern that needs to be reviewed against Google's rules. For a deeper look at how the same root causes feed into broaderGA4 not-set values, see the dedicated guide.
High-cardinality acquisition data also amplifies this problem, our piece onGA4 source/medium cardinalitycovers how UTM sprawl can push otherwise-valid traffic into Unassigned via (other) bucketing.
rules should be reviewed before blaming attribution reports
are a common root cause when revenue lands in Unassigned
can strip attribution before revenue is reported
Why revenue ends up unassigned
Unassigned revenue is not a GA4 bug, it is a data quality signal. The most common root causes are non-standard medium values (e.g.,EDMinstead ofemail), missing UTM parameters on paid campaigns, and redirect chains that strip UTM parameters before they reach GA4. Our walkthrough ofUTM governancecovers the conventions that prevent these issues at source.
The problem is compounded for e-commerce sites where conversion paths span multiple sessions. If a user's first touch was a paid ad with a stripped UTM, and they convert on a direct return visit, that revenue may land in Direct or Unassigned depending on the attribution model in use, our explainer onGA4 attribution modelscovers how credit is distributed in each scenario.
Identify unassigned sessions and their volume
Open the Traffic Acquisition report. Filter by Default Channel Group = Unassigned. Record the session count and, if you have e-commerce, the revenue attributed to Unassigned. This establishes your baseline problem size.
Extract the source/medium values behind unassigned
In the same report, add Session source / medium as a secondary dimension while filtered to Unassigned. This reveals exactly which source/medium combinations are failing to match a channel rule. Export this list.
Map each non-matching value to its intended channel
For each source/medium pair in your list, determine which channel it should belong to. Typically you'll find typos (em instead of email), custom medium values from ESPs, or paid traffic missing UTMs entirely.
Fix UTM values at source where possible
For future traffic, correct the UTM values at the platform level. Update email templates, fix redirect configurations, and add UTM parameters to paid campaigns that were missing them. This prevents new Unassigned sessions.
Create custom channel groupings for legacy patterns
For source/medium patterns you cannot change (e.g., traffic from a partner that uses their own UTM conventions), create a custom channel grouping rule in GA4 that maps those patterns to the correct channel. This improves historical and future data.
Monitor unassigned share over time
Set a monthly review to check the Unassigned session and revenue share. If the share climbs, a new campaign or integration has likely introduced non-standard attribution data.
Unassigned revenue audit plan
Validate
- Check Default Channel Group distribution and investigate any meaningful Unassigned revenue or session share
- Export the source/medium values behind all Unassigned sessions
- Verify that all active email campaigns use utm_medium=email exactly
- Check paid search campaigns for missing or non-standard utm_medium values
- Confirm redirect chains on landing pages preserve UTM parameters
Fix
- Correct utm_medium typos and non-standard values in email platform templates
- Add UTM parameters to all paid campaigns missing them
- Create custom channel grouping rules to capture known non-standard partner UTMs
- Fix redirect configurations to pass through UTM parameters
- Implement a pre-launch UTM validation check for all new campaigns
Watch for
- Unassigned share increasing month-over-month, indicates new tagging problem
- Revenue in Unassigned spiking around campaign launches
- New integrations or affiliate platforms using non-standard medium values
- Seasonal campaigns with rushed UTM setup skipping naming conventions
Channel attribution health checklist
- Unassigned channel share is reviewed regularly and unexplained increases are investigated
- All email campaigns use utm_medium=email (lowercase, exact match)
- Paid search campaigns use utm_medium=cpc or utm_medium=ppc
- Paid social campaigns should use utm_medium=paid-social or utm_medium=paidsocial to match GA4's Paid Social channel group rules
- No redirect chains stripping UTM parameters before GA4 collection
- Custom channel groupings created for known non-standard partner traffic
- UTM naming convention documented and shared across all marketing teams
Related guides to read next
Why Your Source/Medium Changed to Direct
Redirects and missing UTMs that send traffic to Unassigned often also inflate Direct.
GA4 Attribution Models Explained
Once channels are correctly assigned, understand how credit is distributed across touchpoints.
GA4 Conversion Tracking Setup
Ensure conversions and revenue events are firing correctly before auditing attribution.
Review unassigned revenue in GA4
GA4 Audits helps surface channel-rule gaps, broken UTMs, and redirect issues that commonly push revenue into Unassigned.