GA4 Session Timeout Settings: When to Change Them and Why It Matters

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.

The Two Session Settings

GA4 has two configurable session-related timeouts:

• Session timeout: How long a user can be inactive before a new session starts (default: 30 minutes)
• Engaged session timer: How long a user must be active for the session to count as "engaged" (default: 10 seconds)

Both are configured under Admin → Data Streams → [your stream] → Configure Tag Settings → Show More → Adjust session timeout.

How Session Timeout Affects Your Data

The 30-minute default means: if a user is inactive for 30+ minutes and then interacts again, GA4 starts a new session. This affects:

• Session count: Shorter timeout = more sessions (same user, more sessions counted)
• 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.
• Engagement rate: More sessions means more opportunities for unengaged sessions, potentially lowering engagement rate.
• Pages per session: Shorter timeout = fewer pages per session on average.

When to Increase the Session Timeout

Consider increasing beyond 30 minutes if:

• Long-form content: Users read articles for 30+ minutes, leave to reference something, and return. Video streaming platforms, online courses, and documentation sites often benefit from 60-120 minute timeouts.
• Complex B2B purchasing: Users browse, get pulled into a meeting, and return 45 minutes later to continue evaluating. A 60-minute timeout keeps this as one session.
• Applications (SaaS): If your app has idle periods (e.g., user fills out a form, pauses, continues), longer timeouts prevent session fragmentation.

When to Decrease the Session Timeout

Consider decreasing below 30 minutes if:

• Quick-action sites: Food delivery, ride-sharing, quick-commerce — users make decisions in minutes. A 15-minute timeout may better reflect actual sessions.
• Kiosk or shared devices: In retail or hospitality settings where devices are shared, a shorter timeout (10-15 minutes) prevents mixing different users' sessions.

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. Adjusting this changes both metrics across your entire property:

• Increase to 15-20 seconds: Fewer sessions qualify as "engaged", raising your bounce rate. Use this if you want a stricter definition of engagement.
• Decrease to 5 seconds: More sessions qualify as "engaged", lowering your bounce rate. Not recommended — it makes the metric less meaningful.

Important: Changing either setting is not retroactive. It only affects data from the moment you save the change forward. Historical data keeps the old setting's logic.

How Sessions Impact Attribution

Every new session can carry a new traffic source. This means session timeout directly affects your channel attribution:

• User clicks a Google Ad → lands on your site → idle for 31 minutes → continues browsing → GA4 starts a new session attributed to direct (no new referrer)
• Same scenario with a 60-minute timeout → single session, all activity attributed to the original Google Ad click