hi, i’m amr. open your ga4 traffic acquisition report and look for a row called unassigned. if it has real sessions in it, part of your channel data is going nowhere, and google’s help page says why.
what google analytics help says
in google’s words, “the unassigned row appears when Analytics cannot categorize the source of traffic.” traffic is grouped into channels by fixed rules, and a session that matches none of them lands there. the page lists the causes:
- tag order: “If the config command or Google tag fires after other events in the page, it may cause inaccurate reporting.”
- undefined sources: there may be no predefined rule if your traffic comes from a user-defined source or medium
- missing identity: traffic shows as (not set) when it is “missing session or user identity information”
- customized cookies or ids: changing the first-party cookie name, or modifying client_id and session_id from their auto-generated values, breaks how sessions are tracked
- a cross-domain linker that starts late, because user identity “will suddenly change at that point”
the fixes are on the same page: initialize the google tag before any event, put all page configuration in the config command, use one cookie prefix across the site, don’t customize client or session ids, and use user_id for a custom identity.
what to check this week
- open the traffic acquisition report, set the date range to the last 30 days and look at the unassigned row
- check your utm tags. a medium like “email-blast” or “paid-linkedin” that doesn’t fit a predefined rule is a likely cause. that is my reading of the list above, not google’s wording
- look at the order your tags fire in with tag assistant or gtm preview
- if you run several domains, confirm the cross-domain setup fires on first load
where this stops applying
the page gives no figures: no share of traffic that counts as too much unassigned, and no time limits. so this post makes no claim about how big your unassigned row should be. i haven’t seen anyone’s property, which means the check list above is where to start, not a diagnosis.
start scaling — if your channel report and your crm disagree about where leads come from, a tagging review usually finds the gap quickly. let’s connect.
Sources: Google Analytics Help, “Tagging best practices to avoid unassigned, (not set), and direct traffic issues” (support.google.com/analytics/answer/14847402). Figures are published product documentation, not verified results from Amr’s own client accounts.