Frustration signals
Rage click tracking that turns frustration into a fix list
Rage click tracking detects moments when a visitor clicks the same spot several times in quick succession because nothing happens. UserExplorer flags rage clicks, dead clicks and error clicks in every session, ranks the elements that cause them and opens the replay at the exact second.
- Rage, dead and error clicks detected automatically
- Ranked list of elements by affected users
- Each signal opens the replay at the right moment
- Alerts when a new element starts causing frustration
Step 3 of 4
Verify your phone
Code not delivered. Try again.
Three signals
What rage clicks, dead clicks and error clicks mean
A rage click is a burst of clicks on one spot within a second or two. It usually means a button that responds slowly, a link that looks clickable and is not, or an action that fails silently.
A dead click is a single click that produces no change on the page, no navigation, no network request, no visible update. Dead clicks reveal images, headings and icons that users expect to open something. An error click is a click followed by a JavaScript error in the console.
Each signal is rare in one session and very telling across thousands. That is why UserExplorer aggregates them by element and shows them as a layer on click heatmaps as well as markers in the replay timeline.
Frustration report
A ranked list of what annoys your users most
Element ranking
Elements sorted by the number of users who rage or dead clicked them in the selected period.
Straight to the moment
Every row opens the replays with the player already at the frustration marker.
Errors attached
Error clicks show the console message and the failed request next to the click.
Device and browser split
See whether a problem exists only on one browser or screen size.
Trend after releases
Watch the count fall after a fix, or rise when a deploy breaks something.
AI grouping
The AI researcher groups similar signals and writes what users were trying to do.
Example
A typical find in the first week
In an example on sample data, the report ranks an "Apply" button on a discount field as the top rage click element on mobile. The replays show the button waits for a slow price check with no loading state, so visitors tap it five or six times and some leave checkout.
A spinner and a disabled state fix the behavior. The same check in form analytics shows whether the discount field still causes drop-off after the change.
412 sessions of 15,862 match, sorted by frustration
- Visitor 8F21, iPhone /pricing > /checkoutRage x6Error 04:12
- Visitor 2C77, Android /product > /checkoutRage x4 02:48
- Visitor A913, iPhone /checkoutDead clickU-turn 01:35
- Visitor 51D0, iPad /cart > /checkoutRage x3 03:02
Sample data
Setup
Frustration tracking is on from the first session
-
Step 1
Add the snippet
Rage, dead and error clicks are detected from the standard recording, nothing extra to configure.
-
Step 2
Open the report
Choose a page, segment and date range to see the ranked element list.
-
Step 3
Watch the evidence
Play the replays from the markers to understand what users expected.
-
Step 4
Set an alert
Get notified when an element passes a threshold of affected users.
Beyond clicks
Connect frustration to conversion and revenue
A frustrating element matters more when it sits on a step that earns money. Filter the report by users who later left a funnel, or by customers on a paid plan, and the list reorders itself by business impact.
Frustration signals also appear on each user profile, so support can see that a customer who just opened a ticket hit three dead clicks on the export button the day before.
FAQ
Questions teams ask before they start
What is rage click tracking?
Rage click tracking detects bursts of repeated clicks on the same spot, a sign that the visitor expected a response and did not get one, and collects them so you can see which elements frustrate users most.
What are dead clicks?
Dead clicks are clicks that produce no visible change, navigation or request. They often land on images, text or icons that look interactive but are not.
What is an error click?
A click followed by a JavaScript error. UserExplorer shows the error message and the failed request next to the click in the replay.
Do I need to set thresholds?
No. Sensible defaults detect rage and dead clicks out of the box. You can adjust sensitivity per project and exclude elements such as carousels where repeated clicks are normal.
Is rage click tracking included in every plan?
Yes. Rage, dead and error clicks are part of every plan, from Startup. See pricing.
How does this compare with Microsoft Clarity or Hotjar?
Both offer rage click detection. UserExplorer adds error clicks, a ranked element report and AI grouping linked to funnels and profiles. Check each vendor for its current features.
See the reason behind your numbers this week
Install one snippet, record real sessions with masking on by default, and let the AI researcher show you what to fix first.