Landing & exit pages
Landing & exit pages in the Marketing area (Acquisition) — route /marketing/landing-pages.
Landing & exit pages lives in the Marketing area of the dashboard, under Acquisition.
At a glance#
| Dashboard route | /marketing/landing-pages |
| Area | Marketing (marketing) |
| Group | Acquisition |
| Platforms | Web apps only. Hidden for mobile apps. |
What it does#
Landing and exit pages, derived from the pageview data the web SDK already captures — no extra instrumentation.
Entry page — the first pageview of a session.
Exit page — the last.
Bounce — a session with a single pageview.
Engagement — from the page-leave signal.
The landing table also carries an acquisition dimension: each session's stored referrer and UTM signals are re-classified through your channel grouping rules, so a page can be filtered to one channel and read for its organic share, its sending search engine, and its conversions.
When to use it#
To find out which pages start valuable sessions and which end them. Entry-page data tells you where your audience actually arrives, which for most sites is not the homepage — and the pages that receive the most first impressions are usually the least deliberately designed.
The channel filter is what makes it genuinely useful: the same landing page performs differently for organic and paid traffic, and averaging them hides both.
Workflow#
Sort entry pages by volume
Your highest-traffic entry point deserves the most attention and rarely gets it.
Filter to one channel before judging a page
A page with a poor overall bounce rate may be excellent for organic and terrible for one paid campaign.
Read exit pages for the leaks
A high exit rate is expected on a confirmation page and alarming mid-funnel.
Pair with campaign landing performance
Campaign landing adds vitals and revenue per campaign × page, which is where paid traffic problems surface.
Permissions and prerequisites#
Web apps only. Requires pageview and page-leave reporting, both of which the web SDK does by default.
Limits and edge cases#
Bounce is a single-pageview session, which on a single-page application means something different than on a multi-page site — a rich SPA visit can be one pageview.
Engagement depends on the page-leave signal, which a hard tab close may not deliver.
Re-classification follows current rules. Editing your channel grouping changes this report's history.
Troubleshooting#
Bounce rate near 100%. Likely an SPA reporting one pageview per visit. Check whether route changes are reported as pageviews.
A page has entries and no conversions. Either it genuinely does not convert, or conversion events are not attributed — check Revenue attribution.
Where the data comes from#
Derived from pageview and page-leave data the web SDK already captures. The landing table carries the acquisition dimension; the exit-page panel does not.
From the SDK
Served by
Analytics