What Does (not set) Mean in GA4? The Common Causes and How to Fix Each

What does (not set) mean in GA4? It is a placeholder. Google Analytics shows (not set) when it has not received any information for a dimension [1]. It is not an error message, and it does not mean the same thing everywhere. On landing page it means the session had no page view. In source / medium reports, the session had no session_start event. For city, GA4 could not match the visitor's IP address to a city.

The useful question is which report shows it, and whether that cause can be fixed. This guide goes through each one.

Method note: the examples come from Anobee's own GA4 property for anobee.com, 1 to 28 October 2026, read in the standard reports and through the GA4 Data API on 29 October 2026. Causes and fixes come from Google's Analytics Help pages, checked the same day.

What does (not set) mean in GA4, compared with similar values?

GA4 has four placeholder values that are easy to confuse. Each one means something different.

The key difference is whether you can act on it. For (not set), Google says action is "generally possible". For (data not available), it usually is not [1].

Where (not set) showed up in a real GA4 property

Here is what one ordinary property showed over 28 days. Anobee's GA4 recorded 563 sessions from 421 active users between 1 and 28 October 2026.

The largest (not set) row was the one site owners can do least about. The smallest was the one most worth fixing. That pattern is common, which is why the cause matters more than the size of the row.

Landing page (not set) in GA4

Cause: Google says the landing page dimension shows (not set) when a session does not have a page_view event [1].

In practice, the usual cause is a timeout. By default, a GA4 session ends after 30 minutes of inactivity [3]. If a visitor leaves an article open, comes back an hour later and scrolls or clicks, GA4 starts a new session. That session has a session_start event but no fresh page_view, so it has no landing page.

Anobee's data fits that pattern. The 25 (not set) sessions had 0 new users, so every one came from someone who had visited before. Instead of page views, the events inside them were session_start, user_engagement and a few clicks on FAQ items and scroll events. No page_view appeared in any of them. Only 2 of the 25 counted as engaged sessions.

Fix: usually none is needed. A small, stable share of landing page (not set) is a by-product of how sessions work. Look closer only if:

• the share suddenly grows, which can mean page_view events stopped firing on some templates;
• custom events fire before the Google tag loads. Google warns that events sent before the config command can end up separated from the page view and session start [2].

GA4 also lets you adjust the session timeout in the tag settings [3]. However, a longer timeout changes every session count, so do it only for a real business reason, not to hide a (not set) row.

Source / medium (not set) and Unassigned traffic

Cause: session source / medium reports (not set) when the automatically collected session_start event is missing. Those sessions then appear as Unassigned in the default channel group, because no channel rule matches them [1].

Google lists three common reasons session_start goes missing:

1. The tag fires too late. In Google Tag Manager, the Google tag should use the "Initialization - All pages" trigger [1]. The Google Tag Manager setup guide shows where that trigger is set.
2. Events fire before the tag. Custom events sent before the config command get batched with session_start, and later events cannot be tied back to that session [2].
3. Consent mode is set up incorrectly. Using the default command for later consent changes, instead of the update command, can lose the session_start event [1].

So what does (not set) mean in GA4 when it reaches the channel report? Anobee's 6 Unassigned sessions show two versions of it. The Data API broke down 4 of them for the same dates. Two had a fully (not set) source / medium, the classic missing session_start case. The other two had a source but no medium: openai / (not set) and perplexity / (not set).

The second pattern matters more in 2026. GA4's AI Assistant channel requires the medium "ai-assistant", which Analytics sets automatically when the referrer matches its list of AI assistants [4]. A link tagged with utm_source alone overrides that referrer and leaves the medium empty, so the visit falls into Unassigned instead of AI Assistant. Google's tagging guide makes the same point: traffic from a user-defined source or medium can end up Unassigned when no rule fits it [2].

Fix: set the Google tag to the Initialization trigger, fire custom events only after it, and use consent mode's update command. When you tag links yourself, always include both utm_source and utm_medium. The Google Analytics setup guide covers the base installation.

One case is not a fault. Google says sessions carrying the srsltid parameter can show (not set) when the referrer is not google.com, for example when someone shares a modified Google result URL. GA4 does not count those sessions as organic [1].

City and country (not set)

Cause: GA4 approximates geography dimensions such as city and region from the IP address of the traffic [5]. When GA4 cannot match an IP address to a city, the city is (not set).

For some regions, there is also a second cause. GA4 lets you turn off granular location and device data collection per region. When it is off, Analytics does not collect city, along with details such as device model [6].

City (not set) was the largest row in Anobee's city report: 74 active users, more than any named city. However, the Data API split it by country. China accounted for 31 users with only 2 engaged sessions between them, and Nepal for 28 users with 10 engaged sessions. Country itself was (not set) for just 2 users. In other words, GA4 usually knew the country and could not narrow it to a city.

Fix: none through tagging. Treat city (not set) as "location unknown", and judge low-engagement clusters on their behavior, not their location. If you disabled granular location for a region, the (not set) share for that region is expected.

(not set) in Google Ads and campaign dimensions

If Google Ads dimensions show (not set), Google lists four causes [1]:

• Google Ads and Analytics are not linked.
• Auto-tagging is turned off.
• Another Google Ads account that is not linked to the property is sending traffic with the GCLID parameter.
• Someone tagged destination URLs manually with incomplete or incorrect UTM parameters.

Also, the last cause applies beyond ads. Google notes that badly tagged URLs from social networks, blogs or other sites produce (not set) in the same way [1]. Anobee's campaign name dimension showed (not set) for exactly the sessions that were Unassigned, which is what incomplete tagging looks like.

If you run ads across several networks, the cross-network channel guide explains how GA4 groups those campaigns.

Other dimensions that show (not set)

How to check your own (not set) values

1. Open the report where it appears. Landing page sits under the Landing page report; Unassigned under Traffic acquisition; city under Demographic details.
2. Note the share, not just the count. Google does not publish an acceptable percentage, so compare against your own previous periods.
3. Add a second dimension. For landing page (not set), add session source / medium. For Unassigned, do the same to see whether only the medium or everything is missing.
4. Match the cause to the dimension using the sections above, and fix the tagging causes first.
5. Recheck after a full week, because a tag change only affects new data.

Finally, once you know what does (not set) mean in GA4 for each report, check how engaged those sessions really are. For that, the guide to GA4 engaged sessions explains the metric used in the tables above.