Session timeout and event grouping
Session timeout is the period of inactivity after which the next event starts a new session rather than continuing the old one. It governs how GA4 groups events into sessions: a return after the timeout begins a fresh session_start. The default window is configurable. Understanding it explains why a single user can generate several sessions, and how changing the timeout shifts session counts without any change in behaviour.
How events become sessions
GA4 groups a user's events into a session until a period of inactivity equal to the session timeout passes; the next event then opens a new session with a fresh session_start. The timeout is configurable in the property's settings (Google Analytics Help). So a session is not a fixed clock period — it is a run of events with no gap longer than the timeout.
Why the window matters
Because the timeout defines the boundary, changing it changes session counts directly: a shorter window splits one long visit into several sessions; a longer window merges them. Comparisons across a timeout change are not like-for-like. Choose the window to fit how people actually use your site — long-form reading or research may justify a longer timeout — and document any change so trend reports remain interpretable.
- A session = events with no gap exceeding the timeout
- Timeout is configurable per property
- Changing it shifts session counts with no behaviour change
How it appears in analytics and logs
A jump in sessions per user without behaviour change can follow a shorter timeout; fewer, longer sessions can follow a longer one — a configuration effect, not real change.
Diagnostic use case
Interpret session counts correctly by knowing the timeout window that groups events, and adjust it deliberately when your usage pattern justifies a different boundary.
What WebmasterID can help detect
WebmasterID groups first-party events into sessions by a timeout window too; GA4's configurable timeout and its effect on counts are documented here.
Common mistakes
- Comparing session counts across a timeout change as like-for-like.
- Assuming a session is a fixed clock duration.
- Changing the timeout without documenting it for trend reports.
Privacy and accuracy notes
Session timeout is a grouping rule over event timing, not identity. It decides boundaries between sessions and stores no personal data itself.
Related pages
- The session_start event
The session_start event marks the beginning of a visit. In GA4 it is fired automatically the first time a user is active in a new session, and it underpins every session-scoped metric. Understanding when a session begins — and the timeout that ends it — explains why session counts behave the way they do across midnight, campaigns, and idle periods.
- Idle and active state signals
Idle and active signals separate time a user is actually interacting from time the page is merely open. Analytics derives an active state from recent interaction (clicks, keypresses, scroll) and treats prolonged silence as idle, so engagement time does not inflate. This is a derived concept built from input events and visibility, not a single named GA4 event. It keeps engagement-based metrics meaningful.
- Sessions: what a session is and when it resets
A session is a group of interactions from one visitor within a bounded time window. It starts on the first event and ends after a period of inactivity (commonly 30 minutes, configurable). The reset rules differ by tool — and historically Universal Analytics also restarted sessions at midnight and on a new campaign — so the same traffic produces different session counts in different products.
- Web analytics
Read session counts with their boundary in mind.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.