Analytics and tracking

Why is most of my GA4 traffic showing as Unassigned?

GA4 labels traffic Unassigned when no channel rule matches the event data, and shows (not set) when it received no information for a dimension. The usual causes are incomplete campaign links, a Google Ads link or auto-tagging problem, and tags that run in the wrong order.

Published . Last updated . By Hevaris.

What do Unassigned and (not set) mean?

Unassigned is a channel label, and (not set) is a placeholder for missing information. They are related but not the same, which is why the two terms appear together in reports.

Google says Unassigned is used when no other channel rule matches the event data. It describes (not set) as a placeholder GA4 uses when it has not received any information for a dimension, and says a (not set) session source or medium appears as Unassigned.

What causes Unassigned traffic?

The causes Google lists are about how links are tagged and how tags run. The table pairs each with a way to check it and the usual fix.

CauseHow to checkTypical fix
The source or medium fits no channel ruleLook at the source and medium of the Unassigned rowsCorrect the values on your links, or group the traffic in a custom channel group
Incomplete or incorrect UTM parameters on tagged linksOpen the tagged links and read the utm valuesUse utm_source, utm_medium and utm_campaign on every tagged link, with consistent values
Google Ads is not linked, or auto-tagging is offCheck the Google Ads link and the auto-tagging settingLink the accounts and turn auto-tagging on
The Google tag does not run before events are sentCheck the order of tags in Tag Manager PreviewInitialise the Google tag or Tag Manager configuration before events fire
Consent mode default or update errorsTest the site with consent accepted and declinedCorrect how the consent tool sets the defaults and updates

What does Google advise to reduce it?

Google gives tag and setup steps. They are about order and consistency, and they do not need new tools.

  • Initialise the Google tag or the Tag Manager configuration before sending events, and do not fire custom events before it.
  • Use one consistent cookie prefix.
  • Do not customise the client or session identifiers.
  • Do not run a server-side and a standalone client-side setup for the same property.

Google’s campaign guidance adds that you should keep utm values consistent, with one source value per platform.

How do I find out which cause applies to me?

Start with the sources, then the tags. Look at which source and medium the Unassigned rows carry, because that points at links, and then check the tag order in Tag Manager Preview.

  1. Read the source and medium of the Unassigned traffic. A recognisable source with an unexpected medium points at a link tagging problem.
  2. Open a tagged link and check all three utm values are present and consistent.
  3. Check Google Ads, if you use it, for the link and auto-tagging.
  4. Check the tag order in Preview, and test consent accepted and declined.

Fix one cause, then watch new traffic. Past data stays as it was labelled.

What sources does this guide use?

The primary sources are linked below, so each statement can be checked at its origin.

Frequently asked questions

What is the difference between Unassigned and (not set)?

Unassigned is a channel label used when no channel rule matches the event data. (not set) is a placeholder used when GA4 has not received any information for a dimension. Google says a (not set) session source or medium appears as Unassigned in the channel report.

Are UTM links a cause?

They can be. Google lists incomplete or incorrect UTM parameters on manually tagged links among the causes of (not set) values. Google also says utm_source=google and utm_source=Google are different values, so inconsistent capitalisation splits your data.

Does consent mode play a part?

It can. Google lists consent mode default or update errors among the causes of (not set) values. If Unassigned rises after a banner change, test the consent tool setup.

Will Unassigned traffic fix itself?

Not by waiting. The causes are in how links are tagged or how tags run, so the data stays unassigned until the cause is fixed. A fix applies from then on and does not relabel past data.