What's the Default Session Timeout in GA4?

GA4's default session timeout is 30 minutes of inactivity — if a user doesn't trigger a new event within 30 minutes of their last one, GA4 ends that session. You can adjust this setting anywhere from a minimum of 5 minutes up to a maximum of 7 hours 55 minutes.

Where Session Timeout Lives in GA4

Session timeout is configured per data stream, not account-wide: go to Admin, then Data Streams, select your web stream, open Configure Tag Settings, then Show More, and adjust the "Session timeout" value under Adjust Session Timeout. This is a web-specific setting — it's distinct from how GA4 counts "engaged sessions," which require a session to last at least 10 seconds, include a conversion event, or include two or more page or screen views.

Why the Default Matters

A 30-minute window means a visitor who leaves your site, grabs coffee, and comes back 40 minutes later to finish checkout gets counted as a new session, not a continuation of the first one. That split affects session-based metrics like sessions per user, average engagement time per session, and any session-scoped conversion reporting — not the events themselves, which are always recorded, but how GA4 groups them.

When to Raise or Lower It

• Content and research-heavy sites often raise the timeout, since users genuinely pause for long stretches — reading a long guide, comparing options in another tab — without actually disengaging from that visit.
• E-commerce checkout funnels sometimes shorten it to better reflect true single-visit purchase behavior and avoid conflating a user's unrelated return visit with their original session.
• Most standard marketing sites can leave the default alone, since 30 minutes reasonably approximates a single browsing session for most verticals.

Session Timeout Doesn't Change What Gets Recorded

It's worth being precise about what this setting actually controls: every event GA4 collects is still recorded regardless of the timeout value you choose. What changes is only how those events get grouped into sessions after the fact. A shorter timeout produces more, shorter sessions out of the same underlying event stream; a longer timeout produces fewer, longer ones. That distinction matters because teams sometimes chase a "better" engagement rate by adjusting session timeout, when the actual user behavior behind the data hasn't changed at all — only the grouping has.

Signs Your Timeout Setting Might Be Wrong for Your Site

• Unusually high bounce-like behavior on long-form content can indicate the timeout is too short for how long users genuinely spend reading before interacting again.
• Session counts that look inflated relative to your traffic volume can indicate users are naturally pausing mid-visit — browsing a product, stepping away, then returning — in a way the current timeout is splitting into separate sessions.
• A multi-day sales cycle with form fills spread across visits is a signal to look at your conversion window and attribution settings rather than session timeout, since session timeout can't meaningfully bridge gaps longer than its 7-hour-55-minute ceiling.

Bottom Line

Don't change GA4's session timeout without a specific reason tied to your users' real behavior — the 30-minute default is a reasonable approximation for most sites, and adjusting it mainly matters if your typical visit includes a long, natural pause.

Sources: Measure School, "What are Google Analytics 4 Sessions" (measureschool.com/google-analytics-4-sessions); Perfist, "What is Session Timeout in Google Analytics 4, Why is it Important and How to Configure It?" (perfist.com).