How to Fix GA4 “(not set)” and Unassigned Traffic

Every GA4 property I audit has some percentage of “(not set)” traffic — it’s universal. If you’re staring at your GA4 not set traffic source data wondering where your visitors actually came from, you’re not alone. Last quarter, I audited a SaaS company’s GA4 where 31% of all sessions showed as Unassigned. After implementing the fixes in this guide, we got it down to under 4% within two weeks. The remaining 4% was almost entirely consent-blocked users — an irreducible minimum.

The frustrating part? GA4 treats “(not set)” and “Unassigned” as two entirely different problems, but most guides lump them together. That leads people down the wrong troubleshooting path. This article separates them clearly, explains the root causes of each, and gives you step-by-step fixes you can implement today. If you’re new to GA4 or need a refresher on its data model, my complete GA4 guide for marketers covers the foundations you’ll need.

“(not set)” vs “Unassigned”: They’re Different Problems

Open your GA4 property, navigate to Reports > Acquisition > Traffic acquisition, and look at the Session default channel group column. You’ll likely see both — but they mean completely different things.

“(not set)” means GA4 has no data at all for that dimension. Source, medium, and campaign are blank. This is a data collection problem — something went wrong before data reached GA4.

“Unassigned” means GA4 does have source/medium data, but it doesn’t match any Default Channel Group rule. This is a classification problem — your channel rules need updating.

What Causes “(not set)” in GA4 Traffic Sources

Once you’ve confirmed you have a “(not set)” problem (blank source/medium), identify which root causes apply. Most properties have two or three happening simultaneously.

Missing or Broken session_start Event

This is the number one cause I encounter. The session_start event carries attribution data — it records where a session originated. If it doesn’t fire correctly, GA4 has no source/medium to attribute the session to. Common scenarios where this breaks:

• Your Google Tag (gtag.js) or GTM container loads after the user has already triggered page interactions
• A consent management platform delays tag firing past the point where GA4 can associate the session
• Custom GTM triggers accidentally prevent the default session_start from firing
• Single-page applications (SPAs) that don’t properly reinitialize GA4 on route changes

You can verify this in GA4 > Admin > DebugView. Open your site in a new incognito window and watch for the session_start event. If it doesn’t appear, or appears without traffic_type parameters, you’ve found your problem.

Consent Mode Blocking Attribution Data

If you’ve implemented Google Consent Mode v2, users who decline analytics cookies generate sessions with missing attribution data. GA4 sends “cookieless pings” that register as sessions but lack source/medium information. Google’s behavioral modeling tries to fill the gaps, but it doesn’t work well for properties under 1,000 daily users.

Session Timeout and Re-Entry Without Referrer

GA4’s default session timeout is 30 minutes. If a user returns after 31 minutes without a referrer (bookmark re-entries, certain browsers, HTTPS-to-HTTP transitions), GA4 creates a new session with no source data. This is especially common with content-heavy sites where users leave mid-article and return later via direct access.

Missing UTM Parameters on Campaign Links

Any external link — emails, social posts, partner sites, ads — needs UTM parameters. Without them, GA4 relies on referrer data alone, which privacy settings, redirects, or platform restrictions can strip. Common offenders I find in audits:

• Email marketing links without any UTM tags
• Social media bio links that weren’t tagged
• Links in PDFs, presentations, or offline materials
• Affiliate or partner links missing campaign parameters
• Internal links between subdomains without cross-domain tracking

Google Ads Auto-Tagging Issues

If you run Google Ads and rely on auto-tagging (GCLID), several things can break the attribution chain:

• Auto-tagging disabled in Google Ads account settings
• Google Ads not linked to GA4 (check Admin > Product Links > Google Ads)
• GCLID stripped by redirects — landing page redirects drop query parameters
• URL parameter conflicts — CMS or CDN configurations strip gclid

Always verify the Ads-GA4 link is active and test a click-through from an ad to confirm the GCLID survives the full redirect chain.

What Causes “Unassigned” Traffic in GA4

Unassigned traffic is easier to fix because the data itself is fine — it’s just not matching your channel rules.

Non-Standard UTM Values

GA4’s Default Channel Grouping uses specific utm_medium values to classify traffic. If your campaigns use non-standard values, GA4 can’t categorize them. As Julius Fedorovicius from Analytics Mania explains, this is the most common cause of Unassigned traffic. Here’s what GA4 expects versus what I commonly see:

Case Sensitivity Issues

GA4 is case-sensitive for UTM parameters. utm_medium=Email and utm_medium=email are treated as different values. Only lowercase email matches the Default Channel Grouping rule for the Email channel.

This is sneaky because everything looks correct at a glance. Someone on the team capitalizes a value, or your marketing automation platform auto-capitalizes the first letter — and perfectly tagged traffic lands in Unassigned. Fix: Always use lowercase for all UTM values, no exceptions.

Missing Custom Channel Group Rules

GA4’s Default Channel Grouping only covers standard channels. Custom sources like partner programs, in-app promotions, or SaaS-specific funnel tracking channels will show as Unassigned unless you create custom rules. For example, utm_medium=push has no default channel — you need a Custom Channel Group rule.

How to Fix GA4 “(not set)” Traffic (Step by Step)

Work through these in order — they’re sequenced from highest impact to most situational.

Step 1 — Audit Your UTM Tagging

Pull a report of all source/medium combinations for the last 90 days in Reports > Acquisition > Traffic acquisition (add secondary dimension “Session source / medium”). Then:

1. Export the full list of source/medium values
2. Identify campaigns or channels that show as (direct) / (none) but shouldn’t be direct traffic (emails, social posts, ads)
3. Create a UTM naming convention document and share it with every team that creates links
4. Retroactively add UTM parameters to all active campaign links
5. Use a centralized UTM builder (Google’s Campaign URL Builder works, or build a shared spreadsheet)

If you’re running SEO campaigns that drive traffic through linked content on other sites, make sure those backlinks are tracked properly. My SEO strategy guide covers how to combine UTM tracking with your organic strategy without creating duplicate content issues.

Step 2 — Verify session_start in DebugView

Install the Google Analytics Debugger extension, open your site in incognito, and navigate to GA4 > Admin > DebugView. You should see session_start fire on the first pageview with source, medium, and campaign parameters. If it’s missing or lacks attribution:

• GTM users: Verify your GA4 Configuration tag fires on “All Pages” with no blocking conditions (GTM > Tags > GA4 Configuration)
• gtag.js users: Ensure gtag('config', 'G-XXXXXXX') runs before any other interaction events
• SPA frameworks: Verify route changes trigger page_view events that fire session_start

Step 3 — Configure Referral Exclusions

When users return from payment processors, auth providers, or third-party tools, the third-party domain shows as the referrer — creating a new session with wrong attribution. Configure this at Admin > Data Streams > [Your Stream] > Configure tag settings > Show more > List unwanted referrals.

Common domains to exclude:

• Payment gateways: paypal.com, stripe.com, checkout.shopify.com
• Auth providers: accounts.google.com, auth0.com, login.microsoftonline.com
• Your own subdomains (if not using cross-domain tracking)

This prevents GA4 from creating new sessions when users return from these domains, preserving original attribution.

Step 4 — Set Up Cross-Domain Tracking

If users move between domains (e.g., www.yoursite.com to app.yoursite.com), each transition without cross-domain tracking creates a new session and loses attribution. Configure at Admin > Data Streams > [Your Stream] > Configure tag settings > Show more > Configure cross-domain measurement:

1. Add all your domains to the cross-domain configuration list
2. GA4 will automatically append a _gl parameter to links between configured domains
3. Test by clicking links between your domains and verifying in DebugView that the session continues (no new session_start event fires)
4. Make sure no server-side redirects strip the _gl parameter

Step 5 — Link Google Ads Correctly

Without proper Ads-GA4 linking, paid traffic shows as “(not set)” or gets misattributed.

1. Link accounts: Go to GA4 > Admin > Product Links > Google Ads links and verify your Ads account is connected
2. Enable auto-tagging: In Google Ads, go to Account Settings > Auto-tagging and ensure “Tag the URL that people click through from my ad” is checked
3. Test the GCLID: Click one of your ads and check the landing page URL — it should contain a gclid parameter. If not, check for redirect rules or URL parameter stripping in your CMS
4. Verify in GA4: In the Traffic acquisition report, paid traffic from linked accounts should appear as “Paid Search” — not Unassigned or “(not set)”

How to Fix “Unassigned” Traffic

Unassigned traffic is a classification problem with two fix paths: standardize your UTM values to match GA4’s defaults, or create Custom Channel Groups for your non-standard values. I recommend both.

Create Custom Channel Groups

Custom Channel Groups let you define classification rules that supplement or override GA4’s defaults. Go to Admin > Data Display > Channel Groups:

1. Click “Create new channel group” (or edit the existing custom group)
2. Review your Unassigned traffic in the Traffic acquisition report — note the source/medium values
3. For each Unassigned source/medium, create a new channel or add a rule to an existing channel
4. Use conditions like “Source matches regex” or “Medium exactly matches” to classify the traffic

Example custom rules:

• Push Notifications: Medium exactly matches push → Channel: “Push”
• In-App Messages: Source exactly matches in-app → Channel: “In-App”
• Partner Referrals: Medium exactly matches partner → Channel: “Partners”
• QR Codes: Medium exactly matches qr → Channel: “QR Code”

Custom Channel Groups apply retroactively to historical data. As MeasureSchool’s GA4 channel group guide explains, this is the recommended approach for reclassifying existing traffic without changing active campaign UTMs.

Standardize UTM Medium Values

To fix the problem at the source, standardize your UTM values to match GA4’s expectations. Here’s the reference table:

Quick Diagnostic Checklist

Work through each item in order to systematically resolve “(not set)” and Unassigned traffic.

1. Set your date range to exclude the last 48 hours — eliminates false positives from GA4’s processing delay
2. Check DebugView for session_start — does it fire on first pageview? Does it contain source/medium parameters?
3. Verify GTM/gtag.js loads on all pages — check new landing pages, subdomains, and app views
4. Review Consent Mode — is behavioral modeling enabled? Accept some irreducible “(not set)” from consent-blocked users
5. Audit active campaign UTMs — are all links tagged with lowercase, GA4-compatible values?
6. Check Google Ads linking — account linked in Admin > Product Links? Auto-tagging on? GCLID surviving redirects?
7. Review referral exclusions — payment processors, auth providers, and subdomains excluded?
8. Test cross-domain tracking — does the _gl parameter pass correctly between domains?
9. Check session timeout — is 30 minutes appropriate for your content?
10. Review Unassigned values — do any need Custom Channel Group rules?
11. Check audience triggers — verify no audience-triggered events interfere with attribution
12. Document your UTM convention — share and enforce naming rules across all teams

Frequently Asked Questions

Conclusion

“(not set)” and Unassigned traffic directly undermine data-driven decisions about budget allocation, campaign optimization, and channel strategy. Fixing your GA4 not set traffic source issues is systematic, not mysterious. Start with the quick wins: standardize UTM conventions, create Custom Channel Groups, and verify your Google Ads link. Then work through the deeper fixes: audit session_start in DebugView, configure referral exclusions, and set up cross-domain tracking.

Most properties can go from 20%+ unattributed traffic to under 5% within two weeks. The remaining percentage will always be there — consent-blocked users, edge cases, and processing delays. The goal isn’t perfection; it’s getting your data accurate enough to trust your decisions.