Docs Visitor insight
View as MarkdownRage clicks
Clerion finds rage clicks with no setup. When a visitor clicks the same element three or more times, each click within 0.7 seconds of the last, the snippet records one rage click with the page and the element. You see them on the Errors page in a card called Rage clicks, by page and element, with how many bursts and how many visits.
Before you start
The Clerion snippet must be on the page. If it is, rage clicks are already being recorded: the snippet is served by Clerion, so every site picked this up without a change. If it is not installed, set up Clerion first.
Read the card
Open your site, go to Observability, then Errors, and scroll below the event log to Rage clicks:
| Column | What it means |
|---|---|
| Element | The element that was clicked, as a short CSS selector: its tag, its id after #, and up to two classes after .. The page is beside it. |
| Bursts | How many times someone clicked it three or more times in a row. |
| Sessions | How many different visits did it. Rows are sorted by this. |
The briefing and Ask Clerion see the same rows, so "what frustrates visitors on checkout?" is answered with the element.
How a rage click is counted
| Rule | Detail |
|---|---|
| Three clicks | Three or more clicks on the same element, each within 0.7 seconds of the one before, make one burst. Ten clicks in a row are still one burst. |
| Any element | Images, labels, plain text and icons count, not only links and buttons. That is how an element that looks clickable and does nothing shows up. |
| The element itself | The exact element under the pointer is recorded, so a click on the icon inside a button names the icon. |
| Not sampled like clicks | Ordinary clicks are sampled to keep traffic light; bursts are not, so every one is counted. |
| Not a goal | Bursts are recorded as rage_click, which never shows up as a custom event or a conversion. |
What to do with a rage click
Most rows fall into one of three cases:
- It looks clickable and is not. An image in a product gallery, a price, a card with a hover effect. Make it do what people expect, or stop it looking like a control.
- It is clickable and too slow. A button that waits on the network with no sign it heard the click. Show that it is working at once, and disable it until it finishes.
- It is broken. A control that throws a script error. Check the event log on the same page for an error at the same spot.
Make the elements easy to name
A selector such as div.card is hard to place on a busy page. Give the elements people interact with an id or a meaningful class, for example button#apply-coupon or span.delivery-option, and the card names them in a way you can find in your code.
Limits
| Limit | What it means for you |
|---|---|
| From now on | Bursts are recorded from the day the updated snippet reached your site. There is no history before that. |
| Only when tracking runs | Visitors with Global Privacy Control or Do Not Track on, or who declined the consent banner, are not counted. |
| Twelve rows | The card lists the twelve elements with the most visits. |
| Very busy sites | The card reads up to 150,000 events per site for the range. Above that it says so, and a shorter range can bring it back. |
Questions
Do I need to turn rage clicks on?
No. The snippet already records them on every site.
Does this record what visitors type or read?
No. Only the element's tag, id and classes, and where on the page the click landed. No text from the page and no form contents.
What is the difference between a rage click and a dead click?
A rage click is repeated clicking on one element. A dead click is a single click that does nothing. Clerion records rage clicks; an element that keeps getting rage-clicked is usually a dead click people tried more than once.
Why is the same element listed on two pages?
The card counts by page and element together, so a header button that frustrates people on two pages appears on both.