Unassigned Traffic in GA4: What It Means, Why It Grows, and How to Fix It

Open GA4’s Traffic acquisition table and you’ll see a row called Unassigned among the channels. It’s not ads, search or social, and when revenue or purchases show up there, you’ll want to know where they came from.

Revenue stuck in Unassigned makes your ads, newsletters and other sources look weaker than they are. Start with the steps in “How to see what’s inside Unassigned” below. If you run Shopify with the Google & YouTube app and Unassigned jumped partway through 2026, server-side purchase tracking is the likely cause.

This article is for anyone who uses GA4 to judge traffic and ad results. It covers what Unassigned means, how it differs from (not set) and Direct, the main reasons it grows, how to see what’s inside, and how to reduce it. Details reflect Google’s help center as of October 2026.

If you run a Shopify store with the Google & YouTube app and Unassigned revenue grew partway through 2026, also read our article on Shopify’s server-side purchase tracking to GA4. We found purchases sent this way landing in Unassigned with no source.

What Unassigned means in GA4

Unassigned in GA4 is where a session goes when it doesn’t match any rule in the default channel group (how GA4 looks at a session’s source and medium and sorts it into channels like Organic Search and Paid Social).

Source is where a visit came from (google, instagram and so on), and medium is how it came (cpc for ads, email and so on). On links you share, you set them by adding ?utm_source=…&utm_medium=… to the URL. These are UTM parameters. Channels are decided mostly by the session’s source and medium. For example, a medium of email means Email, and a search-engine source with a medium of cpc means Paid Search. Anything that matches no rule ends up in Unassigned.

You’ll find Unassigned under Session primary channel group (Default channel group) in the Traffic acquisition table (under Acquisition, or under the lead generation collection in some properties).

Unassigned vs (not set) and Direct

(not set) and Direct look similar but mean different things.

Bookmarks and typed URLs go to Direct. Sessions where no source / medium value arrived at all don’t match the Direct rule either, so they land in Unassigned. For the causes of (not set) by dimension, see our (not set) in GA4 article.

Why Unassigned traffic grows

There are two main causes: the source / medium never arrives, or a value arrives but matches no rule.

Here it is as a table.

The source / medium never arrives

GA4 sets source and medium from the session start (session_start) event. If no session start is recorded and only events like purchases arrive, source / medium is (not set), and the session lands in Unassigned. Google’s help center lists two causes: a GA4 configuration tag that isn’t triggered on Initialization, and consent mode set with only the default command, which drops the first event carrying session_start.

This often happens with server-side events. With Measurement Protocol (sending events to GA4 from a server), in our tests the session source wasn’t carried over unless we included the original visit’s client ID and session ID (the numbers GA4 uses to identify visitors and visits). See our Measurement Protocol article.

On Shopify, the Google & YouTube app started sending purchases from Shopify’s server to GA4 in 2026. In a client store, purchases sent this way landed in Unassigned with no page views and no source. See our article on Shopify’s server-side purchase tracking.

UTM values match no rule

If utm_medium carries a custom value and utm_source matches no rule either, the session lands in Unassigned even though values arrived. Google’s help center says the Email rule requires the source or medium to match email, e-mail, e_mail or e mail, so utm_source=mailmag with utm_medium=newsletter is Unassigned. With utm_source=email, though, it’s Email even when the medium is newsletter.

Many channel rules match when the source is on one of Google’s lists (search, social, shopping or video sites), whatever the medium. For example, utm_source=line goes to Organic Social even with a custom medium.

Links with only utm_source and no utm_medium also match nothing unless the source is on those lists or matches email, sms and the like. Putting a referring site’s domain in utm_source doesn’t make it Referral, because the Referral rule needs a medium of referral, app or link. Every channel’s rule is listed in Google’s “[GA4] Default channel group” help article. For UTM tagging, see our UTM parameters article.

How to see what’s inside Unassigned

You can check what’s inside Unassigned in the Traffic acquisition table.

1. Open Reports > Traffic acquisition and note the sessions and revenue on the Unassigned row
2. Click the dimension name at the top left of the table and switch to Session source / medium
3. Click Add comparison, choose Session primary channel group (Default channel group) as the dimension, Exactly matches, and Unassigned as the value, then apply
4. Each row shows two lines, “All Users” and “Unassigned”. Look at the rows with numbers on the Unassigned line

Pick a date range that covers the days before and after Unassigned started growing.

Here’s how rows map to causes.

If the (not set) / (not set) row has purchases or revenue, create the same comparison in the Landing page report and look at the (not set) landing page row. These are sessions where a purchase arrived with no page views. Sessions split by consent mode settings and purchases made after a 30-minute session timeout look the same as server-side purchases. To tell them apart, check changes made around that date and the breakdown by event name (whether events other than purchase exist).

What to check when it suddenly grows

1. In the Traffic acquisition chart, find the day Unassigned started growing
2. Check for changes to UTM tagging, tags, apps or the consent banner around that day
3. Look for annotations on the chart (such as “New Shopify integration”). Click the icon under the chart to see their names
4. Use the steps above to see whether the increase is (not set) / (not set) or a custom medium

How to reduce Unassigned traffic

The fix depends on the cause.

Here’s how to tag common campaigns.

Create custom channel groups under Admin > Data display > Channel groups. Copy the default channel group into a new group and add rules that map your custom media to Email and so on. Google’s help center says custom channel groups can be applied retroactively. Creating one doesn’t shrink Unassigned in the Default channel group, though. Switch the report’s dimension to your new channel group to see the change.

Some Unassigned traffic remains by design: purchases that never pass through your store’s pages, such as purchases sent by Shopify’s Google & YouTube app from the server, or subscription renewal orders sent from a server. For those, compare channels with Unassigned excluded, and include it only when you look at totals.

Summary

• Unassigned in GA4 is where sessions go when they match no rule in the default channel group
• Direct is a visit with no source information, and (not set) means a value never arrived. Both are different from Unassigned
• The two main causes are a source / medium that never arrives and UTM values that match no rule
• Switch Traffic acquisition to Session source / medium and compare with Unassigned to see which cause you have
• Use rule-matching UTM values or a custom channel group, and send session IDs with server-side events

Sources

• [GA4] Default channel group (Google Analytics Help)
• [GA4] What the value “(not set)” means in your reports (Google Analytics Help)
• [GA4] Traffic-source dimensions scope (Google Analytics Help)
• [GA4] Custom channel groups (Google Analytics Help)
• Send Measurement Protocol events to Google Analytics (Google for Developers)