Nobody clicks a button three times in a second because they're enjoying themselves. They do it because they expected something to happen and it didn't. That makes a rage click one of the most honest signals your product gives you — and one of the cheapest to collect, because your customers are already producing it.
What coview counts as a rage click
coview records a rage click when a visitor clicks the same element three or more times within one second. One burst becomes one event on the session's timeline, with the element it happened on and how many clicks there were — a button labelled “Continue” clicked four times reads as exactly that.
Sessions with rage clicks are flagged in the Sessions list, so you can filter to them instead of watching recordings at random.
A weekly routine that takes twenty minutes
- Filter. Open Sessions, turn on Rage clicks, and look at the last seven days.
- Group by element. Most weeks a handful of buttons account for most of the frustration. Note the element and the page.
- Watch three. For each group, watch three sessions from just before the burst. Jump straight to the marker on the timeline.
- Read the console. Look at the errors and failed requests next to the click. A
500on the request the button sends explains more than any guess. - File it with the evidence. Turn what you found into a ticket and keep the session on it, so engineering sees what you saw.
The three kinds you'll find
The button that is slow
The click worked, but nothing on the page said so. A spinner, a disabled state or a short message would have stopped the second and third click. These are often the quickest fixes on the list.
The button that is broken
The request behind it failed. The session shows the click, the failed request and usually an error in the console within the same second. This is a bug, and now it comes with a reproduction.
The thing that only looks clickable
An underlined word, a card with a shadow, an icon next to a label. People click it because it looks like it should do something. Either make it do that, or stop it looking like it would.
Make it a habit, not a project
The goal isn't zero rage clicks. It's that the same button never makes the list two weeks in a row.
Keep a short list in your team's channel: the element, the page, the session link and who picked it up. When a fix ships, check the next week's sessions for that element. If it's gone from the list, the fix worked — and you have the recordings from before to show why it mattered.
Rage clicks don't replace talking to customers. They tell you where to start the conversation — and when a customer is stuck right now, the five-message rule tells you when to stop typing and watch.
Session replay with rage-click filters is on every coview plan, including Free. Start a free workspace or compare plans.
We build coview: session replay, co-browsing, chat and calls for support teams. Questions about a post? Ask us from the contact page.