What is Page Path and Screen Class in Google Analytics 4?
Diving into Google Analytics 4 can feel like you're learning a new language, especially with dimensions that sound similar but mean very different things. When you open the "Pages and screens" report, the main dimension is named "Page path and screen class," immediately raising questions about what each part means and why they're bundled together. This guide will clarify exactly what Page Path and Screen Class are, how they differ, and how you can use them to better understand your audience's behavior on your website and mobile app.
What is a Page Path in GA4?
A Page Path is the part of a URL that comes after the domain name and before any question marks (which signal the start of query parameters). It identifies the specific page a user is viewing on your website. Think of your website's domain as the street address of an apartment building, and the page path as the specific apartment number.
Let's look at a simple example:
- Full URL:
https://www.yourstore.com/products/running-shoes - Domain:
www.yourstore.com - Page Path:
/products/running-shoes
The page path always begins with a forward slash (/). For your website's homepage, the page path is simply /. This dimension is fundamental to web analytics because it shows you exactly which pages are being visited, allowing you to gauge content popularity, trace user flows, and identify potential issues.
Page Path vs. Other Page Dimensions
It's easy to confuse Page Path with similar-sounding dimensions in GA4. Here’s a quick breakdown to help you keep a few key terms straight:
- Page location: This is the full URL, including the protocol (https://), domain name, page path, and any query strings. For example:
https://www.yourstore.com/products?category=shoes&sort=price_asc. You'd use this dimension when you need to see the entire URL. - Page path + query string: This combines the page path with any parameters that follow a question mark in the URL. For a URL like
www.yourwebsite.com/search?q=ga4-tutorials, the page path is/search, and the page path + query string is/search?q=ga4-tutorials. This is useful for analyzing pages with dynamic content, like on-site search results pages or filterable product category pages. - Page title: This is the content that appears in the browser tab or window title. For instance, the page path
/about-usmight have the page title "About Our Company | Example Inc." While useful, page titles can sometimes be inconsistent or duplicated, making the Page Path a more reliable metric for page identification.
For most website content performance analysis, Page Path is your go-to dimension because it provides a clean, standardized way to identify each page on your site.
Finding and Using Page Path Reports in GA4
Now that you know what it is, let's find it. GA4 includes a pre-built report designed for analyzing page and screen performance. Here’s how to access and customize it to focus on website data.
How to Find the Pages and Screens Report
- Log in to your Google Analytics 4 property.
- From the left-hand navigation menu, click on Reports.
- Under the "Life cycle" collection, expand the Engagement section.
- Click on Pages and screens.
By default, GA4 often sets the primary dimension in this report to "Page title and screen name." To get actionable website data, you'll need to change this.
Switching the report to Page Path
- In the "Pages and screens" report, locate the table of data.
- Click on the little dropdown arrow on the first column heading (which likely says "Page title and screen name").
- From the dropdown list, select Page path and screen class.
The report will now repopulate with all of your website page paths, along with key metrics like Views, Users, Views per user, and Average engagement time. You can sort this table by any metric to quickly find your most (or least) popular pages.
Practical Example: Find Top Performing Content from Organic Search
Let's say you want to know which pages on your website get the most traffic from Google search. You can do this by adding a secondary dimension to the report.
- Once you've set the primary dimension to "Page path and screen class", click the + icon next to the primary dimension dropdown.
- A list of secondary dimensions will appear. Search for and select Session source / medium.
- The table now shows two columns: page path and session source/medium. To isolate organic traffic, use the search bar directly above the table and type "google / organic", then hit Enter.
- Finally, sort the table by the "Views" metric in descending order.
You can now see a clean list of pages that organic search visitors land on most often. This is a powerful, yet simple, way to understand what content is performing best in search results.
What are Screen Class and Screen Name in GA4?
While Page Path deals with websites, Screen Class and Screen Name are its counterparts for mobile applications (like an iOS or Android app). When a user navigates through your app, GA4 tracks the screens they view instead of pages. Because GA4 is designed to unify web and app analytics, these dimensions are included in the same reports as page path, often leading to confusion.
Here’s the difference between the two:
- Screen Class: This is the technical name of the screen, automatically collected from the class name of the
UIViewController(for iOS) orActivity(for Android) that is currently displayed. A developer would recognize it. For example, a screen showing user settings might have a Screen Class ofUserSettingsViewController. - Screen Name: This is a more user-friendly name that you manually set within your app’s code using the Firebase SDK. You can name a screen anything you want, making reports much easier to read. For example, you could give the
UserSettingsViewControlleran easy-to-read Screen Name of "User Settings Screen."
If you don't have a mobile app linked to your GA4 property, the columns for Screen Class and Screen Name in your reports will simply show "(not set)". If you do have an app, you'll almost always want to rely on Screen Name for your analysis because the names are explicitly set to be descriptive and easy for your entire team to understand.
The Key Differences: Page Path vs. Screen Class
Bringing all of this information together, the core distinction is simple: Page Path is for web, and Screen Class/Name is for apps. GA4 combines them to provide a single, cross-platform view of a user's journey.
Here’s a summary of the differences:
The decision to bundle these metrics reflects Google's focus on user-centric tracking. In GA4's data model, a user isn't just a website visitor or an app user, they're one person who might interact with your business across multiple platforms. Combining these dimensions allows you to see their engagement holistically.
Practical Analysis Tips
Understanding the definitions is the first part. Using them to make better decisions is the goal. Here are some actionable ways to analyze user behavior with these dimensions.
For Websites Using Page Path
1. Identify Your Content “Winners” and “Losers”
Go to the Pages and screens report, set the dimension to Page Path, and sort by "Views." Your top pages are your content winners - consider updating them, promoting them more heavily, or creating similar content. Sort in ascending order to find your losers, which might be candidates for deletion, redirection, or improvement.
2. Uncover High-Exit Pages
Within an exploration report, you can add "Exits" as a metric alongside your Page Path dimension. Pages with a high number of exits (relative to views) can indicate a problem. Is the page loading slowly? Is the content unhelpful? Does a link lead nowhere? A high exit rate on a critical "thank you" or "order confirmation" page is a red flag and worth investigating.
3. Analyze User Journeys with Path Exploration
Navigate to Explore → Path exploration. You can set the starting point as a specific page path (like / for your homepage) and see what pages users most commonly navigate to next. This helps you understand how visitors flow through your website and whether they're following your intended funnels.
For Mobile Apps Using Screen Name
1. Measure Feature Popularity and Adoption
Once you’ve set descriptive screen names, the Pages and screens report becomes an easy-to-read view of which app features are most popular. If your new "Social Sharing" feature's screen has very low views, you might need to make it more prominent in the UI.
2. Optimize Your Onboarding Funnel
Use the funnel exploration report in Explore to map out your onboarding screens (e.g., Welcome Screen → Profile Setup Screen → Home Screen). This will visualize where new users are dropping off, giving you clear insights into where your onboarding experience might be confusing or difficult.
3. Understand In-App Behavior
Just like with page path, you can use Screen Name in a path exploration to see how users navigate between different parts of your application. Are they frequently returning to the home screen after viewing a product, or are they proceeding to checkout? This helps you understand engagement patterns and optimize the user flow.
Final Thoughts
Understanding the difference between Page Path and Screen Class is a quick way to level up your Google Analytics 4 skills. Remember, Page Path is for websites and identifies which pages are viewed, while Screen Class and Screen Name do the same job for mobile app screens. By using the right dimension, you can gain a clear, accurate picture of your audience's behavior on any platform.
Knowing which pages and screens drive engagement is just the first step. To connect this behavior to actual business outcomes like campaign ROI or sales revenue, you often have to pull data from other sources. We built Graphed to simplify this by allowing you to instantly create dashboards with your Google Analytics data alongside other sources like Shopify or Facebook Ads, just by asking in plain English.
Related Articles
What SEO Tools Work with Google Analytics?
Discover which SEO tools integrate seamlessly with Google Analytics to provide a comprehensive view of your site's performance. Optimize your SEO strategy now!
Looker Studio vs Metabase: Which BI Tool Actually Fits Your Team?
Looker Studio and Metabase both help you turn raw data into dashboards, but they take completely different approaches. This guide breaks down where each tool fits, what they are good at, and which one matches your actual workflow.
How to Create a Photo Album in Meta Business Suite
How to create a photo album in Meta Business Suite — step-by-step guide to organizing Facebook and Instagram photos into albums for your business page.