Engagement
Rage click
Also called frustration click.
Rage click is rapid repeated clicking on the same control, used as a frustration signal.
How it is measured
The script flags three or more clicks within about a second inside a small radius, then logs the element and URL. A threshold that is too loose catches double-clicks, one that is too strict misses slow frustration.
Tarsier does not detect rage clicks. You can wrap one important button with your own counter and send an event when it trips.
Worked example
An online pharmacy's refill button takes four seconds to respond. In one week it takes 640 rage clicks, and some customers submit twice.
The developers add a loading state and disable the button after the first click. Duplicate orders disappear.
How it differs
A rage click is a burst. A dead click is a single click with no response. An error click is tied to an error. Rage is the symptom; slowness or a bug is the cause.
Common errors
Counting double-clicks as rage. Missing mobile taps. Reading the number as users. Ignoring slow networks. Fixing the button and not the delay behind it.
In practice
List the elements with the most rage clicks and test each on a slow connection.