How to Fix "Unassigned" Traffic in GA4: Complete Diagnosis Guide

Why does GA4 show Unassigned traffic? Check source and medium values against current channel definitions, then inspect the traffic-source data GA4 collected.

Diagram showing how mismatched utm_medium values fall through GA4 channel rules into the Unassigned bucket
Table of Contents
  1. Why GA4 Creates the "Unassigned" Channel Group
  2. How to Audit What Lies Inside Your Unassigned Bucket
  3. Examples to Review When Investigating Unassigned
  4. How to Fix Unassigned Traffic: Present and Future

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:

  1. Navigate to Reports > Acquisition > Traffic acquisition.
  2. Click the + icon next to Session default channel group to add a secondary dimension.
  3. Select Session source / medium.
  4. 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_ad or utm_medium=promoted instead of paid_social.
  • Custom Email Mediums: Using utm_medium=klaviyo_flow or utm_medium=blast instead of email.
  • Missing utm_source: Providing utm_medium=cpc without utm_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

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