Lorixen.
EN

GA4 'Unassigned' and '(not set)' traffic: causes and fixes

Short answer: "Unassigned" is the channel GA4 uses when a session's source and medium don't match any of its default channel rules; "(not set)" is the placeholder it uses when it received no value for a dimension at all. Most of it comes from a short list of causes: custom UTM mediums GA4 doesn't recognise, sessions missing their session_start event (often a tag trigger or consent setup issue), and sessions without a page_view. Fix the ones you control, then accept a small leftover.

A rising "Unassigned" line in GA4's traffic acquisition report makes it look as if a chunk of your visitors came from nowhere. Usually they came from somewhere perfectly ordinary, and GA4 simply couldn't file them. Here's how to work out which case you're looking at.

What the two labels actually mean

Google's default channel group documentation explains that channels are rule-based definitions of traffic sources, and that default channel groups can't be edited (you can create custom ones). It defines Unassigned as the value used when no other channel rule matches the event data, and lists the rules themselves. A few examples, as of November 2026:

  • Direct: source exactly "(direct)" and medium "(not set)" or "(none)"
  • Email: source or medium is email (several spellings, such as "e-mail", are accepted)
  • Referral: medium is "referral", "app" or "link"
  • AI Assistant: medium exactly "ai-assistant", set automatically when the referrer matches a list of AI assistants
  • Organic Search: a known search source, or medium exactly "organic"

Google's page on (not set) describes (not set) as a placeholder used when Analytics hasn't received any information for a dimension, and notes that when session source / medium is (not set), the traffic appears as Unassigned in the default channel group. So the two often show up together.

Symptom → cause → fix

Symptom Likely cause Fix
Unassigned sessions with a recognisable source (e.g. "newsletter", "facebook") Custom UTM medium that matches no rule (e.g. utm_medium=newsletter, social-post, whatsapp) Use mediums the rules understand: "email" for email, "referral" for links, and the ad mediums listed in Google's rule table for paid traffic; build links with a URL builder
Unassigned with source / medium "(not set)" Session missing its session_start event In Tag Manager, set the Google tag's trigger to "Initialization – All Pages", as Google's (not set) page describes
(not set) source / medium after adding a consent banner Consent mode implemented with the wrong command Use the consent update command after the visitor chooses, not a second default; don't send extra events with denied consent after consent was granted
Landing page "(not set)" Session had no page_view event (for example, a session that started with another event) Check page_view fires on every page load, including single-page app route changes
(not set) in Google Ads dimensions Ads and Analytics not linked, auto-tagging off, or traffic from an unlinked Ads account Link the accounts and turn on auto-tagging
(not set) for a custom parameter you just registered First 24 hours after registering Wait a day before investigating
Unassigned or (not set) from server-side events Measurement Protocol events not tied to a session See the section below
(other) rows Cardinality limits, a different issue from Unassigned Reduce high-cardinality dimensions; not fixable by tagging

Cause 1: UTM mediums GA4 doesn't recognise

This is the most common one on small business sites. Someone tags a newsletter link with utm_source=mailchimp&utm_medium=newsletter, or a WhatsApp broadcast with utm_medium=whatsapp. Neither "newsletter" nor "whatsapp" matches a rule, so the sessions land in Unassigned.

What to do:

  1. In GA4, open the traffic acquisition report, set the primary dimension to Session default channel group, filter to Unassigned, and add Session source / medium as a secondary dimension.
  2. List every source/medium pair you see.
  3. For pairs you created, change the medium on future links to one GA4 recognises. Check Google's rule table for the exact wording; for example, the Email channel accepts "email" in source or medium.
  4. Keep a shared sheet of approved source and medium values so everyone tags links the same way.

Past data won't be reclassified in the default group. If you need old campaigns grouped properly, create a custom channel group with rules that cover your old mediums.

Cause 2: missing session_start

When the session_start event is missing, the session has no source or medium recorded, so it's (not set) and therefore Unassigned. Google's (not set) page points to a specific configuration cause: a Google tag in Tag Manager that isn't using the "Initialization" trigger type. The fix is to change the tag's trigger to "Initialization – All Pages" and remove the old trigger.

The same Google page lists two consent mode mistakes that lead to (not set): using the default command for everything, including the update after the visitor clicks the banner (so the initial event with session_start is lost), and sending further events with denied consent after the visitor granted it (which GA4 treats as a separate session without session_start). Ask whoever installed your banner to check which commands it sends.

Some loss from visitors who decline is expected and not something to "fix"; the goal is only to remove losses caused by mistakes.

Cause 4: landing page (not set)

Google's explanation is short: the landing page dimension is (not set) when a session doesn't have a page_view event. Common real-world triggers include a session that starts with a non-page event, and single-page apps that don't send a page_view on route changes. Use DebugView or Tag Assistant to load a few pages and watch for page_view on each.

Cause 5: server-side events

If a developer sends purchases or leads from your server using the Measurement Protocol, Google's Measurement Protocol docs say it's meant to supplement, not replace, normal tagging, and that to attach an event to a specific session you include the session_id and send it within 24 hours of the session starting. Events that aren't linked to a session have no traffic source to classify, so check that your developer passes the session and client identifiers through.

When to stop worrying

Some Unassigned and (not set) will always remain. A reasonable approach:

  • Fix every source/medium pair you created yourself
  • Fix tag triggers and consent commands once
  • Re-check monthly in the traffic acquisition report
  • If what remains is a small and stable share, and it isn't hiding a campaign you care about, leave it

FAQ

Why did Unassigned jump after I changed my cookie banner?

A new banner often changes how consent commands are sent. Check for the two consent mistakes above.

Can I edit GA4's default channel rules?

No. You can create a custom channel group and use it in reports alongside the default.

Is Unassigned the same as Direct?

No. Direct has its own rule (source "(direct)", medium "(none)" or "(not set)"). Unassigned means nothing matched.

Will fixing UTMs fix my old reports?

Not in the default channel group. Use a custom channel group to regroup past data.

Untangling Unassigned traffic usually takes one careful look at your tags and links, and we're happy to review your GA4 setup with you.

Sources

WhatsAppLet’s talk