What is a rage click?

A rage click is a rapid series of clicks or taps on the same element or spot, made by a user whose action produced no visible response, and it is one of the most reliable signals of frustration in a session recording.

Why it matters

Nobody clicks a button three times in a second because it worked. Rage clicks point at buttons whose handler failed, links that look clickable but are not, overlays that swallowed the event, or a page that simply froze. They are cheap to detect and strongly correlated with abandonment.

On their own, rage clicks are a count. Paired with replay they become a diagnosis: open the session, jump to the burst, and watch what the user expected to happen. That is the difference between analytics and replay. A dead click is the quieter sibling of the same problem.

How AnyReplay handles it

The AnyReplay web SDK detects a rage click as 3 clicks within 1000 ms inside a 30 px radius, at record time in the browser. The chunk containing the burst is flagged hasRageClick, alongside hasError and pageCount, so the dashboard can surface sessions with frustration without decoding them. A reviewer filters the session list to flagged sessions, opens one and scrubs to the burst. Because the recording is a DOM recording rather than video, the element under the cursor is known, not guessed from pixels. The QA and bug reproduction use case shows a typical workflow.