“Not Set” in Google Analytics: Find the Missing Dimension Before Changing Tracking

Identify the dimension and reporting scope

Write down the exact column displaying the placeholder, the property, the report and the date range. A missing session source and a missing first-user source describe different scopes. Comparing them as if they represented the same acquisition moment creates a second reporting problem.

Google’s explanation of missing dimension values identifies several causes. For example, a session without a page-view event can lack a landing page. These are diagnostic starting points, so verify the relevant event flow on your own site.

Keep missing values separate from channel labels

“Unassigned” is a channel-group label used when event data does not match the other channel rules. “Direct” is also a channel classification. Neither label identifies every reason a particular dimension lacks a value.

A source/medium problem can contribute to Unassigned traffic, but relabelling all Unassigned sessions as direct would change the meaning of the report. Keep the original values and investigate the acquisition dimensions underneath them.

Google distinguishes missing values and channel classifications in its attribution reporting documentation. Use the same reporting scope when comparing source, medium and channel results.

A campaign’s Google Ads clicks and GA4 sessions also measure different events. Use our Search Console and Google Analytics comparison for a related explanation of why platform totals require consistent definitions.

Quantify the affected report before fixing it

Choose a dimension and a metric that fit the question. For a landing-page investigation, compare sessions assigned to known landing pages with sessions in the missing-value row over the same period. Preserve the report’s totals and any limits on returned rows.

Suppose a hypothetical report contains 1,000 sessions: 820 assigned to known landing pages and 180 in the “(not set)” row. The missing share is 18%. If those 180 sessions cluster on one date or browser, the next investigation is more specific than a property-wide tracking rebuild.

For GA4 property [ID], investigate landingPage = “(not set)” over [complete period]. Start with a report by landingPage using sessions. Retrieve enough rows to check coverage and keep any incomplete-data warnings. Then examine the missing group by date and deviceCategory in separate supported reports. State the exact filter, timezone and returned totals. Make no configuration changes.

SourcetoMCP supports dimension filters for the reporting fields it exposes. Ask the assistant to inspect the available schema before choosing a filter. A short, unfiltered top-pages response is insufficient to calculate the property’s total missing share.

Investigate Ads-related gaps with the account link and URLs

For Google Ads dimensions, first confirm that the GA4 property is linked to the Ads account responsible for the traffic. The connector can read the configured Google Ads links and the available campaign dimensions.

Then inspect auto-tagging, manual campaign parameters and the resolved destination. Redirects or site code can remove information between the ad click and collection. Privacy-related click identifiers and processing can also affect which dimensions are available. Google documents these checks in its Ads clicks and Analytics sessions troubleshooting guide.

A missing campaign name does not justify replacing all URL tracking at account level. Compare the affected traffic with a working campaign first. Use the tracking-template audit to document the exact settings and overrides before proposing a change.

SourcetoMCP can read configuration and reporting fields, but cannot inspect a live browser redirect or change your Google Tag Manager container. Validate those steps in the website and tag-debugging tools.

Check custom definitions against event collection

If a custom dimension is affected, compare its registered parameter and scope with the tracking plan. Registering a name in Analytics does not make your website start sending the corresponding value.

Use the GA4 custom dimensions guide to inspect the saved definition and plan a fresh event test. The connector can list and manage definitions. Its reporting operations use a fixed field selection, so arbitrary custom dimensions need validation in GA4 reports or explorations.

Avoid creating another definition simply because a report has missing values. Check the property, scope, parameter spelling and whether the value was sent on the event you are analysing. A configuration mismatch and an event that legitimately lacks the parameter require different responses.

Validate the repair using fresh, comparable data

Record the approved change and a test visit that exercises the affected route. Check whether the intended page view, session information or campaign parameters now arrive. Changing collection does not reconstruct information that earlier events never supplied.

Wait for the relevant reporting to process before comparing periods. Start with complete days and preserve the property timezone. A lower missing share after a release is useful evidence, but also examine whether the traffic mix or the report’s filters changed.

Review the missing-value investigation after [change and date]. Compare [complete before period] with [complete after period] using the same property, dimension, metric and filters. Report the missing count, comparable total and missing share for each period. State any traffic-mix changes, processing limits or unresolved cases. Keep observed improvements separate from claims about their cause.

Add the remaining checks to your GA4 audit checklist. Assign a named owner to the specific tag, URL or configuration issue the evidence supports.