What Is "(not set)" in GA4? Causes and How to Fix It

When you look at reports in GA4 (Google Analytics 4), you may see “(not set)” appear as a dimension value. This is a placeholder indicating that Analytics could not determine the value—due to missing data, a timing gap in measurement, and similar causes. This article clearly explains the main reasons GA4 displays “(not set)” and how to address it for each dimension.

What “(not set)” means in GA4

“(not set)” is a label showing that GA4 did not receive a value for that dimension, or has not yet been able to determine one. It is not an error itself—think of it as a label meaning “the data is empty.” The (not set) value in Analytics does not arise from a single cause; the reason differs by dimension. That is why the first step is to identify which report and which dimension it appears in.

The difference between “(not set),” “(none),” and “(other)”

Two easily confused labels are “(none)” and “(other).” (none) is mainly used in source/medium and indicates that no value exists (for example, the medium for direct traffic). (other) represents a row that was aggregated together because the cardinality (number of distinct values) was too high. (not set), by contrast, refers to a case where data did not arrive, or could not be determined, where a value should have been.

Common causes of “(not set)”

There are several typical reasons Analytics displays not set.

1. A missing tag implementation or a timing gap in firing means the required parameters are not being sent
2. In some dimensions such as landing page, the value at session start has not yet been determined
3. The Google Ads integration (auto-tagging / gclid) is not set up correctly
4. A custom dimension’s scope setting or registration error means the value is not linked
5. A temporary undetermined state caused by data processing, or the lag before data is reflected
6. Referrer information is missing, so the source/medium cannot be identified

How to address it by dimension

When (not set) appears in source/medium

The main causes are missing UTM parameters or a flaw in Google Ads auto-tagging (gclid). Review the parameter settings on your ad links and confirm that the account link between GA4 and Google Ads is active.

When (not set) appears in landing page

This field is prone to causes such as page information not being determined at session start, or a timing gap in event measurement. Confirm that the tag (the GA4 configuration tag) fires correctly on every page and that page_location is being sent.

When (not set) appears in a custom dimension

Typical examples are a scope (event/user) misconfiguration or a parameter-name mismatch. Cross-check that the parameter name you are sending matches the custom dimension definition registered in the admin settings.

A checklist for reducing “(not set)”

• Does the GA4 tag fire correctly on every page (verify with GTM preview, etc.)?
• Are UTM parameters applied to ad links without omissions?
• Is the GA4–Google Ads integration and auto-tagging active?
• Do the custom dimension’s scope and name match the sending side?
• Are you judging based on the last 48 hours without accounting for data processing lag?

“(not set)” is not always a problem

A small amount of (not set) can occur even from hard-to-avoid factors such as measurement lag or missing referrers. If the proportion is very small, there is no need to address it anxiously. On the other hand, a high proportion in a specific dimension is a sign that there is room to improve your tag implementation or integration settings. First check which dimension is affected and at what proportion, then prioritize the ones with the largest impact.

Conclusion

GA4’s “(not set)” is a placeholder indicating a value could not be determined, and the cause differs by dimension. The fastest path to a solution is to isolate where it occurs—source/medium, landing page, custom dimensions, and so on—and then review your tag implementation, UTMs, integration settings, and scope definitions in turn. Tolerate the small-proportion cases while improving the areas with the biggest impact first.