Bounce rate needs a platform-specific definition. In Google Analytics 4, it is the percentage of sessions that are not classified as engaged sessions. It is the inverse of engagement rate.
This differs from older interpretations based primarily on single-page visits. A person can read one page and still have an engaged session under GA4's rules.
How is it calculated?
GA4 bounce rate equals non-engaged sessions divided by total sessions, multiplied by 100. If 40 of 100 sessions are not engaged, the rate is 40%.
Use a consistent property and configuration for comparisons. Changes to key events or engagement settings can affect the result.
What is an engaged session?
GA4 uses criteria involving a time threshold, a key event or multiple page or screen views. The standard time criterion is commonly based on ten seconds, and settings can affect the implementation.
Check the current property configuration rather than assuming every report uses an identical definition.
Is a high bounce rate always bad?
No. The page's purpose matters. Someone may find a simple answer quickly, while another page may require a longer decision and several steps.
Investigate whether suitable visitors accomplish the intended task. The percentage alone cannot distinguish a satisfied reader from someone who encountered a poor experience.
What can cause a change?
Traffic composition, page content and technical behaviour can affect engagement. Measurement changes can also alter which sessions qualify.
Segment by relevant page groups and acquisition sources. A blended increase may reflect a new audience rather than a deterioration on existing pages.
How does it relate to conversion?
Bounce rate describes engagement classification. Conversion measures a defined outcome. A site can produce substantial engagement without useful enquiries.
Review the full journey, including the value of the resulting actions. Improving one ratio does not automatically improve the business result.
What should you investigate?
Check the landing page's clarity, task suitability and technical reliability. Then verify that tracking records the expected events.
Avoid adding artificial interactions merely to improve the metric. That can change the dashboard without improving the visitor's experience.
How should it be reported?
State the platform, definition, period and relevant segment. Include volumes and business outcomes where appropriate.
A useful report explains why the movement matters to a decision. A bounce-rate target without context can encourage changes that make the number look better while leaving the task unresolved.
Further reading
For reference, see the supporting documentation. Explore related explanations of Engagement rate, Google Analytics 4, Conversion rate.
A practical example
Illustrative example: a guide attracts readers who need a specific answer. The team reviews engagement and appropriate next steps, while checking that a change in key-event configuration has not distorted the comparison. It avoids assuming every short visit was unsuccessful.
Why it matters
Bounce rate can help identify questions about a journey. Clear definitions prevent outdated assumptions and metric-driven changes that do not help visitors.
