Reports

[GA4] Pages and screens report

The Pages and screens report is a pre-made detail report that shows data about the pages users visited on your website and the screens users opened on your mobile app, enabling you to see where people are going across both your websites and apps. The 'pages' refers to the individual pages on a website, while the 'screens' refers to the individual screens on a mobile app.

How do users interact with your website or app? Use Engagement reports in Google Analytics

For subtitles in your language, turn on YouTube captions. Select the settings icon at the bottom of the video player, then select "Subtitles/CC" and choose your language.

View the report

Sign in to Google Analytics.
From the left menu, select Reports .
On the left, click Engagement > Pages and screens.

Note: If you can't find the report, it may have been removed or isn't in your default view. Editors (and above) can add it back to the left navigation. Learn more about how to add the report.

See data for one page or screen

If you want to focus the report charts and table on one page or screen (and hide the rest of the data), add a report filter. Make sure the report filter has the following definition so you only see data for one or a few pages or screens:

Click + Add filter at the top of the report.
In the 'Build filter' dialog on the right, leave 'Include' selected.
In the 'Dimension' drop-down, select 'Page path and screen class'.
In the 'Dimension values' drop-down, select one or more page paths or screen classes.
Click OK.
Click Apply.

Note: If your page gets localized, you’ll see the Page title dimensions in the localized language. If you want to view the page title in one language, for example, in English, you can override the title that gets pulled from the <title> tag using the page_title event parameter. Learn more about [GA4] Google Analytics event parameters.

See the first page someone landed on

The Pages and screens report shows data about the pages and screens people are visiting, whether that's the first page or a page later in their session. If you want to see the first page from your website that they land on, use the Landing page report instead.

See what a user did before or after visiting a page or screen

To see what someone did before or after visiting a page or screen, create a path exploration. A path exploration enables you to choose a page or screen to start or end with, and then see the pages or screens that users visited either right after or right before that page or screen.

For example, it could help you answer the question, "After someone visited the t-shirt page, what page did they go to next?" or "Before someone saw the 'Upgrade my plan' screen, what screens did they visit before?"

Understand what the page path '/' means

The page path '/' is a directory separator that indicates that the home directory of the website was requested. In other words, it represents the home page of your website.

Dimensions in the report

The report includes the following dimensions. If you are an Editor or Administrator, you can add or remove dimensions in the report.

Dimension	What it is	How it's populated
Content group	The content group (i.e., the categories of pages and screens you've defined) associated with a page or screen.	Content group derives from the `content_group` parameter. Learn more
Hostname	The subdomain and domain names of a URL that people visited on your website. For example, the hostname of 'example.com/contact.html' is 'example.com'.	This dimension is populated automatically.
Page path and screen class	The page path from a website URL and screen class from a mobile app.	Page path derives from the value after the domain. For example, if someone visits `example.com/Bags`, then `example.com` is the domain and `Bags` is the page path. Screen class derives from the class name of the `UIViewController` or `Activity` that is currently in focus.
Page title and screen class	The page title from a website and screen class from a mobile app.	Page title derives from the `<title>` tag in your HTML. Alternatively, you can add the `page_title` parameter to the `config` command to send a different page title. Screen class derives from the class name of the `UIViewController` or `Activity` that is currently in focus.
Page title and screen name	The page title from a website and screen name from a mobile app.	Page title derives from the `<title>` tag in your HTML. Alternatively, you can add the `page_title` parameter to the `config` command to send a different page title. Screen name derives from the name you set for a screen using Firebase.

Metrics in the report

The report includes the following metrics. If you are an Editor or Administrator, you can add or remove metrics in the report.

Metric	What it is	How it's populated
Average engagement time	The average time that your website was in focus in a user's browser or an app was in the foreground of a user's device. Average engagement time = Total user engagement durations / Number of active users	This metric is populated automatically.
Key events	The number of times users triggered a key event.	Populate this metric by marking an event as a key event.
Event count	The number of times users triggered an event.	This metric is populated automatically.
Total revenue	The total revenue from purchases, in-app purchases, subscriptions, and ad revenue.	This metric is the sum of the purchase, in_app_purchase, app_store_subscription_renew, and app_store_subscription_convert events, as well as ad revenue, which is populated via the Google AdMob integration, Google Ad Manager integration, or by sending the ad_impression event from a third-party integration.
Views	The number of mobile app screens or web pages your users saw. Repeated views of a single screen or page are counted.	This metric is populated automatically.
Views per active user	The average number of mobile app screens or web pages viewed per active user.	This metric is populated automatically.
Active users	The number of distinct users who visited your website or app.	This metric is populated automatically.

Was this helpful?

How can we improve it?