Study first
Review the ideas behind the questions
Check what each GA4 engagement report is meant to answer before you judge a page. Focus on the difference between visited pages, first landing pages, live activity, and engagement metrics.
Pick the page report that matches the question
Page reporting starts with the business question: which pages were visited, which page started the session, or what happened before and after a page.
- Use Pages and screens when the question is about pages or screens users visited.
- Use Landing page when the question is about the first page a visitor saw.
- Use path exploration when the question is what users did before or after a page.
In Practice
Separate page visits from entry pages
A page can have many visits without being the first page of a session. Use the report that matches the wording of the question.
Move to paths for sequence questions
If the stakeholder asks what happened next, the table of page totals is not enough. Start a path exploration from the page.
Common mistakes
Using Pages and screens to answer every page question.
Use Landing page for first-page questions and path exploration for before-or-after navigation questions.
Q&A
Which report answers which pages people visited?
Use Pages and screens for visited pages or screens.
Which report answers the first page visitors saw?
Use the Landing page report for the first page visitors land on.
Read engagement metrics by definition
Engagement metrics can sound familiar, but GA4 defines them through active users and engaged sessions.
- Average engagement time measures time with the site in focus or app in the foreground.
- An engaged session can qualify through time, a key event, or two or more page or screen views.
- Bounce rate is the share of sessions that were not engaged.
In Practice
Do not read views as attention time
Views can show how often pages or screens were seen, but they do not replace engagement-time metrics.
Explain bounce rate in GA4 terms
If someone expects the older bounce idea, bring the discussion back to engaged sessions before recommending page changes.
Common mistakes
Calling every one-page visit a bounce.
Check whether the session was engaged by GA4 criteria before treating it as not engaged.
Q&A
What is average engagement time divided by?
It is based on total user engagement durations divided by active users.
How is GA4 bounce rate tied to engagement rate?
Bounce rate is the opposite side of engagement rate: sessions that were not engaged.
Use live reports for live questions
Realtime reporting is useful when the question is about what is happening now. It should not be confused with finalized historical analysis.
- Realtime pages shows views and active users from the last 30 minutes.
- The Realtime pages table breaks active users down by page path and screen class.
- Realtime pages currently does not support custom comparisons and filters.
In Practice
Use the right time window
Use Realtime pages to confirm current activity after a launch. Use standard reports when the team needs a processed historical view.
Keep customization expectations modest
If a stakeholder wants comparisons or filters, explain that this specific realtime report has limits.
Common mistakes
Using a live report as final campaign proof.
Treat Realtime pages as a current-activity check and use standard reports for finalized historical analysis.
Q&A
When does Realtime pages fit best?
Use it when the question is about current page or screen activity in the last 30 minutes.