GA4 Sessions, Engaged Sessions and Bounce Rate

What is a session in Google Analytics, what counts as an engaged session in GA4, and how are engagement rate and bounce rate calculated? These come up in the Google Analytics certification and in every argument about whether a landing page is working. GA4 changed the definitions from Universal Analytics, so old rules of thumb about bounce rate no longer apply.

Short answer: a session is "a period of time during which a user interacts with your website or app", and by default it ends after 30 minutes of inactivity. An engaged session is one that lasts longer than 10 seconds, has a key event, or has 2 or more page or screen views. Engagement rate is the percentage of sessions that were engaged, and bounce rate is the opposite: the percentage of sessions that were not engaged. Sources: Google Analytics Help, About Analytics sessions and [GA4] Engagement rate and bounce rate.

How GA4 Counts a Session

• Start: a session begins when someone views a page or screen (or opens your app in the foreground) and no session is currently active. GA4 records a session_start event and creates a session ID.
• End: after 30 minutes of inactivity by default. Google notes "there is no limit to how long a session can last."
• Timeout is adjustable: in Admin, Data Streams, Configure tag settings, Adjust session timeout. The same screen lets you change the number of seconds before a session counts as engaged.
• Attribution: the session_start event carries the gclid, UTM parameters and referrer that decide which channel gets credit (a UTM builder keeps those values consistent).
• Counting: GA4 estimates the number of unique session IDs, so session totals are an estimate rather than an exact count.

Engaged Sessions, Engagement Rate and Bounce Rate

Google's example: a visitor reads for less than 10 seconds, triggers no event and leaves. That session is not engaged. If it were the only session, engagement rate would be 0% and bounce rate 100%.

The important change from Universal Analytics: a single-page visit where someone reads for two minutes and leaves used to count as a bounce. In GA4 it is an engaged session. A long blog post or a landing page with all the information on one screen is no longer penalized for not generating a second pageview.

Two practical notes from the documentation: most standard reports do not show engagement rate and bounce rate until you add them with Customize report (Editor or Administrator role needed), and first_visit, session_start and similar events do not make a session engaged even if marked as key events.

Using Engagement Rate on B2B Landing Pages

Engagement rate is the best quick diagnostic GA4 gives you for a landing page, because it separates "people arrived and left immediately" from "people read". Google's own guidance for low engagement is useful: check whether "the content correlates well with the marketing you use to drive users to those pages", and "if users who come from display are bouncing, make sure your ads are relevant to your site content." Reading these reports well is a core skill in most marketing analytics jobs.

That is a message match problem. When paid traffic shows low engagement on a page that organic visitors engage with, the page is usually fine and the ad promises something else. Our post on landing page experience explains how Google evaluates the same thing from the ads side.

A diagnostic sequence that works:

1. Open the Pages and screens report, add engagement rate, and filter to your landing pages.
2. Add a secondary dimension of session source / medium or session campaign.
3. Compare engagement rate by channel for the same page. A gap of more than a few points between paid and organic usually points to the ad, not the page.
4. For pages with low engagement across all channels, check load time and what is above the fold. Our guide to B2B landing page optimization lists the usual fixes.
5. Set the form submission or demo request as a key event so engaged sessions with a conversion are visible.

Worked B2B Example (Illustrative)

Illustrative numbers: a B2B company sees a comparison page with healthy engagement from organic search but much lower engagement from a display campaign.

• The display ad says "See the 2026 pricing guide". The page is a feature comparison with pricing three scrolls down.
• Fix: a second version of the page for that campaign with the pricing summary at the top, sized with the A/B test calculator and tested against the original on display traffic only.
• Read the result on engagement rate first (fast signal), then on visits to the pricing page and demo requests (slower, more important).

If you personalize pages by segment, compare engagement rate for personalized and default sessions with a holdout. Our guide to measuring personalization ROI shows how to set that up, and account-level website analytics adds which companies those engaged sessions came from.

Frequently Asked Questions

What is a session in Google Analytics?

A period of time during which a user interacts with your website or app. In GA4 it starts with a page or screen view when no session is active and ends after 30 minutes of inactivity by default.

What is an engaged session in GA4?

A session that lasts longer than 10 seconds, includes a key event, or has at least 2 page or screen views. The 10-second threshold can be changed in the data stream's tag settings.

How is bounce rate calculated in GA4?

Bounce rate is the percentage of sessions that were not engaged. It is the inverse of engagement rate, so a 60% engagement rate means a 40% bounce rate.

What is engagement rate in GA4?

The percentage of sessions that were engaged sessions. Google describes it as a way to measure the share of visits that involved some form of meaningful engagement.

Why is my GA4 bounce rate lower than in Universal Analytics?

Because the definition changed. A single-page visit longer than 10 seconds counts as engaged in GA4, while Universal Analytics counted any single-page session as a bounce.