Bounces, engagement, rage

Three behavioural signals Replayful surfaces, and exactly how they're defined. Knowing the thresholds keeps you from arguing with the dashboard.

Bounce

A session is a bounce if either:

• it has ≤ 3 events, or
• its duration is under 10 seconds.

Either condition triggers a bounce label. In practice this means "landed, looked, left", no scroll, no click, no meaningful engagement. The two thresholds together catch both bot drive-bys and humans who hit back instantly.

Engagement (the inverse of bounce)

Anything that isn't a bounce. Engaged sessions have more than 3 events and stayed for at least 10 seconds. The Engagement filter on the sessions toolbar (Only engaged) hides everything that bounced.

Rage clicks

A rage click is detected when 3 or more clicks land within a 30-pixel radius of each other in quick succession. The tell-tale "why isn't this button working" pattern.

Replayful counts them two ways:

• Total rage clicks, every click in a cluster, so a 7-click frustration burst counts as 7.
• Frustrated sessions, number of distinct sessions that contained any rage cluster.

The Analytics overview surfaces both. The KPI turns amber when rage-affected sessions exceed 5% of total, at that point frustration is systemic, not noise.

Drilling in

The bounce % cells on Top Ads and Traffic Sources are clickable and take you to the matching sessions with bounce = only pre-filtered. Use this to investigate whya cohort bounces, usually it's landing-page mismatch, slow first paint, or an in-app webview rendering poorly.