Post title

Do you see (not set) in your Google Analytics 4 reports? This value appears when GA4 has not received the data needed to assign information to a specific dimension. However, it does not always indicate a configuration error - the cause depends on where it appears and how the data is collected. Learn where (not set) comes from in GA4, how to identify the source of the problem, and when you need to make changes to your configuration.

What does (not set) mean in GA4?

The (not set) value in Google Analytics 4 is a placeholder that appears when GA4 has not received the data needed to assign a value to a specific dimension. It can appear for dimensions such as session source and medium, landing page, campaign, content group, or custom parameters.

The presence of (not set) alone does not point to one specific cause. Its meaning depends on the report and dimension where it appears. In one case, the problem may be caused by a missing session_start event, while in another it may result from incomplete campaign tagging, incorrect Consent Mode configuration, or missing data for a specific parameter.

It is also important to distinguish (not set) from (data not available). With (not set), it is often possible to identify the source of the problem and correct the configuration. By contrast, (data not available) usually results from limitations in data availability or processing and cannot always be eliminated through changes to the GA4 configuration.

Why does (not set) appear in GA4 reports?

The reason (not set) appears depends primarily on the dimension for which the value is missing. This is why you should start your diagnosis by checking exactly where the problem occurs - different mechanisms are responsible for (not set) in session source and medium than in Google Ads data, landing pages, or custom parameters.

(not set) in session source and medium

The (not set) value may appear in the session source/medium dimension when the automatically collected session_start event is missing from a session. GA4 uses information associated with the start of a session to determine its source and medium. If this data is missing, the system cannot correctly assign a value to this dimension, and the traffic may be classified under the Unassigned default channel group.

One possible cause is the way the Google tag is triggered. If GA4 is implemented through Google Tag Manager, check whether the tag fires early enough and whether session_start is recorded correctly.

Problems with identifying the traffic source may also be related to manual campaign tagging. Incomplete or incorrect UTM parameters can prevent GA4 from receiving the information needed to correctly determine where the traffic came from. Therefore, the presence of (not set) in the source or medium does not automatically mean there is an issue with UTM parameters - the cause should be investigated in the context of how sessions and traffic acquisition are tracked as a whole.

(not set) in Google Ads and campaign data

If (not set) appears in dimensions related to Google Ads, the cause may lie in the GA4 configuration, the advertising account settings, or the way campaigns are tagged. The issue can occur when the Google Ads account has not been linked to the correct GA4 property or when auto-tagging is disabled.

You should also check whether traffic comes from other Google Ads accounts advertising the same website that have not been linked to the GA4 property. In this case, Analytics may receive a click identifier but be unable to attribute the data to the correct account and campaign.

Manually tagged URLs can also be a source of (not set). If the UTM parameters used are incomplete or incorrect, GA4 may not receive the information needed to correctly identify the campaign and traffic source.

(not set) for landing pages

For the landing page dimension, (not set) may appear when no page_view event has been recorded during a session. In this case, GA4 does not receive the information needed to determine which page the session started on.

If the proportion of (not set) for this dimension is unusually high, check how page views are tracked and verify that page_view is being sent correctly across all areas of the website included in the measurement setup.

(not set) for events and custom parameters

For events, (not set) may appear when GA4 does not receive the parameter value required for the dimension being analyzed. When diagnosing the issue, check not only whether the event itself was recorded, but also which parameters were sent with it and whether they contain the expected values.

A specific case involves the session_start and first_visit events. For these events, GA4 retains parameters from the first collected event. If the expected parameter was not available in that event, its value may appear as (not set). For newly registered custom parameters, keep in mind that (not set) may also appear in reports during the first 24 hours after they are created.

A similar mechanism can occur with content groups. The (not set) value may appear when the content_group parameter is sent without a value or when the content group dimension is combined with an automatically collected event that does not accept this parameter.

(not set) and Consent Mode

Using Consent Mode itself does not cause (not set) to appear. However, implementation errors can result in GA4 missing the data it needs to correctly describe a session.

One such case is the incorrect use of the default and update commands. The default command is used to set the initial consent state, while after the user interacts with the consent banner, the consent status should be updated using update. An incorrect implementation may prevent the user_engagement event from being sent and cause the initial event containing session_start to be lost.

The issue can also occur when additional events with denied consent are sent after consent was initially granted. GA4 may treat them as a separate session without session_start, which can consequently lead to (not set) appearing in session-related data.

How to identify the cause of (not set) in GA4?

Before making any changes to your configuration, determine where and under what circumstances (not set) appears. The cause depends on the dimension and the way data is collected, so as part of your diagnosis:

How to fix (not set) in Google Analytics 4?

The way to resolve (not set) depends on the dimension affected and the cause identified during diagnosis. Once you have identified the source of the problem, implement the appropriate fix, for example:

Keep in mind that configuration fixes affect data collected after the changes are implemented - they do not automatically correct historical data. Once the issue has been resolved, monitor your reports to check whether the proportion of (not set) in newly collected data actually decreases.

How can you reduce the risk of (not set) appearing in the future?

Not every case of (not set) can be avoided, but maintaining your GA4 configuration correctly can reduce the risk of issues caused by implementation errors. The most important practices include:

A periodic Google Analytics 4 audit is a useful addition to these practices. Conducting a GA4 audit step by step allows you to verify individual elements of the configuration and identify issues that may affect the quality of the data being collected.

GA4 (not set) FAQ

The (not set) value can appear in different Google Analytics 4 reports, and its cause depends on the specific dimension and how measurement is configured. Below, you will find answers to the most frequently asked questions about why it appears and how to diagnose it.

What does (not set) mean in Google Analytics 4?

(not set) is a placeholder displayed by Google Analytics 4 when the system has not received data for a particular dimension. Its presence does not automatically indicate a specific error - the cause should be determined based on the report, dimension, and context in which it appears.

Why does session source/medium show (not set)?

The (not set) value may appear for session source/medium when the automatically collected session_start event is missing from the session. This may be caused by the way the Google tag is triggered. Problems with traffic source attribution can also result from incomplete or incorrect manual URL tagging.

Does (not set) mean there is a GA4 configuration error?

No. (not set) does not always indicate a Google Analytics 4 configuration error. In some cases, it results from the way dimensions and events are combined, missing data for a particular dimension, or the way GA4 processes information. Before making any changes, you should first identify the cause and determine the scale of the issue.

Can incorrect UTM parameters cause (not set)?

Yes. Incomplete or incorrect UTM parameters can prevent GA4 from receiving the information needed to correctly attribute data from a manually tagged URL. In this case, you should first check that the UTM parameters you use are complete and correct.

Can Consent Mode cause (not set)?

Errors in the Consent Mode implementation can cause (not set) to appear in GA4. This can result from incorrect use of the default and update commands or situations where consent handling causes the session_start event to be lost. However, this does not mean that every instance of (not set) is related to a lack of user consent.

Can you remove (not set) from historical GA4 data?

No. You cannot correct data already stored in standard GA4 reports by changing the configuration later. Fixing the cause of (not set) will primarily affect data collected after the change, so you should monitor subsequent reports to check whether the proportion of this value decreases.