GA4 Sessions and Engaged Sessions: Definitions and Formulas

What is a session in GA4?

A session groups a user's website or app activity during a visit. It is different from a person or a page-view count.

A person opening three pages may still be in one session. Returning after inactivity may start another, so 100 sessions does not mean 100 distinct people.

When does a session start and end?

GA4 starts a session when a user opens the site or app without an active session. The documentation specifies a default timeout after 30 minutes of inactivity; that setting can be adjusted. A session is not defined by a fixed maximum duration.

The interface documented on 18 October 2026 uses the path Admin → Data Streams → the web stream → Configure tag settings → Show all → Adjust session timeout. It includes timeout and engaged-session timer settings. Interface labels and available controls should be checked in the actual property.

What counts as an engaged session?

Under the documented default, a session qualifies if it lasts longer than 10 seconds, has a key event, or contains at least two page or screen views. Meeting any one condition is sufficient. The time threshold can be adjusted.

Events such as first_visit, first_open and session_start are excluded from the engaged-session calculation even if marked as key events. A recorded event and a qualifying key event are not interchangeable.

Engagement rate and bounce rate

Engagement rate = engaged sessions ÷ all sessions. Bounce rate = non-engaged sessions ÷ all sessions. For the same scope, they sum to 100%.

Illustrative example: 620 of 1,000 sessions qualify, giving 62% engagement and 38% bounce. In Google's example, a visitor leaves before 10 seconds, triggers no qualifying event and opens no second page. If it is the only session, engagement is 0% and bounce is 100%.

Qualification does not establish satisfaction or a purchase. It records whether one of the defined conditions was met.

Where can the measures be inspected?

Sessions and engaged sessions are available in acquisition and engagement reporting and in Explorations. Google's documented route for engagement rate and bounce rate is to customize a detail report, add the metrics, apply and save.

That customization requires Editor or Administrator access and applies to detail reports rather than overview cards. The documentation describes the available operation; no property setting has been changed for this article.

To inspect recognized AI visits, combine the relevant source dimension with session measures as explained in the AI referral guide.

Sources and scope

Source-language entry records a source check on 2026-10-18. Google’s engagement and bounce-rate documentation was also reopened on 2026-10-26, including qualifying criteria, excluded events and report customization. The settings path retains the source entry’s recorded interface scope.