GA4 Landing Page Shows (not set): The Documented Cause and the Fix

You open the landing page report in GA4, and a large share of your sessions are attributed to a page called (not set). It is not a bug and it is not missing data exactly. It means GA4 could not work out where that session began.

Google documents the cause for this specific dimension in one line: a session does not have a page_view event. Everything below follows from that.

Why a session would have no page view

A session is opened by a session_start event. The landing page is worked out from the first page_view in that session. If a session begins with something that is not a page view, there is nothing to name as the landing page.

• The tag fires on some pages and not others. A page without the tag can start a session through an event while never recording a page view.

• The first interaction is an event rather than a page load. Sessions starting on a page kept open from a previous visit are a common version of this.

• Consent handling drops the opening event. Google names this directly: an incorrect default consent command can lose the initial event carrying session_start.

• A tag manager trigger is configured so session_start fires without an accompanying page view. Google names this as a cause for session source and medium, and the same misconfiguration produces the landing page version.

Two causes that are not this, and get blamed anyway

• Recent data. Custom parameters can read (not set) within the first twenty four hours after registration, so a value that is missing this morning may simply not be processed yet. Wait a day before investigating.

• Traffic that has no landing page to report. Some traffic genuinely does not enter through a page you control.

How to confirm it is your cause

1. In the realtime report, load a page of your site in a private browser window and watch for both session_start and page_view. If session_start appears without page_view, you have found it.

2. Compare the count of page_view events with the count of sessions over the same period. A large gap points the same way.

3. Check whether the (not set) sessions cluster on one traffic source or one device type. A cluster usually means a tagging gap on a specific path rather than something site-wide.

4. Check the tag is present on every page. The reliable way is to look at the pages report for pages receiving no views at all despite being live.

The fix

1. Make sure the base tag is on every page of the site, including any built outside your main template. Landing pages made in separate tools are the usual offender.

2. In Tag Manager, make sure the configuration tag fires on a page view trigger rather than on something narrower.

3. If you use consent management, check the default consent state is set before any tag fires, so the opening event is not lost.

4. Then wait. Changes here affect new sessions only. The historic (not set) rows will not be repaired retrospectively.

That last point matters and it is where people give up. Nothing you do today improves last month's data. It stops the gap growing from now on, which is the only outcome available.

Is it worth fixing?

Yes, and the reason is not tidiness. The landing page report is how you find out which pages bring people in. If a large share of sessions cannot be attributed to a page, you cannot tell which of your work is producing anything, and every decision made from that report is made on a sample that excludes an unknown group.

If you want someone to look at whether your measurement is telling you the truth before you act on it, book a free SEO consultation. You will speak to the person who does the work.

Written by Spencer Capron at Capron Media, in collaboration with our AI agents. The same way we do the work for clients. Spencer reviews everything published here.