GA4 Landing Page (not set): Why It Happens and How to Fix It
Updated: Nov 7
By Spencer Capron, founder of Capron Media. Updated October 30, 2026.
If the Landing page report in GA4 shows a row called (not set), GA4 could not tell which page some sessions started on. It is not a bug, and each cause below has a fix or a check for new data. This guide covers why it happens, how to find your cause, how to fix it, and what you cannot fix.
What does (not set) mean in the GA4 landing page report?
In the GA4 landing page report, (not set) means a session had no page_view event, so GA4 had no page to name as where it started. Google describes (not set) as a placeholder it uses when it has received no information for a dimension. For landing page, the missing information is the page view.
Google's help page puts the landing page case in one line: "(not set) can appear for the landing page dimension when a session doesn't have a page_view event."
Why would a session have no page view?
A GA4 session can start without a page view when the first thing GA4 records is some other event. That happens after a session times out on an open tab, when events fire before the Google tag's setup, when consent settings drop the opening event, or when a page has no tag at all.
Cause | What happens | How to spot it | Source |
Session timeout | A visitor leaves a tab open past the timeout, comes back and clicks or scrolls without reloading. A new session starts with no page view | (not set) rows with sessions but almost no new users | Google: sessions time out after 30 minutes of inactivity by default. Root and Branch describes this case |
Events fire before the tag's setup | Custom events sent before the Google tag's config command are batched with session_start, and the later page view is not tied to that session | The tag fires late in Tag Manager, or custom events load first | Google's tagging best practices |
Consent settings | Using the consent "default" command for values that should use "update" can lose the opening event | (not set) rose when a consent banner was added or changed | Google's (not set) help page |
Pages with no tag | A page outside your main template starts a session through an event but records no page view | A live page that gets visits elsewhere but no views in GA4 | Our reading of Google's landing page rule |
Data still processing | Recent data can change while GA4 processes it | (not set) in the last day or two only | Google: processing can take 24 to 48 hours |
From Capron Media: the free Lite subscription

Your visits and clicks, beside your rankings
Connect Analytics and Search Console yourself, when ready, and see your own visits and clicks too. Lite does not include the work on your site. Starter does.
How do you find which cause is yours?
To find your cause, watch a fresh visit in GA4's Realtime report, compare page views with sessions, and look at where the (not set) sessions come from. If session_start arrives without page_view, or (not set) clusters on one source or device, you have narrowed it to a tagging gap on that path.
Watch a visit as it happens. Open your site in a private browser window, then open GA4's Realtime report and look at "Event count by event name". You should see session_start and page_view together.
Compare page views with sessions. Over the same dates, far fewer page_view events than sessions points to sessions starting without a page view.
Add a second dimension. In the Landing page report, add "Session source / medium" or device category. If (not set) clusters on one source or device, look at the tag on that path.
Look for pages with no views. A page that is live and linked but shows no views at all may be missing the tag.
Check the dates. If (not set) appears only in the last day or two, wait for processing to finish before acting.
How do you fix (not set) landing pages in GA4?
Fix (not set) landing pages by making the Google tag load first on every page, setting consent with the default and update commands as Google describes, and lengthening the session timeout if visitors keep tabs open. A tag change cannot add a page view GA4 never received, so last month's (not set) rows stay as they are.
Put the tag on every page. Include pages built outside your main template, such as landing pages made in a separate tool.
Make the tag fire first. In Tag Manager, fire the Google tag on the "Initialization - All Pages" trigger, so its setup runs before custom events. Google gives this trigger as the fix for (not set) session source and medium.
Set consent the way Google describes. Use the "default" command for the starting state, and the "update" command after the visitor answers your banner.
Lengthen the session timeout if it fits your site. In GA4, the Google tag settings let you adjust the session timeout from its 30-minute default.
Then wait. Check the Realtime report again, and compare the next week with the last.
Can you fix old (not set) data?
Not by changing your tags. A tag change cannot add a page view GA4 never received, so the (not set) rows already in your reports stay. Analytics Mania, a GA4 practitioner's guide, says the same: a fix "will only affect data collected from this point forward." Judge the fix on the weeks after it, not the weeks before.
Can you hide (not set) from the landing page report?
You can filter (not set) out of the Landing page report, but that hides the problem rather than fixing it. Google's help shows how to apply a filter to a report. Use it to read the pages you can see, and keep an unfiltered copy so you know how many sessions are still missing a landing page.
Is (not set) worth fixing?
Yes, if the share is large. The landing page report is how you find out which pages bring people in. When many sessions have no landing page, you cannot tell which pages are working, and every decision made from that report rests on the sessions GA4 could place.
To see which reports show how visitors arrived in the first place, read which reports show how traffic arrived at a website. To see what people do after they land, read how behavior flow charts show where visitors go.
If you want your own site's numbers in one place, start a free Lite subscription and connect Analytics and Search Console when you are ready. If you would rather talk first, book a free call about your site.
From Capron Media: the free Lite subscription

See your numbers without connecting a thing
See real, estimated numbers about your site before you connect anything. Lite does not include the work on your site. Starter does.
Written by Spencer Capron, founder of Capron Media, a Middleborough, Massachusetts SEO service for small business owners. Spencer is HubSpot SEO II certified, holds CompTIA Security+, and has run recurring SEO programs for 30+ small-business clients. He wrote this post in collaboration with our AI agents, and he reviews everything published here.





Comments