> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/debugging-monitoring/how-do-i-solve-not-set-landing-pages-in-ga4.md).

# How do I solve '(not set)' landing pages in GA4?

A '(not set)' landing page in GA4 is a session that started without a page\_view.

A '(not set)' landing page in GA4 is a session that started without a page\_view. Most of them appear when a visitor leaves a tab open, the session expires, and an automatic Google event such as 'user\_engagement' starts a new session hours later. You can stop these sessions from reaching GA4 with one exception trigger in your server-side GTM (sGTM) container.

### What the landing page report shows <a href="#what-the-landing-page-report-shows" id="what-the-landing-page-report-shows"></a>

The landing page report (Reports > Engagement > Landing page) lists the first page of every session. Next to each page you see sessions, users, engagement, key events and revenue. You use it to judge which pages bring visitors in and how well they perform.

Every session has exactly one landing page. When GA4 cannot assign one, the session is grouped under the row '(not set)'.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FtbwDj08V59snNDDYLffN%2Fimage.png?alt=media&amp;token=4dc9fc88-438a-4f52-9793-6b1ed9f2d3bf" alt=""><figcaption></figcaption></figure>

### How GA4 determines the landing page&#x20;

GA4 fixes the landing page once, at the session\_start event. That event is generated from the first hit of a new session. If part of the events from that first hit is a page\_view, its page becomes the landing page.&#x20;

If the first hit is another event, such as user\_engagement or scroll, the session gets a session\_start but no first page view. The landing page then stays '(not set)'.&#x20;

That hit still carries the URL of the page it was sent from. This is why you can find sessions in an exploration with landing page '(not set)' next to a page path that is perfectly known.

### Investigate with a user explorer exploration <a href="#investigate-with-a-user-explorer-exploration" id="investigate-with-a-user-explorer-exploration"></a>

To see where these sessions come from, look at the full timeline of the visitors who have them.

1. In GA4, go to Explore and start a new exploration with the User explorer technique.
2. Within this User explorer, create a user segment with the condition: Landing page + query string exactly matches '(not set)'.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FFx55u03z8qN6q1oHhPSi%2Fimage.png?alt=media&amp;token=84248374-39d3-4280-bece-fec283c68d5a" alt=""><figcaption></figcaption></figure>

3. Apply the segment and pick a recent date range, for example the last 7 days.
4. Open a few users from the list to see their event timeline.

### What these sessions look like <a href="#what-these-sessions-look-like" id="what-these-sessions-look-like"></a>

The typical pattern is a normal visit, followed hours later by a lone 'session\_start' without any page view. A real example from one user's timeline:

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FzVsulwVC8bnoptv14PKk%2Fimage.png?alt=media&amp;token=0d6c60aa-6353-47dd-81eb-4e4ab01637c2" alt=""><figcaption></figcaption></figure>

The second session has 0 seconds of engagement, no conversions and is not counted as engaged. The event that started it is often not shown next to it in the timeline, which makes the session\_start look like it came out of nowhere.

### Where these session\_start events come from <a href="#where-these-sessions-come-from" id="where-these-sessions-come-from"></a>

These are real visitors, but not real visits. GA4 ends a session after 30 minutes without activity, while a browser tab can stay open for hours or days. Typical situations:

* A visitor opens a product page, switches to another tab or app, and closes the forgotten tab hours later.
* A visitor closes their mobile browser with a shop tab still open in the background.
* A visitor returns to a tab that stayed open and scrolls, without loading a new page.

Single page applications (SPAs) are hit harder. Navigation there does not reload the page, so tabs live longer and a returning visitor often triggers no new page view.

### The cause: the \_ss flag on Google's own events <a href="#the-cause-the-ss-flag-on-googles-own-events" id="the-cause-the-ss-flag-on-googles-own-events"></a>

The Google tag (gtag.js) keeps track of the session itself, in the `_ga_<ID>` cookie. Every hit carries the session ID (`sid`), the session number (`sct`) and the engaged flag (`seg`). The first hit of a new session also gets the session start flag `_ss=1`.

GA4 turns that flag into the 'session\_start' event. It does this for any event that carries the flag, not only for page views.

The Google tag also sends events on its own, without any tag or trigger in your GTM container. The most important one here is 'user\_engagement', which is sent when a page goes to the background or is closed, to report engagement time. If the session expired in the meantime, that hit is the first of a new session and gets `_ss=1`.

Such a hit looks like this in the request to GA4:

```
en=user_engagement&sid=<new session id>&sct=2&seg=0&_ss=1
```

It starts a session (`_ss=1`), is not engaged (`seg=0`) and carries no engagement time (`_et` is missing). In data we analysed for one webshop, about 2,400 sessions per week started this way, and 97% of them never received another hit.

You cannot block these hits in the web container, because Google sends them itself. In a server-side container you decide what is forwarded to GA4, so that is where you fix it.

### The solution: an exception trigger in your sGTM container <a href="#the-solution-an-exception-trigger-in-your-sgtm-container" id="the-solution-an-exception-trigger-in-your-sgtm-container"></a>

You add one trigger that recognises these hits and use it as an exception on your GA4 tag. The GA4 client in sGTM stores the `_ss` flag as `x-ga-system_properties.ss` and the engagement time `_et` as `engagement_time_msec` in the event data.

1. In your server container, go to Variables > User-Defined Variables > New and choose Event Data. Name it `ED - session start`, with key path `x-ga-system_properties.ss`.
2. Create a second Event Data variable named `ED - engagement time`, with key path `engagement_time_msec`.
3. Go to Triggers > New and choose Custom. Name it `Block - GA4 session start without engagement` and set it to fire on Some events, with these three conditions:
   * Event Name equals `user_engagement`
   * `ED - session start` equals `1`
   * `ED - engagement time` equals `undefined`

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FUCWxJWbSumBG9H0acIX9%2Fimage.png?alt=media&amp;token=f2438d10-4fdb-4733-8ede-e1069012b3ed" alt=""><figcaption></figcaption></figure>

4. Open your GA4 tag, go to Triggering, choose Add exception and select this trigger. Repeat this for every GA4 tag in the container.
5. Save, check in Preview mode that normal 'user\_engagement' hits still fire the GA4 tag, then submit and publish.

Normal 'user\_engagement' hits are not affected. They either carry engagement time or are not the start of a session.

### Check the result and the trade-offs <a href="#check-the-result-and-the-trade-offs" id="check-the-result-and-the-trade-offs"></a>

After a week, compare the '(not set)' row in the landing page report with the week before. The number of sessions should drop, and the remaining '(not set)' sessions should show real activity in the user explorer.

Keep two things in mind:

* A small share of these sessions does receive more hits later (about 3% in the data above). Those later hits reach GA4 without a 'session\_start'.
* Visitors who return to an open tab and scroll still start a session without a page view. If you want those to get a landing page, the web container can send a 'page\_view' when a tab returns after more than 30 minutes in the background. That needs no change to the website itself.

This is standard GA4 behaviour and happens just the same without server-side tagging. A server-side container is simply the place where you can filter it out.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/faq/debugging-monitoring/how-do-i-solve-not-set-landing-pages-in-ga4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
