← Blog·Analytics Implementation

Analytics Implementation

What is (not set) in Google Analytics and how to fix it

Learn what (not set) means in Google Analytics 4, why it shows up in landing page, source, campaign and custom dimension reports, and how to fix each cause.

David PombarSwiss army knife at Trackingplan
7 min read · 1621 words

TL;DR (not set) means GA4 received no value for the dimension you are looking at. The data arrived; the field was empty. Each report has its own usual cause: sessions without a page view in the landing page report, missing or broken attribution in source and campaign reports, parameters that were never sent in custom dimensions. Find the report, match the cause, fix it at the source. Filtering it out hides the problem; it does not remove it.

(not set) is GA4's placeholder for an empty value. It is not an error message and it is not a category of traffic. It is a row of sessions, users or conversions that GA4 could not label, and those rows are often the ones that matter most: an organic landing page you cannot see, a paid campaign that gets no credit, a product with no name in the revenue report.

A small amount is normal on any property. A large share, or a share that grows suddenly, means something in your tracking or your configuration changed.

Where (not set) appears and what causes it

The cause depends on the report. Start from where you see it.

Report or dimensionWhat is missingUsual causes
Landing pageA page_view at the start of the sessionSession started by another event after the timeout; events before the Google tag; Measurement Protocol hits; single-page app without page views
Session source / mediumThe attribution of the sessionEvents with no session context (Measurement Protocol, server-side without client data); referrer lost on a redirect; consent setup that drops attribution
Session campaignA campaign nameGoogle Ads not linked or auto-tagging off; links with utm_source and utm_medium but no utm_campaign
Custom dimensionsThe event or user parameterParameter not sent with that event; dimension registered after the data arrived; wrong scope (event vs user); name typo
Page titleThe title of the pagePages without a <title>, or a tag that overrides it with an empty value
Item name, item categoryFields in the items arrayEcommerce events sent without those fields, or with a different key
Country, city, networkThe location of the visitorIP addresses GA4 cannot map, for example from some VPNs or server-side setups that do not forward the visitor's IP
Google Ads dimensionsAds data for the clickGoogle Ads account not linked to the GA4 property

Landing page (not set)

This is the one SEO and content teams see most, because it hides which pages bring traffic.

GA4 takes the landing page from the first page_view of the session. A session that never sends one has no landing page. The usual ways that happens:

Our post on diagnosing (not set) with session_start walks through finding these sessions in an exploration.

Source, medium and campaign (not set)

Here the session exists but GA4 cannot say where it came from.

A growing share of (not set) source next to a falling Organic Search channel is worth checking before anyone blames rankings. Our guide to an organic traffic drop covers that order of checks.

Custom dimensions and event parameters (not set)

A custom dimension shows (not set) for every event that did not carry its parameter. Check four things:

  1. Was the parameter sent? Look at the event in DebugView or in Tag Assistant. If the parameter is not there, the problem is in the tag or the dataLayer.
  2. Is it sent with this event? A parameter sent with purchase is (not set) when you look at page_view. Build the report on the events that carry it.
  3. When was the dimension registered? Custom dimensions only apply to data collected after you create them. Earlier dates show (not set).
  4. Do the name and scope match? The parameter name is case-sensitive, and a user property registered as an event-scoped dimension will not fill in.

The same logic applies to ecommerce: an items array without item_name or item_category gives (not set) rows in every item report.

How to diagnose it, step by step

  1. Measure the share. Put the dimension in a free-form exploration with sessions or event count and see what share is (not set). Then plot it by day: a stable share is background noise, a step change has a date.
  2. Find the date. Match the step change with releases, tag manager publishes, consent changes and campaign launches.
  3. Narrow it down. Add device, browser, hostname and event name. A problem in one browser, one domain or one event points to its cause.
  4. Reproduce it. Open the affected page with Tag Assistant or GTM preview, and look at the order of events and the parameters each one sends.
  5. Fix at the source and annotate the dates in your reports, so nobody compares against them later as if they were real.

(not set), (other), (direct) and Unassigned

Four labels that get confused:

LabelMeaning
(not set)GA4 received no value for this dimension
(other)GA4 grouped rare values together because the dimension has too many distinct values in the report
(direct) / (none)The session had no referrer and no campaign parameters
UnassignedGA4 has a source and medium, but no rule of the channel group matches them

(other) is a reporting limit, not missing data; use an exploration or BigQuery to see the rows. Unassigned has its own causes, covered in what Unassigned traffic is in Google Analytics.

Catch it the day it starts

Most (not set) problems start on a specific day: a release removes a page view, a tag manager publish changes the event order, a campaign goes out without its UTMs, a new event ships without the parameter a dimension depends on. Found a month later, the affected data cannot be repaired.

Trackingplan watches the hits your site sends, per event, per property and per platform, and flags anomalies, missing properties and consent breaches as they appear. A parameter that stops arriving, a page view that disappears from a template or a campaign without its UTMs shows up the day it happens, with links to the affected hits, instead of as a growing (not set) row at the end of the month.

(not set) is GA4 telling you it was not given something. The fix is always the same: find out what, and since when.

Frequently asked questions

What does (not set) mean in Google Analytics?

It means GA4 received no value for that dimension. The data was collected, but the field the report is grouped by was empty: a session without a page view has no landing page, an event without a parameter has no value for the custom dimension built on it, and a visit GA4 cannot attribute has no source.

Why is my landing page (not set) in GA4?

Because the session has no page_view event. The usual cause is a session that starts with another event: a visitor comes back to an open tab after the 30-minute session timeout and clicks or scrolls, so GA4 starts a new session without a page view. Events sent before the Google tag loads, Measurement Protocol hits and single-page apps that do not send page views on route changes cause it too.

Can I just filter (not set) out of my reports?

You can hide it in an exploration, but the sessions and conversions behind it are still real. Filtering only removes the evidence of a tracking or configuration problem. Find the cause, fix it, and annotate the affected dates instead.

Is (not set) the same as (other), (direct) / (none) or Unassigned?

No. (not set) means the value is missing. (other) means GA4 grouped rare values together because the dimension had too many distinct values. (direct) / (none) means the visit had no referrer and no campaign parameters. Unassigned means GA4 has a source and medium but none of the channel rules matches them.

David PombarSwiss army knife at Trackingplan

Read more from David, a Senior Product Strategist with 18+ years in digital product development and an atypical error detection knack.

Read next

All Blog →

Trackingplan

See everything. Miss nothing.

Your implementations audited around the clock with real-time, real-user data. Real-time alerts about errors or changes in your data, campaigns, pixels, privacy and consent. Let AI flag issues before they cost you.