Prompt
How do I spot rage clicks and dead clicks in session replay?
Latest observation
Oct 30, 2026
OpenAI APIWeb search: off
To spot rage clicks and dead clicks in session replay, look for repeated user frustration on the same spot and clicks that don’t lead to any visible response.
Rage clicks
A rage click is usually a burst of rapid clicks in the same area, often because the user expects something to happen but it doesn’t.
What it looks like in replay:
- 3+ clicks in the same location within a short time
- Cursor rapidly clicking the same button, icon, or text
- User pauses, then clicks again more aggressively
- Often followed by scrolling away, abandoning the task, or clicking elsewhere
Common causes:
- Button is broken or unresponsive
- User is trying to click something non-clickable
- Slow loading makes the UI feel frozen
- Misleading affordance, like text that looks like a link but isn’t
Dead clicks
A dead click is a click with no apparent effect.
What it looks like in replay:
- User clicks an element and nothing visible changes
- No navigation, modal, animation, or state change
- The element may not actually be interactive
- Sometimes the UI responds later, but not immediately enough for the user to notice
Common causes:
- Broken interaction
- Click intercepted by overlay or invisible element
- Missing state update
- User expects a tooltip, dropdown, or page transition that never appears
In session replay, watch for:
- Repeated clicking in the same area
- Hovering and then clicking with no response
- Clicks on elements that aren’t wired up
- Abrupt abandonment after clicks
- Back-and-forth behavior that suggests confusion
Best practices
- Use event markers if your replay tool labels rage/dead clicks automatically
- Compare replay with DOM or network events to confirm whether the UI responded
- Check if the element was visible, enabled, and actually clickable
- Look for patterns across multiple sessions, not just one replay
If you want, I can also give you a checklist for manually reviewing replays or show how rage/dead clicks are typically detected programmatically.