Why does my Landing Page report show "(not set)"?

Usually a missing or malformed page_location parameter on the page_view event, often from a broken redirect, migration, or a single-page app firing the pageview before the URL updates.

Why does Session source/medium show "(not set)"?

This is how unassigned traffic appears in that report — GA4 has partial acquisition data but couldn't map it to a channel, usually due to incomplete UTM tagging.

Is "(not set)" in the Campaign dimension always a problem?

No. Organic search and direct traffic never carry a campaign name, so "(not set)" there is often expected. It's only worth investigating if a paid or email campaign was supposed to be tagged and isn't showing up.

What Does "(not set)" Mean in Google Analytics?

"(not set)" in Google Analytics means GA4 has no value to display for a dimension in that row of data. It's not one specific bug with one specific fix — it shows up in different reports for different reasons: missing UTM parameters, a page with no title tag, a deleted or renamed dimension value, or a tracking gap. The fix depends entirely on which report it's appearing in.

Landing page: (not set)

This usually means GA4 received a pageview event with a missing or blank page path — the page_location or page_referrer parameter didn't come through cleanly. It's common right after a site migration, a broken redirect, or a tag misconfiguration where the page_view event fires before the URL is fully resolved.

Check that your Google tag or Google Tag Manager container is firing page_view with a valid page_location parameter on every page, and audit any client-side routing (single-page apps in particular) for pageviews firing before the URL updates.

Source / medium: (not set)

This is usually what unassigned traffic looks like in the Traffic Acquisition report's Session source/medium dimension — GA4 has some acquisition data for the session but not enough to map it to a defined channel. The most common cause is incomplete UTM parameters, like a link with utm_source set but no utm_medium.

Audit your tagged links for missing parameters, and check custom channel group rules in Admin for coverage gaps that leave certain source/medium combinations unclassified.

Campaign: (not set)

This shows up when a session has source and medium data but no utm_campaign value — common for traffic tagged only with utm_source and utm_medium, or for default channel traffic like organic search and direct, which never carries a campaign name in the first place.

This one isn't always a problem to fix — organic and direct traffic legitimately have no campaign, so "(not set)" here is often expected rather than broken. It's only worth investigating if you expected a paid or email campaign to be tagged and it's showing up without one.

Other places it appears

Page title: a page missing a <title> tag, or a single-page app that doesn't update the title on route changes, will show "(not set)" in reports keyed by Page Title.

Custom dimensions: if a custom dimension is registered in GA4 Admin but the corresponding event parameter isn't being sent on every relevant event, rows without that parameter show "(not set)" for the dimension rather than being excluded.

Item/product dimensions in ecommerce reports: missing item_category, item_brand, or similar parameters on purchase or view_item events produce the same "(not set)" pattern in ecommerce breakdowns.

FAQ

What does "(not set)" mean in Google Analytics?: It means GA4 has no value to show for a given dimension on that row of data. The specific cause depends on which report and dimension it appears in — it's not a single bug with one fix.
Why does my Landing Page report show "(not set)"?: Usually a missing or malformed page_location parameter on the page_view event, often from a broken redirect, migration, or a single-page app firing the pageview before the URL updates.
Why does Session source/medium show "(not set)"?: This is how unassigned traffic appears in that report — GA4 has partial acquisition data but couldn't map it to a channel, usually due to incomplete UTM tagging.
Is "(not set)" in the Campaign dimension always a problem?: No. Organic search and direct traffic never carry a campaign name, so "(not set)" there is often expected. It's only worth investigating if a paid or email campaign was supposed to be tagged and isn't showing up.

If you're here because GA4 is confusing — that's why we built Gizmo.

A dead-simple, cookieless Google Analytics alternative. Free forever, 10k events/mo.

Try Gizmo free See the GA4 alternative