When I started working with Google Analytics 4, one thing that confused me the most was the difference between Landing Page Query String and Page Path. At first glance, both look like they’re tracking the same page URL, but they actually measure different things in a user’s session.
Page Path simply shows the page someone viewed on a site, without the extra parameters in the URL. Landing Page Query String, on the other hand, shows the first page a visitor lands on in a session, along with any URL parameters, such as UTM tags from marketing campaigns. That small difference can completely change how I interpret traffic sources and campaign performance.
Understanding these dimensions matters because GA4 processes billions of events daily across websites and apps, making accurate dimensions essential for reliable analysis. In this article, I’ll break down the difference between Landing Page Query String and Page Path in GA4, and explain when I use each one for better reporting.
What Is Page Path and Screen Class in GA4?
In Google Analytics 4, I use the Page Path and Screen Class dimension to see exactly which pages users view on a website or which screens they open inside a mobile app.
For websites, Page Path shows the part of the URL that comes after the domain name. For example, if someone visits:
https://example.com/blog/landing-page-guideThe page path would be:
/blog/landing-page-guide This helps me understand which specific pages are getting traffic without the extra noise from query parameters or tracking tags.
The Screen Class part is used for mobile apps. Instead of URLs, GA4 tracks different views inside an app as “screens.” When GA4 combines both into Page Path and Screen Class, it allows the same report to work for both websites and apps.
In practice, I mainly use this dimension inside the Pages and Screens report in GA4 to analyze which content people are viewing the most and how users move across different pages of a site.
What Is a Landing Page in GA4?
In Google Analytics 4, a landing page is the first page a visitor sees when they arrive on a website during a session. It represents the starting point of a user’s journey on the site.
For example, if someone searches on Google and clicks a result that takes them to:
https://example.com/blog/seo-guidethat page becomes the landing page for that session. Even if the user later visits other pages like a product page or contact page, GA4 will still record the first page they entered as the landing page.
I usually look at the Landing Page report in GA4 when I want to understand which pages are attracting visitors to the site. It helps me identify pages that bring in traffic from sources like search engines, ads, or social media.
According to Google Analytics documentation, the landing page dimension tracks the first page path that starts a session, making it useful for analyzing entry points and measuring how well pages attract new users.
What Is a Landing Page Query String in GA4?
In Google Analytics 4, a Landing Page Query String shows the first page a visitor lands on in a session along with any URL parameters attached to it. These parameters usually appear after a ? in the URL and are commonly used for tracking campaigns.
For example, if someone clicks an ad and lands on:
https://example.com/shoes?utm_source=google&utm_campaign=spring-saleThe landing page path would be:
/shoesBut the landing page + query string would be:
/shoes?utm_source=google&utm_campaign=spring-sale I use this dimension when I want to see exactly how visitors arrived, especially from marketing campaigns. Query strings often contain UTM parameters, which help identify the source, medium, and campaign driving the traffic.
According to Google Analytics documentation, query parameters are commonly used for campaign tracking and attribution, helping marketers understand which channels and campaigns bring users to a website
Landing Page Query String vs Page Path and Screen Class in GA4
The difference between Landing Page Query String and Page Path and Screen Class in GA4 mainly comes down to what part of the user journey I want to analyze.
Page Path and Screen Class shows every page or screen a user views, while Landing Page Query String focuses only on the first page a visitor enters during a session, including any URL parameters.
For example, imagine a user clicks a campaign link and lands on:
https://example.com/shoes?utm_source=google&utm_campaign=saleIn GA4, the data would look like this:
| Dimension | Value |
| Landing Page Query String | /shoes?utm_source=google&utm_campaign=sale |
| Page Path and Screen Class | /shoes |
This means:
- Landing Page Query String helps me understand where visitors entered the site and which campaign brought them.
- Page Path and Screen Class helps me analyze which pages users view across the entire session.
Here’s a simple comparison:
| Dimension | What It Tracks | Best Use |
| Landing Page Query String | First page of a session with parameters | Campaign and traffic analysis |
| Page Path and Screen Class | All pages or screens viewed | Content and user behavior analysis |
In practice, I use Landing Page Query String when I want to measure traffic sources and marketing performance, and Page Path and Screen Class when I want to understand which pages users interact with throughout their visit.
When Should You Use Each Dimension in GA4?
In GA4, I choose the dimension based on what exactly I want to analyze. Even though Landing Page Query String and Page Path and Screen Class come from the same URL data, they answer different questions.
I use Page Path and Screen Class when I want to understand content performance and user navigation across the site. It shows every page people visit during a session, which helps me identify popular pages and how users move between them.
I use Landing Page Query String when I want to analyze traffic sources and campaign performance. Since it includes URL parameters like UTM tags, it helps me see exactly how visitors arrived on the site.
Here’s a simple way I think about it:
| Dimension | When I Use It |
| Page Path and Screen Class | To analyze which pages users view and how they navigate the site |
| Landing Page Query String | To understand where visitors entered the site and which campaigns brought them |
In short, if I want to study user behavior inside the site, I use Page Path and Screen Class. If I want to analyze how visitors arrived, I use Landing Page Query String.
Common Mistakes When Using GA4 Page Dimensions
- When I first started analyzing GA4 reports, I noticed it’s easy to misinterpret data if the wrong page dimension is used. Since dimensions like Page Path, Landing Page, and Landing Page Query String look similar, many reports end up showing misleading insights.
- One common mistake I see is using Page Path to analyze entry pages. Page Path shows every page someone visits, not the first page of the session. If I want to know where users entered the site, I need to use the Landing Page dimension instead.
- Another mistake is ignoring query strings when analyzing campaigns. Marketing links often include parameters like UTM tags. If I only look at Page Path, those campaign details disappear, and I can’t see which campaign actually brought the visitor.
- I also see people mixing dimensions in the same analysis without understanding what each one tracks. For example, comparing Page Path data directly with Landing Page metrics can lead to confusion because one tracks all page views, while the other tracks session entry points.
To avoid these issues, I always make sure the dimension I choose matches the question I’m trying to answer, whether it’s how users navigate the site or how they first arrived.
Conclusion
Understanding the difference between Landing Page Query String and Page Path and Screen Class in GA4 helps me interpret data more accurately. Page Path and Screen Class shows every page users view, while Landing Page Query String focuses on the first page of the session along with any URL parameters.
By using the right dimension for the right analysis, I can better understand how visitors arrive and how they navigate through the site.
Frequently Asked Questions
What is Page Path and Screen Class in GA4?
Page Path and Screen Class shows the specific pages users view on a website or the screens they open in a mobile app. It helps analyze how users move through different pages during a session.
What is the Landing Page Query String in GA4?
Landing Page Query String shows the first page a visitor lands on in a session, along with any URL parameters, such as UTM tags used for campaign tracking.
What is the difference between Landing Page Query String and Page Path in GA4?
Landing Page Query String tracks the first page of a session, including parameters, while Page Path shows all pages viewed during the session without query parameters.
When should I use Page Path and Screen Class in GA4?
I use Page Path and Screen Class when I want to understand which pages users visit and how they navigate through the site.
When should I use Landing Page Query String in GA4?
I use Landing Page Query String when I want to analyze traffic sources, campaigns, and how visitors first arrive on the site.