GA4 Landing Page Report: How to Find and Fix Your Worst Performers.

Every session starts somewhere. The landing page report tells you where — and more importantly, it tells you which pages are engaging users and which are driving them away. This report is the fastest way to find conversion optimization wins.

Accessing the Report

Finding the GA4 Landing Page Report

Navigate to Reports → Engagement → Landing Page. The report isn't visible in all GA4 properties by default — Google quietly re-added it in July 2023 after removing it at the GA4 launch, and properties created during that window often still don't include it in the default navigation. If you don't see it, you'll need to add it to your report library manually, which takes about 60 seconds.

1. Go to Reports → Library (bottom-left of the Reports section).
2. Find the "Life cycle" or "Engagement" collection.
3. Click Edit Collection.
4. Drag the "Landing page" report card into the collection.
5. Click Save, then Publish so the change rolls out to all viewers of the property.

You need Editor role or higher to publish library changes — Viewer or Analyst roles can only edit for themselves.

Reading and Analyzing the Report

Key Metrics to Add to the Default Report

The out-of-the-box landing page report only shows sessions, users, and new users. That's not enough to diagnose a page's performance. Click the pencil icon in the top-right to customize the report and add these five metrics — they give you the complete picture of entry-point quality in under a minute.

• Engagement rate — % of sessions lasting 10+ seconds, having a conversion event, or 2+ page views. The GA4 equivalent of UA's inverse bounce rate.
• Bounce rate — % of sessions that were NOT engaged (exactly the inverse of engagement rate).
• Key events (conversions) — Which landing pages actually drive the outcomes you care about?
• Average engagement time — How long do people spend here in seconds?
• Views per session — Do visitors explore further or land-and-leave?

How to Read the Report: The 4-Quadrant Framework

Once you've added the right metrics, the fastest way to extract insight is to mentally plot each landing page onto a 2×2 grid: traffic volume (sessions) on one axis, engagement rate on the other. Every page falls into one of four quadrants, and each quadrant demands a different action. Sort by sessions descending first, then scan engagement rate to place each page.

• High traffic + High engagement: Your stars. Protect these pages. Do not redesign what's already working — document it.
• High traffic + Low engagement: Your biggest opportunity. These pages get eyeballs but lose visitors fast. Prioritize for A/B testing or rewriting.
• Low traffic + High engagement: Hidden gems. These convert well but lack visibility. Improve internal linking, write about them, run ads to them.
• Low traffic + Low engagement: Deprioritize. Either fix fundamental issues (speed, mobile layout, misaligned intent) or remove them from the sitemap.

Segmenting Landing Pages by Traffic Source

A single landing page can perform wildly differently depending on where the traffic came from. Organic visitors arrive with high intent; paid social visitors are cheaper to acquire but less patient; email visitors are already warm. An aggregate bounce rate hides these patterns completely. Add a secondary dimension to break the numbers apart and you'll often find one source dragging the average down.

1. Click the + icon next to the "Landing page" dimension column.
2. Select Traffic source → Session source / medium.
3. The table now shows each page split by source (e.g. google/organic, facebook/cpc).
4. Sort by sessions to find your highest-volume page-source combinations.

Typical diagnostic this unlocks: "Our homepage has a 45% bounce rate" becomes "25% from organic, 70% from paid search — the paid landing experience is the problem, not the page itself."

Advanced Analysis

Combining Landing Page with Path Exploration

The Landing Page report tells you the entry point but stops there. To see where users go after they land — and where the biggest drop-offs happen — pair it with a Path Exploration. Path explorations run against the last 30-60 days of event data depending on your retention setting, and they're the single best way to visualize multi-step user flows inside GA4.

1. Open Explore → Path exploration.
2. Click the "Starting point" dropdown and set it to Event name: page_view.
3. Add a filter for your specific landing page URL or a regex pattern.
4. Expand each node to see which pages users visit next and where they exit.
5. Look for unexpected exit pages — these usually flag broken flows or missing CTAs.

Common Landing Page Problems and How to Fix Them

Most landing page issues fall into four repeating patterns. Recognizing them on sight saves hours of diagnosis — we see these daily across the NiceLookingData audit pipeline, and the fix for each is usually well-defined even when the root cause isn't immediately obvious in the data.

• High bounce, fast exit (< 3s average engagement): Page loads slowly, doesn't match ad copy, or has a confusing above-the-fold experience. Check Core Web Vitals first.
• Good engagement, no conversions: Strong content but weak or missing CTA. Add one clear next step above the fold.
• Mobile bounce much higher than desktop: The page isn't mobile-optimized. Check font sizes (≥16px), button tap targets (≥44×44px), and layout shifts.
• "(not set)" appearing as the landing page: Usually caused by cross-domain tracking gaps or sessions starting with a non-page_view event (e.g. a file_download fired first).

Frequently Asked Questions

What is the GA4 landing page report?

The GA4 landing page report shows you which pages users first arrive on when they start a session on your site. It displays each entry URL alongside session volume, new users, engagement rate, bounce rate, and key event counts. Unlike the page path report, which shows all pages visited, the landing page report is limited to the first page of each session — making it the right tool for evaluating campaign performance, SEO entry points, and top-of-funnel conversion efficiency.

How do I find the landing page report in GA4?

Navigate to Reports → Engagement → Landing Page. If the report isn't in your navigation, it needs to be added to the report library. Go to Reports → Library, find the Engagement collection, click Edit Collection, drag the Landing Page report card in, and publish the change. This takes about 60 seconds. You need Editor access or higher to publish library changes — Viewer and Analyst roles can add the report for their own view but cannot publish it to all property users.

Why does GA4 show (not set) for landing pages?

The (not set) value in the landing page dimension appears when GA4 cannot determine which page started a session. The two most common causes are cross-domain tracking gaps, where a session begins on a subdomain or partner domain that isn't configured in the cross-domain measurement settings, and sessions that start with a non-page_view event — for instance, when a file download event or custom event fires before the page_view tag has triggered. Less common causes include server-side events sent without a page location parameter and sessions created programmatically through the Measurement Protocol without page context.

What is the difference between landing page and page path in GA4?

The landing page dimension captures only the first page of a session — the URL where the user entered your site. The page path dimension captures every page viewed during a session, including pages visited after the initial entry point. In reports, landing page is used to evaluate how well entry points attract and engage visitors, while page path is used to understand on-site navigation and content performance across the full visit. A page can appear in both reports: it might receive a large volume of session entries (landing page) while also being a common mid-session destination (page path).

How do I add custom dimensions to the GA4 landing page report?

You can add secondary dimensions to the landing page report by clicking the + icon next to the dimension column header in the report table. This lets you break down each landing page by attributes like session source, device category, country, or any custom dimension you've registered in your GA4 property. For custom dimensions specifically, they must first be created in Admin → Custom Definitions, and the dimension must be scoped correctly (session-scoped dimensions work well alongside the landing page dimension). For deeper custom dimension analysis, the Exploration reports give you more flexibility to combine dimensions and apply filters simultaneously.

Does GA4 track landing pages for all traffic sources?

Yes, the landing page report includes sessions from all traffic sources by default — organic search, paid ads, direct, email, referral, and social. However, a few scenarios cause landing page attribution to break down. If cross-domain tracking is not configured and a user lands on a subdomain first, the actual first page may not be recorded. If a redirect chain strips UTM parameters before the page loads, the session may be attributed to (direct) rather than the correct source. And if a page uses a JavaScript-based redirect on load, the page_view tag may fire before the redirect completes, recording the wrong URL as the landing page.

How do I create a GA4 landing page report in Looker Studio?

Connect Looker Studio to your GA4 property using the native Google Analytics data source connector. Add a table chart and set the dimension to "Landing page + query string" (the full URL including parameters). Add metrics for Sessions, Engaged sessions, Engagement rate, Key events, and Average session duration. To segment by source, add "Session source / medium" as a secondary dimension or use a filter control. For comparison views, add a date range control and a segment picker. One common issue: Looker Studio caches GA4 data and may show results from the previous day — use a custom date range that excludes today if you want clean, fully-processed data.

Why are some landing pages missing from my GA4 report?

Pages can be missing from the landing page report for several reasons. GA4 applies data thresholds in some reports, which means rows with very low session counts may be aggregated into an "other" category or omitted entirely — this is more common in properties with the "Blended" data quality setting. Pages accessed only by authenticated users via server-side sessions without a browser page_view event won't appear. Pages that only appear as mid-session destinations (never first in a session) will not show up. And if your date range is short or your filters are narrow, lower-traffic pages may simply fall below the visible rows — increase the rows-per-page limit or export the full table to see the complete picture.