Reading Entry Page vs Landing Page in GA4 and Adobe

What is the difference between an entry page and a landing page?

Confusion over entry page vs landing page comes from one word doing two jobs: an entry page is a fact about a session, and a landing page is a decision about a page. The entry page is whichever page a session happened to begin on, discovered after the fact by the analytics tool. A landing page is a page someone designed to be arrived at cold, with its own headline, its own offer and usually its own campaign behind it.

Those two sets overlap, and neither contains the other. A campaign landing page that nobody has clicked yet is a landing page with no entries at all. A support article written for logged-in customers becomes an entry page the moment one search result sends a stranger to it. The analytics tools pick one of the two words, apply it to the session-level fact, and leave you to remember which meaning is on screen.

How does GA4 define and compute the landing page?

Google Analytics 4 has no entry page dimension. It has Landing page, and Google's dimensions reference defines it as "the page path associated with the first page view in a session." The variant Landing page + query string is "the page path and query string associated with the first page view in a session." The Data API exposes the same pair as landingPage and landingPagePlusQueryString with matching descriptions.

Read the definition closely and three consequences fall out.

The unit is the session, not the visitor and not the campaign. Change what ends a session and you change which page is the landing page, which is why session timeout rules move landing page reports without anyone touching the site.

The trigger is the first page_view event specifically, not the first event of any kind. A session that opens with session_start and a custom event but no page_view has no landing page to report, which is one of the routes to (not set) in GA4.

The default dimension drops the query string. Landing page reports /pricing for every arrival regardless of the utm_source attached, and only Landing page + query string separates a paid arrival from an organic one at the same path. Teams that report on Landing page and tag campaigns with UTMs are looking at a dimension that has thrown the tagging away.

How does Adobe Analytics define and compute the entry page?

Adobe takes the other word and a different mechanism. Its documentation describes the family directly: "Entry dimensions are visit-based. They record the first dimension item, and persist it for the entire duration of that visit." Adobe names two in this family, Entry page and Entry page original, and the second one has a much longer memory, preserving "the very first entry page for the entire life of that visitor's cookie" rather than resetting at each visit.

Adobe also says these dimensions cost nothing to turn on: "No implementation changes are required for entry dimensions if your traffic variables contain data." The entry page is derived from the page traffic variable you already populate, which matters because that variable normally holds a page name rather than a URL. Two URLs that share a page name collapse into one entry page row in Adobe and stay separate in GA4.

The persistence clause is the real difference. Because the entry page value rides along on every hit in the visit, any metric collected later in that visit can be broken down by where the visit started. Revenue on hit forty is attributable to the entry page without a join. GA4's session-scoped dimension reaches the same conclusion for session-scoped metrics but does not stamp the value onto each event row.

Which metric pairs with each dimension?

Adobe supplies a dedicated metric, and GA4 does not. Adobe defines Entries as "the number of times a given dimension item is captured as the first value in a visit," and the metric generalises past pages: any dimension has entries, so you can ask which campaign, which search keyword or which referring domain was first in the visit. GA4 has no entries metric and no entrances metric; you count Sessions against the Landing page dimension and the session count does the job.

Why can the same URL be one and not the other?

The same URL is an entry page only for the sessions that started on it, and it is a landing page for all of them or none of them. Four situations make that gap visible in a report.

A designed landing page reached second. A visitor clicks a display ad to /, browses, then reaches /offer/spring from the nav. /offer/spring is a landing page by construction and contributed zero entries to that session. In GA4 the session's Landing page is /.

An accidental entry page. An old blog post ranks, and a stranger arrives there from search. It was never designed as a landing page, it has no offer and no form, and it is now the entry page for thousands of sessions. What to do about that is the subject of how to analyse a landing page.

A session that split. One person reads for ten minutes, takes a call, comes back forty minutes later and clicks through to /pricing. GA4's thirty minute inactivity rule has already closed session one and opened session two, so /pricing is now a landing page in the report despite being the middle of one human visit. The mechanics are in what counts as a session.

A page reached through a redirect. If /promo 302s to /offer/spring, the first page_view fires on the destination. The entry page is the destination, the URL you bought traffic to never appears, and the campaign report loses the mapping unless the query string survives the redirect.

What does this change about how you read the report?

Treat every entry page row as a question about acquisition, and every landing page row as a question about design. They are different questions and the same table answers both badly if you do not say which one you are asking.

Entry-page questions are about supply. Which pages are receiving strangers, in what volume, from where? Any page in that list with meaningful volume needs to work for a cold visitor whether or not you intended it to, and a high exit rate there means something different than a high exit rate mid-journey, as bounce rate versus exit rate sets out.

Landing-page questions are about conversion of intended traffic. Did the page built for this campaign do its job? That question needs the query string in the dimension, because a page that converts at 9 percent from email and 1 percent from paid social is two different results hiding behind one path. Switch to Landing page + query string in GA4, or make sure the Adobe page variable keeps campaign context, before comparing anything.

Frequently asked questions

Does GA4 have an entry page dimension?

No. Google Analytics 4 ships Landing page and Landing page + query string and nothing named entry page or entrances. The Landing page dimension is computed the way an entry page is computed, from "the first page view in a session," so the concept is present under Google's chosen name.

Why does GA4 show (not set) for a landing page?

Because the dimension needs a page_view event and the session did not produce one before it was assembled. A session that starts with a custom event, or whose first page_view is lost to consent or a blocked request, has a session_start with no page path to attribute.

Can the same URL be both an entry page and a mid-journey page?

Yes, constantly. Entry is a property of the session, not the page, so /pricing is the entry page for every session that began there and an ordinary page view in every session that reached it from elsewhere. The same row in a landing page report counts only the first group.

How does Adobe's Entries metric differ from Visits?

Entries counts "the number of times a given dimension item is captured as the first value in a visit," so it is scoped to a dimension item. Visits counts visits. A visit produces exactly one entry for any given dimension, which is why entries summed across all entry page items equals visits that had a page value.

Does the landing page change when a session times out?

Yes. GA4 ends a session after thirty minutes of inactivity by default, and the next page view opens a new session that supplies its own landing page. One uninterrupted human journey can therefore contribute two landing pages, neither of which was where the person originally arrived.

Which dimension should a paid campaign report use?

Landing page + query string in GA4. The plain Landing page dimension discards the UTM parameters that separate one campaign from another at the same path, so every paid, email and organic arrival at /pricing collapses into a single row that no campaign owns.

Does Adobe Analytics have a landing page dimension?

Adobe's documentation names this family "entry dimensions" and ships Entry page and Entry page original, not a landing page. What GA4 calls Landing page, Adobe calls Entry page, computed from the page traffic variable instead of a page_view event.

Why do two URLs with the same page name look identical in Adobe's entry page report?

Because Adobe's entry page comes from the page traffic variable, which normally holds a page name rather than a URL, two URLs sharing that name collapse into a single row. GA4 does not have this problem because Landing page reads the page path directly.

Can a campaign landing page have zero entries?

A landing page built for a campaign that nobody has clicked yet has no entries at all, since Entries only counts sessions that happened to start there. The page is still a landing page by construction, entries or not.

Why does a redirect break landing page reporting for a campaign?

When /promo 302s to /offer/spring, the first page_view fires on the destination, so the entry page becomes /offer/spring and the URL the campaign paid for never shows up in the report. The campaign mapping survives only if the query string carries through the redirect.