TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-049

SYMPTOM FILE SYM-049 FILED 09 NOV 2026 · REVISED 09 NOV 2026

GA4 Unassigned traffic: what it means and how to fix it.

ALSO FILED AS
  • “ga4 unassigned traffic”
  • “why is my traffic unassigned in ga4”
  • “ga4 unassigned vs not set”
  • “ga4 session default channel group unassigned”
  • “how to fix unassigned traffic in ga4”
  • “ga4 unassigned medium not recognised utm”

Baris Asa, tracking consultant, London · Last checked: 9 November 2026

Unassigned means GA4 couldn’t match a session to any default channel. The visits are real. Usually your links use a medium GA4 doesn’t read (newsletter / blast, say), or the session has no source at all ((not set) / (not set)). Open Unassigned by source / medium to see which. Fix: rename the medium to one the default rules read (email, affiliate, paid_social, cpc), or move the Google tag to the Initialization trigger if the source shows (not set). Google’s default channel group page defines Unassigned as the value used when there are no other channel rules that match.

To see yours, open Reports, Acquisition, Traffic acquisition, then:

  1. Set the dimension to Session default channel group.
  2. Click the Unassigned row.
  3. Add Session source / medium as the second dimension.
SESSION SOURCE / MEDIUMWHAT IT MEANSFIRST CHECK
newsletter / blastBoth values present, medium no rule readsCause 1: rename the medium
crm / journeySame: your own naming, no rule matchesCause 1: rename the medium
(not set) / (not set)No source on record for the sessionCause 2: session_start
WHAT SITS IN UNASSIGNED · Session source / medium, last 28 days · worked example, illustrative, not a client account

Both values present is a naming problem. Both (not set) points to a collection problem: Google lists a missing session_start as a common cause. The two get different fixes, so name the row first. Revenue sitting in Unassigned is worth tracing before anything else, because it’s also one place your GA4 channel revenue and your store’s numbers can part ways.

Cause 1: the medium is one the rules don’t read

The default rules key off the medium, and sometimes the source. The ones people tag most, from Google’s default channel group page (check the full rule there before renaming, since some rows also read the source):

  • Email: source or medium is email, e-mail, e_mail or e mail.
  • Affiliates: medium is affiliate.
  • Referral: medium is referral, app or link.
  • Display: medium is display, banner, expandable, interstitial or cpm.
  • Paid Search and Paid Social: a source on Google’s search or social site list, plus a medium that is ppc or retargeting, contains cp, or starts with paid.

Google’s page lists the rest (Organic Social, Organic Video, SMS, Audio, AI Assistant and more). Check a candidate medium against all of them, because several are pattern matches, not exact words. A medium of partner_push isn’t Unassigned: it ends with push, so it goes to Mobile Push Notifications. Anything containing video goes to Organic Video the same way. Those are wrong buckets, and they won’t show up as Unassigned.

What does fall through: a medium that matches nothing and a source that isn’t on a site list. newsletter / blast, partner / promo, crm / journey. A source on the social list goes to Organic Social when the medium isn’t paid, so a mislabelled paid social medium usually turns up there. The attribution order note works through that case.

Test: list every source / medium pair in Unassigned and check each medium against Google’s list. Change it to the nearest one the rules read (email, affiliate, paid_social, cpc), in lowercase. For the paid ones the source matters too: Paid Search and Paid Social also need a source on Google’s search or social list (google, facebook). If your source is your own name, change the source as well, or use a custom channel group. Or build a custom channel group that claims your pairs. Standard properties get 2 custom groups with up to 50 channels each, and 360 properties get 5. The predefined default can’t be edited, but Google says the primary channel group, the property’s editable default, can.

Renaming fixes the Unassigned pairs you’ve found today. If several teams or agencies build campaign links, new pairs tend to come back the next month unless everyone tags to one written UTM convention: lower case, one source per platform, one medium per channel, and each medium one GA4’s default rules read. I write that convention and hand it over; it is part of my attribution repair for ecommerce stores.

Cause 2: no session_start, so no source

When session source / medium shows (not set), Google says a common cause is a missing session_start event. Its example is the Google tag (formerly the GA4 configuration tag) not using the Initialization trigger in Tag Manager. Google’s fix is to add the Initialization - All pages trigger, remove the previous trigger, save and publish.

To check, open DebugView or Tag Assistant and load a page on a fresh visit. session_start should come first. If other events arrive without it, the session has no source to report. Google also says session_start and first_visit values can show (not set) when they weren’t in the first event, so (not set) doesn’t prove the trigger is wrong.

If the tag is already on Initialization, ask who else sends hits to the property: a second tag, a server container, a developer’s own script. This is a developer or agency task. The sentence to send them:

Is the Google tag on the Initialization - All pages trigger, and does anything else send events to this GA4 property?

How do I fix it, in order?

  1. Open Unassigned by session source / medium and list the pairs. Both values present means Cause 1. Both (not set) means Cause 2.
  2. Fix naming. Rename the medium on the live links to one the default rules read, in lowercase. Or add a custom channel group.
  3. Check session_start in DebugView. If it’s missing, fix the Google tag trigger (developer task, sentence above).
  4. Check the Google Ads link if Ads clicks are in the row. Admin, Google Ads links (menu names move, so search Admin if it isn’t there). Google says a new link can take up to 48 hours to show Ads data, and lists an unlinked account, auto-tagging switched off and a click ID dropped in redirects as causes of missing Ads data. It doesn’t say how those sessions are channelled, so look at what source / medium your Ads clicks carry.
  5. Date the change. Tag and tracking fixes affect new sessions only. A custom channel group re-sorts past data in your reports, though Google says it isn’t in the BigQuery export. Note which one you used when you compare periods.

What else to rule out

  • Fresh data. Google says processing can take 24 to 48 hours. If only yesterday looks odd, wait.
  • Server-sent events. Measurement Protocol is how a server sends events to GA4 without the browser. Google’s guide says a new session_id creates a new session without the need for session_start, and that the client_id should match the one the site’s tag generated. It doesn’t describe traffic source for these events. If your server sends purchases, filter Unassigned to that event name and compare its client_id and session_id with the browser’s. Google doesn’t document this as a cause of Unassigned. Check it against your own report.
  • Redirects and own domains. Redirects that strip UTMs more often show as Direct, and a second domain or payment return shows as a referral. The direct traffic note covers the first, and F-204 is the nearest filed case: attribution lost before the report. It isn’t a cause of Unassigned as such.

Is Unassigned the same as (not set) or (other)?

No, and mixing them up sends people to the wrong fix. Google defines each separately.

  • Unassigned: a channel. No rule in the default channel group matched.
  • (not set): a missing value in a dimension. Google says traffic with source / medium (not set) is shown as Unassigned in the default channel group. So (not set) can put sessions in Unassigned, but Unassigned can also be a real source and medium that no rule reads.
  • (other): an aggregated row, used because of cardinality limits (too many unique values for one report). A row-limit problem, not a channel problem. See GA4 hides data behind (other) and R-502 .

Send me the list

If the row holds revenue or your campaign links and nobody on your side owns the tags, send me the source / medium list from step 1 and I’ll tell you which cause it is. Or send it to your developer with the sentence above. I take this on as a GA4 consultant.

Does a small Unassigned row matter?

Compare its share of sessions and of revenue against the channel total. A few odd sessions can be one stray tag. A row that holds your campaign links or revenue is the one to trace.

Sources: Google Analytics Help on the default channel group, custom channel groups, what (not set) means, missing Google Ads data and collecting campaign data with custom URLs. Google for Developers, Measurement Protocol: sending events.

← back to the reading room