GA4 Session Timeout Settings: Default 30 Minutes and When to Change It.

A "session" in GA4 is not as simple as it sounds. GA4 has two timeout settings that control when sessions start and end — and they directly affect your session count, engagement rate, bounce rate, and attribution. Most teams never touch them. Some should.

Understanding GA4 Session Timeout Settings

The Two GA4 Session Settings You Can Configure

GA4 exposes two session-related timeouts in the admin UI. Both are property-wide settings that affect every session going forward, and both have defaults optimized for a generic average site — which is almost certainly not your site. Before tuning either one, understand what each controls and which metrics it drives. Changes take effect immediately but are not retroactive: historical data keeps the old timeout logic.

• Session timeout: How long a user can be inactive before a new session starts. Default: 30 minutes. Range: 5 minutes to 7 hours 55 minutes.
• Engaged session timer: How long a user must be actively engaged for the session to count as "engaged." Default: 10 seconds. Range: 10 seconds to 60 seconds.

Both are configured in one place: Admin → Data Streams → [your stream] → Configure Tag Settings → Show More → Adjust session timeout. Google buried these settings intentionally — they want most sites to keep the defaults.

How Session Timeout Affects Your Metrics and Attribution

How Session Timeout Affects Your Key Metrics

The 30-minute default means: if a user is inactive for 30+ minutes and then interacts again, GA4 ends the current session and starts a new one. This single setting cascades into four of the metrics you look at most often. Changing the timeout is never "free" — you're trading one metric for another, and you need to understand the trade-offs before touching the setting in a live property.

• Session count: Shorter timeout = more sessions (same user, multiple sessions counted). Expect 5-15% more sessions if you drop from 30 to 15 minutes.
• Attribution: A new session can carry a new traffic source. If someone returns via a different referrer after timeout, that becomes a new attributed session — potentially crediting Direct instead of the original paid campaign.
• Engagement rate: More sessions means more opportunities for unengaged sessions, potentially lowering your engagement rate.
• Pages per session: Shorter timeout = fewer pages per session on average, making your navigation metrics look worse.

When to Change the Default Session Timeout

When to Increase the Session Timeout (Beyond 30 Minutes)

Increasing the session timeout is the right call when your typical user workflow includes long periods of genuine idleness that shouldn't split into separate sessions. The goal is to match the timeout to your users' actual behavior — if a natural browsing pattern regularly exceeds 30 minutes of tab-open-but-inactive time, the default undercounts the depth of each visit and fragments attribution.

• Long-form content sites: Users read articles for 30+ minutes, leave to reference something, and return. Video streaming, online courses, and documentation sites typically benefit from 60-120 minute timeouts.
• Complex B2B purchasing: Users browse pricing, get pulled into a meeting, and return 45 minutes later to continue evaluating. A 60-minute timeout keeps this as one session, preserving accurate attribution.
• SaaS applications: If your app has idle periods (e.g., user fills a form, pauses to review a doc, returns), longer timeouts prevent session fragmentation that distorts retention and feature-usage metrics.

When to Decrease the Session Timeout (Below 30 Minutes)

Decreasing the session timeout is unusual but occasionally the right move. It applies when your typical user workflow is measured in minutes, not hours, and when the default 30-minute window combines visits that should be counted separately. The biggest win from decreasing the timeout is cleaner attribution on short-intent sessions — you stop blending the first visit with the second when the user has genuinely moved on between them.

• Quick-action sites: Food delivery, ride-sharing, quick-commerce — users make decisions in minutes. A 15-minute timeout better reflects actual sessions and keeps attribution tight.
• Kiosk or shared devices: In retail, hospitality, or conference kiosks where devices are shared, a 10-15 minute timeout prevents different users' sessions from being merged into one bloated session.
• Transactional tools: Calculators, converters, single-task utilities — users complete their task in under 10 minutes and leave. A shorter timeout keeps each task a distinct session.

The Engaged Session Timer

The Engaged Session Timer: More Impactful Than You Think

The engaged session timer (default 10 seconds) directly controls GA4's engagement rate and bounce rate across your entire property. A session counts as "engaged" if the user stays for this duration OR fires a conversion OR views 2+ pages. The 10-second default is forgiving; the maximum of 60 seconds is strict. Raising this setting narrows the definition of engagement and will noticeably lower your engagement rate and raise your bounce rate — this is not a bug, it's a stricter bar applied to the same traffic.

• Increase to 15-30 seconds: Fewer sessions qualify as "engaged," raising bounce rate and making your engagement metric more meaningful for content-heavy sites.
• Leave at 10 seconds (default): The right choice for transactional and commerce sites where the key event (purchase, signup) naturally takes longer than 10 seconds anyway.
• Decrease: Not possible — 10 seconds is the minimum.

Important: Changing either setting is not retroactive. It only affects data from the moment you save forward. Historical data keeps the old setting's logic, which means you'll see a step change in your reports on the day of the change.

How Session Timeout Directly Impacts Attribution

Every new session can carry a new traffic source. This is the critical second-order effect most teams miss: session timeout doesn't just affect session counts, it directly changes which campaigns get credit for conversions. A poorly-chosen timeout can shift 10-30% of your paid-campaign conversions into the Direct channel, making your ad spend look less effective than it actually is. The two scenarios below show the same user behavior producing completely different attribution depending on timeout.

• 30-minute timeout (default): User clicks a Google Ad → lands on your site → idle for 31 minutes in a background tab → continues browsing → GA4 starts a new session attributed to Direct because no new referrer was present. The Google Ad loses credit for any subsequent conversion.
• 60-minute timeout: Same scenario, but the user returns within 60 minutes → single continuous session → all activity and any resulting conversion attributed correctly to the original Google Ad click.

Frequently Asked Questions

What is GA4 session timeout?

GA4 session timeout is the period of user inactivity after which GA4 closes the current session and starts a new one if the user becomes active again. The default is 30 minutes. If a user opens your site, reads for 10 minutes, then stops interacting for 31 minutes, and then clicks a link, GA4 records that click as the start of a brand-new session — not a continuation of the earlier one. The timeout is property-wide, applies to all streams on that property, and changes take effect going forward only; historical data keeps the setting that was active when it was collected.

How long is a GA4 session?

A GA4 session lasts until one of three things happens: the user is inactive for longer than the session timeout (default 30 minutes), midnight passes in the user's time zone (GA4 splits sessions at the day boundary), or the user's campaign attribution changes because they clicked a new UTM-tagged link. There is no hard maximum session length — a user who keeps interacting with your site for three hours without a 30-minute idle period will count as a single session for that entire period. The average session duration you see in reports is the median of all sessions that completed in your selected date range.

How do I change GA4 session timeout?

Go to Admin → Data Streams → [your web stream] → Configure Tag Settings → Show More → Adjust session timeout. The setting is nested several layers deep, which is intentional — Google wants most sites to leave the default. You'll see two sliders: one for session timeout (5 minutes to 7 hours 55 minutes) and one for the engaged session timer (10 seconds to 60 seconds). Adjust the session timeout slider to the value that reflects your users' typical active browsing window and save. The change takes effect immediately on new sessions; existing open sessions finish under the old timeout logic.

Does GA4 session timeout affect engagement rate?

Yes, indirectly. Session timeout controls how many sessions are counted, and engagement rate is calculated as engaged sessions divided by total sessions. If you shorten the timeout, the same user activity produces more sessions — some of which may be short, unengaged sessions that pull the engagement rate down. If you lengthen the timeout, fewer sessions are created and each one is more likely to meet the engagement threshold (10+ seconds, 2+ pages, or a conversion), which tends to lift the engagement rate. The engaged session timer setting has a more direct impact on engagement rate because it sets the duration threshold a session must meet to qualify as engaged.

What is the maximum GA4 session timeout?

The maximum GA4 session timeout is 7 hours and 55 minutes. The minimum is 5 minutes. The default is 30 minutes. In practice, even content-heavy sites rarely need more than 2–4 hours; the upper end of the range exists for edge cases like kiosk deployments, long-running web applications, or properties where users leave a tab open overnight as part of their workflow. Setting the timeout extremely high (above 4 hours) can cause attribution problems if a user genuinely visits twice in one day — both visits would be counted as one session, and any new campaign source from the second visit would be ignored.

How does GA4 handle sessions at midnight?

GA4 splits sessions at midnight in the user's local time zone. If a user is actively browsing at 11:58 PM and continues past midnight, GA4 closes the session at midnight and opens a new one for the activity that crosses into the new day. This means a single continuous visit can produce two sessions if it straddles midnight — one session on day one and one on day two. This behavior is by design and matches the day-boundary logic used in many session analytics tools. It means session counts for pages with high late-night traffic can appear slightly inflated compared to what you'd expect from the activity data alone.

What is the difference between session timeout and engaged session timeout in GA4?

These are two distinct settings that control different things. Session timeout defines the inactivity window after which a new session begins — it affects session count and attribution. The engaged session timer defines the minimum active duration a session must have to qualify as "engaged" — it affects engagement rate and bounce rate. A session can be long (well above the timeout threshold, because the user kept interacting) but still unengaged if the user spent all their time on a single page without triggering a conversion or a second page view. Conversely, a short session can be engaged if it contains a conversion event even if it lasts fewer than 10 seconds.

Should I change the default GA4 session timeout?

For most sites, no. The 30-minute default is a reasonable middle ground that Google calibrated across a broad range of site types. The cases where changing it genuinely improves data quality are specific: if your users regularly take breaks longer than 30 minutes during what is logically one continuous visit (long-form content, complex B2B evaluation, SaaS applications), increasing the timeout to 60–90 minutes keeps those visits together and preserves attribution. If your site serves quick-decision users who complete a task in under 10 minutes and return later for a distinct second visit, a shorter timeout may produce cleaner session boundaries. Before changing it, run a session duration distribution report in Explorations to see how your actual sessions cluster — if sessions are almost never longer than 20 minutes, the 30-minute default isn't causing problems worth fixing.