Bounce Rate Calculator

Background.

Ask two analysts for the same site's bounce rate and you can get two correct answers eight points apart. Google changed what the word means when Google Analytics 4 replaced Universal Analytics, whose standard properties stopped processing data in July 2023, and the old figure and the new one count different visits as bounces.

Universal Analytics called a session a bounce when it sent a single request to the Analytics server: one pageview and nothing after it. Bounce rate was single-page sessions divided by all sessions. GA4 works from the other end. It first decides which sessions were engaged — longer than 10 seconds, or with a key event, or with two or more page or screen views — and everything left over is a bounce. A reader who spends four minutes on one article was a bounce under the old rule and is engaged under the new one, so the GA4 number usually comes out lower for the same traffic.

Choose the definition your data came from, enter session counts from one property and one date range, and you get the rate, its complement, the session counts behind both, and a short note spelling out what the figure means. The target field turns a goal like "get under 55%" into a count of visits: how many more sessions would have to stop bouncing, with traffic unchanged, to get there.

One caution before you compare your figure with a competitor's or an agency's: GA4's 10-second bar is a default, and each property can raise it. Identical visitors on two sites can therefore produce two different GA4 bounce rates.

What is bounce rate calculator?

Bounce rate is the percentage of sessions that ended without whatever the analytics tool counts as follow-up activity. In Universal Analytics that meant a session with exactly one hit sent to Google's servers, usually a lone pageview. In GA4 it is the share of sessions that were not engaged, where engaged means lasting longer than 10 seconds, triggering a key event, or recording at least two page or screen views. Both versions divide by sessions, and a GA4 session closes after 30 minutes without activity unless the property owner has changed the timeout, which can be set as high as 7 hours 55 minutes. Because every GA4 session is either engaged or not, bounce rate and engagement rate always add up to exactly 100%.

How to use this calculator.

1. 01Under "Which definition?" pick GA4 for anything exported from a GA4 property, and Universal Analytics only for archived reports from the old platform. The field for the other definition is ignored.
2. 02Enter total sessions for the period, then engaged sessions (GA4) or single-page sessions (Universal Analytics), taken from the same property, the same date range and the same filters. Neither count can exceed total sessions.
3. 03If a report gives you only a bounce rate and total sessions, rebuild the counts first: 62% of 48,000 sessions is 29,760 bounced, which leaves 18,240 engaged sessions to type in.
4. 04Set a target bounce rate to see the gap in visits rather than percentage points. It does not change the rate itself; a target of 0% simply asks for every bounced session.
5. 05Read the "What this number means" line before you put the figure in a report, so the definition and the adjustable GA4 threshold travel with it.

The formula.

Universal Analytics: BR = S₁ ÷ S × 100, where S₁ is single-page sessions and S is all sessions. GA4: BR = (1 − E ÷ S) × 100, where E is engaged sessions, which is the same as dividing the non-engaged sessions, S − E, by S. In both modes the engagement or non-bounce rate is 100 − BR, because each session lands on exactly one side of the line.

The target works in sessions instead of percentages. Holding the bounce rate at T% means at least S × (1 − T ÷ 100) sessions must not bounce. Subtract the sessions that already did not bounce and you have the number still to win over; if that comes out negative the target is already met, and the answer shown is 0 rather than a negative count.

Two consequences follow. The required number of non-bounced sessions depends only on total traffic and the target, so each session you convert cuts the shortfall by exactly one. And because the same traffic yields fewer non-bounced sessions under the Universal Analytics rule, the same target always looks further away when measured the old way.

A worked example.

Frequently asked questions.

References& sources.

1. [1]Google Analytics Help, "[GA4] Engagement rate and bounce rate" (article 12195621, current edition, retrieved 2026-07-29). Source of the GA4 definitions used on this page: an engaged session is "a session that meets any of the following criteria: Lasts longer than 10 seconds, Has a key event, [or] Has 2 or more screen or page views"; engagement rate is "the percentage of engaged sessions on your website or mobile app"; bounce rate is "the percentage of sessions that were not engaged". Publicly accessible.
2. [2]Google Analytics Help, "[UA] Bounce rate" (article 1009409, retrieved 2026-07-29; the page is explicitly flagged "You are viewing a legacy article about Universal Analytics"). Source of the legacy definition: "A bounce is a single-page session on your site … a session that triggers only a single request to the Analytics server", and "Bounce rate is single-page sessions divided by all sessions". Also the source of the statement that a high bounce rate is "perfectly normal" for single-page sites and blogs. Archived-status legacy documentation, still publicly accessible.
3. [3]Google Tag Manager Help, "Configure your Google tag settings" (article 12131703, current edition, retrieved 2026-07-29). Consulted as an independent second authority on whether GA4's engagement threshold is a fixed constant; it is not — "The default threshold for engagement time is 10 seconds but can be adjusted here." This is why the page treats the 10 seconds as a per-property setting and says so beside the result. Publicly accessible.
4. [4]Google Analytics Help, "[GA4] Session" (article 12798876, current edition, retrieved 2026-07-29). Restates the engaged-session rule — "An engaged session is a session that lasts longer than 10 seconds, has a key event, or has at least 2 pageviews or screenviews" — and documents the separate, configurable session timeout, noting that "the maximum value for 'Adjust session timeout' is 7 hours and 55 minutes". Used to confirm the engagement rule against a second Google page rather than relying on one article. Publicly accessible.
5. [5]Google Analytics Help, "[GA4] About Analytics sessions" (article 9191807, current edition, retrieved 2026-07-29). Defines the denominator both modes divide by: "A session is a period of time during which a user interacts with your website or app", which "ends or times out after 30 minutes of user inactivity". Publicly accessible.