Table of Contents
Unassigned means the traffic-source data did not match an applicable GA4 channel rule. Look at the source and medium behind the row, then compare them with the current definitions. This guide walks through the checks.
Why GA4 Creates the "Unassigned" Channel Group
GA4 applies its current Default Channel Group definitions to the available traffic-source information. A session is Unassigned when no applicable definition matches the event data. The information considered can include source platform, campaign and advertising details as well as manually tagged source and medium values; review Google's current definitions for the relevant traffic type.
How to Audit What Lies Inside Your Unassigned Bucket
To investigate the traffic-source values associated with Unassigned sessions:
- Navigate to Reports > Acquisition > Traffic acquisition.
- Click the
+icon next to Session default channel group to add a secondary dimension. - Select Session source / medium.
- Filter the search bar for
Unassigned.
You will immediately see the rogue source/medium pairs that GA4 cannot categorize.
Examples to Review When Investigating Unassigned
- Non-Standard Social Mediums: Using
utm_source=facebook&utm_medium=fb_adorutm_medium=promotedinstead ofpaid_social. - Custom Email Mediums: Using
utm_medium=klaviyo_floworutm_medium=blastinstead ofemail. - Missing utm_source: Providing
utm_medium=cpcwithoututm_source. - Typos or Unexpected Values: A medium or source that does not match the current channel definition may lead to Unassigned. Google documents that default channel definitions are not case-sensitive.
- Event-Level Hits Without Session Context: Measurement Protocol server hits lacking session association.
How to Fix Unassigned Traffic: Present and Future
Require your media team to generate URLs using UTMCraft Bulk Matrix with pre-validated GA4 medium values.
In GA4 Admin, go to Data display > Channel groups > Create new channel group. Copy the default channel group, then add custom rules to map your legacy non-standard mediums (e.g. fb_ad, klaviyo_flow) into Paid Social and Email. This immediately cleans up your historical reporting dashboards without modifying raw underlying data.
For the broader setup, read GA4 UTM Tracking Troubleshooting Guide: Root Causes, Debugging & Solutions. Browse the GA4 Attribution & Troubleshooting guides to choose another troubleshooting task.
References
- GA4 Default Channel Grouping Rules (Google Analytics Help)