How Session Timeout Rules Quietly Inflate Your Analytics

What is a session timeout?

A session timeout is the length of visitor inactivity an analytics tool waits before it closes an open session and starts a new one on the next tracked event. Every major analytics platform runs a countdown that resets on each pageview, click or scroll a visitor generates, and once that countdown reaches zero with no new activity, the session ends. The next action from that same visitor, seconds or hours later, opens a fresh session instead of continuing the old one.

What is the 30-minute inactivity rule?

The 30-minute inactivity rule is the default session timeout that Google Analytics 4, Universal Analytics, Adobe Analytics, Matomo and Plausible all ship with out of the box. A visitor who takes no tracked action for 30 minutes has their session closed by every one of these tools unless the site owner has changed the setting. The rule exists as a shared industry convention, not a technical requirement, and every platform listed exposes a way to move it, which is why comparing raw session totals between two sites only works when both sites run the same timeout value.

Does a session timeout also close at midnight?

In Universal Analytics, yes; in GA4, no. Universal Analytics closed every open session at midnight in the property's configured timezone, so a visitor browsing from 11:50pm to 12:10am produced two sessions purely from crossing the date line, with no gap in their activity at all. GA4 removed the midnight cutoff and relies on the inactivity timer as the only default closing condition, so that same 20-minute browsing stretch straddling midnight now counts as one session in GA4. What a session actually contains covers how Matomo and Adobe handle the same day-boundary question, since the two platforms did not converge on identical rules after Universal Analytics retired.

Does a new marketing campaign trigger a session timeout in classic analytics?

Yes, in Universal Analytics, a session closed and a new one opened the moment a visitor's traffic source changed, even while the visitor stayed active on the page. A visitor who arrived from organic search and then clicked a UTM-tagged campaign link ten minutes later, well inside the 30-minute inactivity window, still triggered a new session in Universal Analytics because the campaign parameters changed. GA4 does not carry this rule forward; a campaign change no longer closes a session on its own, and only the inactivity timer decides when one ends.

How do you configure the session timeout in GA4?

GA4 exposes the session timeout in Admin, under the data stream's tag settings, where the value can be raised from a 5-minute minimum up to a maximum of 7 hours and 55 minutes. Raising the timeout keeps a slower-paced visit, such as someone reading a long article or filling out a multi-step form with pauses between fields, inside one session instead of splitting it every time they stop clicking for half an hour. The setting applies going forward from the moment it is saved and does not retroactively recalculate sessions already recorded under the previous value.

session count for one visit = 1 if the longest gap between events < timeout, else it increases by one for each gap that exceeds the timeout

Why does a short session timeout inflate session counts?

A short session timeout inflates session counts because any natural pause in a visitor's behavior that exceeds the timeout value gets counted as the end of one visit and the start of another, even though the visitor never left. Take a single visitor who opens a page at 14:00, reads for a while, and clicks a second link at 14:52, a 52-minute gap caused entirely by reading time.

The visitor's behavior did not change between the two rows; only the setting did. A site that shortens its timeout to catch bounces faster will see its total session count rise and its pages-per-session ratio fall, and neither change reflects anything happening in actual traffic.

Every metric that divides by session count moves with it. Bounce rate rises when a single-page visit that would have continued past the timeout gets recorded as a session that ended after one page, and pageviews per session falls for the same reason, both without any change in what the visitor actually did.

How do you choose the right session timeout for your site?

Choose a session timeout that roughly matches how long a genuine, engaged visitor pauses between actions on your specific site, then leave it fixed once it is set. A documentation site or a long-form publisher, where readers routinely stop for several minutes without clicking, benefits from a longer timeout than the 30-minute default; a checkout flow or a short interactive tool rarely needs one longer than the default, since a 30-minute gap there means the visitor has left. Changing the timeout later resets the baseline for every session-based metric on the site, so a team that adjusts it mid-quarter loses the ability to compare that quarter's session count against the one before it.

Flowsery's real-time analytics records every session alongside the underlying event stream with no sampling, so a session boundary can be checked against the actual sequence of pageviews and events that produced it instead of trusting the count alone.

Frequently Asked Questions

What is the default session timeout in Google Analytics 4?

The default session timeout in GA4 is 30 minutes of inactivity, matching the default every other major analytics platform ships with. GA4 lets that value be raised in the Admin settings up to a maximum of 7 hours and 55 minutes.

Can a session timeout be shorter than 30 minutes?

Yes, GA4 allows the session timeout to be lowered to a minimum of 5 minutes. A short timeout suits sites where a multi-minute pause reliably means the visitor left, but it also means more brief gaps in ordinary browsing get counted as a new session.

Does changing the session timeout affect past data?

No. Changing the session timeout applies only to sessions recorded after the change is saved; every session already logged keeps the boundaries it was originally recorded with. Comparing data from before and after a timeout change means comparing two different measurement rules, not just two different time periods.

Why did my session count jump after I lowered the timeout?

Lowering the timeout closes sessions on shorter gaps than before, so pauses that used to stay inside one session, such as a visitor reading for 35 minutes under a 45-minute timeout, now split into two sessions under a 30-minute one. The traffic did not change; the rule for grouping it did.

Does a session timeout apply to session replay recordings too?

Not in the same way. A session timeout closes an analytics session for counting purposes, while a session replay tool decides separately how much of a visitor's activity to keep in one recorded video, and the two do not have to use the same cutoff. Check your specific tool's documentation, since some tools link the two settings together and others keep them independent.

Is there a maximum session timeout allowed?

GA4 caps the configurable session timeout at 7 hours and 55 minutes. Setting the timeout close to that maximum risks merging genuinely separate visits, such as a visitor who leaves a tab open overnight and returns the next morning, into a single session with an unrealistic duration.

Why do two sites with identical traffic show different session counts?

Two sites with identical traffic show different session counts when their session timeout settings differ. A site running the 5-minute minimum splits more visits into extra sessions than a site running the 7-hour-55-minute maximum, even with the same visitor behavior. Comparing raw session totals only makes sense when both sites use the same timeout value.

Does a shorter session timeout make bounce rate look worse?

A shorter timeout raises bounce rate. When a single-page visit runs past the timeout before the visitor's next action, the session records as a bounce even though the visitor would have continued under a longer window. Pages per session falls for the same reason, with no real change in what the visitor did.

Why did switching from Universal Analytics to GA4 change session totals?

Universal Analytics closed a session at midnight and whenever a visitor's traffic source changed, on top of the 30-minute inactivity rule. GA4 dropped both of those closing conditions and keeps only the inactivity timer, so a visitor who crossed midnight or clicked a campaign link mid-visit now counts as one session instead of two. That gap alone can lower session totals after a migration, before anyone touches the timeout setting.

What session timeout should a checkout flow use?

A checkout flow rarely needs a timeout longer than the 30-minute default. A gap that long in a short interactive flow usually means the visitor already left, so raising the timeout there just delays when abandoned sessions close. Longer timeouts fit documentation sites and long-form publishers, where readers routinely pause for several minutes without clicking.