How to fix 'Unassigned' traffic in GA4?

The Short Answer

Unassigned traffic occurs when GA4 receives event data that doesn't match any of its default channel grouping rules, usually due to broken UTM parameters or missing session_start events.

The Context

We know how incredibly frustrating it is to log into your Google Analytics 4 acquisition reports only to see a massive chunk of your hard-earned traffic dumped into a bucket labeled "Unassigned".

Unlike Universal Analytics, which was heavily session-based, GA4 evaluates traffic on an event-by-event basis. If the metadata attached to a specific event does not strictly map to Google's rigid Default Channel Grouping rules, GA4 simply gives up and labels it "Unassigned." This ruins attribution, making it impossible to know which marketing campaigns are actually driving ROI.

The 3 Most Common Root Causes

If you are seeing Unassigned traffic, it is almost always caused by one of these three technical configuration errors:

1. Mangled or Non-Standard UTM Parameters Google Analytics 4 is exceptionally strict about UTM parameters. If you use a custom utm_source=IG but fail to include a utm_medium, GA4 often defaults to Unassigned. Furthermore, trailing spaces, inconsistent capitalization (e.g., utm_source=Facebook instead of utm_source=facebook), or custom parameters not recognized by GA4 will break the attribution chain.

2. Missing session_start Events (Orphan Events) In GA4, a session only truly begins when the session_start event is triggered. If a user leaves their browser tab open overnight, wakes up the next day, and clicks a button, a custom event might fire without triggering a new session_start. These floating "orphan" events have no session data attached to them, and thus, fall into the Unassigned void.

3. Broken Cross-Domain Tracking If you operate multiple domains (e.g., a main site shop.com and a checkout portal checkout.shop.com), users passing between them must retain their _gl linker parameter in the URL. If a redirect strips this parameter, GA4 treats them as a brand new user starting a brand new session from a "referral" source, or worse, strips the data entirely, resulting in Unassigned traffic.

How to fix it:

1
Audit your UTM hygiene across all ad platforms: Export a list of your top landing page URLs from Facebook Ads, Google Ads, and email campaigns. Ensure every single link contains both utm_source and utm_medium, strictly adhering to lower-case values.
2
Verify the session_start event in Google Tag Manager: Open GTM Preview mode and trigger a brand new visit to your website. In the GTM tag assistant, verify that the session_start event fires immediately after the page_view event. If it doesn't, your core GA4 configuration tag is firing incorrectly.
3
Test your Cross-Domain Linker: Click a link on your main domain that leads to your secondary domain (e.g., clicking 'Checkout'). Look at the URL bar on the checkout page. If you do not see ?_gl=1*... appended to the end of the URL, your cross-domain tracking is broken. Go to Admin > Data Streams > Configure Tag Settings > Configure your domains to fix this.
4
Check Measurement Protocol endpoints (Server-Side): If you are sending server-side events (like a Stripe webhook purchase), you must append both the exact client_id and the session_id to the payload. If these are missing, the purchase will show up in GA4 as Unassigned.

Want to check this automatically?

Instead of clicking through settings yourself, let our engine audit your GA4 Property for this exact issue (and 30 others) in 60 seconds.

Scan your setup with our Google Analytics 4 Audit Tool

The Context

We know how incredibly frustrating it is to log into your Google Analytics 4 acquisition reports only to see a massive chunk of your hard-earned traffic dumped into a bucket labeled "Unassigned".

The 3 Most Common Root Causes

If you are seeing Unassigned traffic, it is almost always caused by one of these three technical configuration errors:

How to fix it:

Audit your UTM hygiene across all ad platforms: Export a list of your top landing page URLs from Facebook Ads, Google Ads, and email campaigns. Ensure every single link contains both utm_source and utm_medium, strictly adhering to lower-case values.

Verify the session_start event in Google Tag Manager: Open GTM Preview mode and trigger a brand new visit to your website. In the GTM tag assistant, verify that the session_start event fires immediately after the page_view event. If it doesn't, your core GA4 configuration tag is firing incorrectly.

Test your Cross-Domain Linker: Click a link on your main domain that leads to your secondary domain (e.g., clicking 'Checkout'). Look at the URL bar on the checkout page. If you do not see ?_gl=1*... appended to the end of the URL, your cross-domain tracking is broken. Go to Admin > Data Streams > Configure Tag Settings > Configure your domains to fix this.

Check Measurement Protocol endpoints (Server-Side): If you are sending server-side events (like a Stripe webhook purchase), you must append both the exact client_id and the session_id to the payload. If these are missing, the purchase will show up in GA4 as Unassigned.