At a glance
Rage Click Rate % is the share of sessions where a visitor clicked the same element rapidly and repeatedly, which Microsoft Clarity flags as a strong frustration signal. It usually means something looked clickable but did not work, or did not respond fast enough. A rising rate is an early, vivid warning that part of your experience is broken.
| What it counts | The percentage of Clarity-captured sessions containing rapid repeated clicks on the same element. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | Rage clicks are a direct signal of frustration, often pointing to broken or unresponsive elements. |
| Reading the value | Lower is better; a rise versus the prior period flags a UX or technical fault worth investigating fast. |
| Currency | percent |
| Time window | 30D vsP |
| Alert trigger | >5% of sessions |
| Sentiment key | clr_rage_click_pct |
| Roles | owner, marketing |
Calculation
Microsoft Clarity detects rapid repeated clicks on the same element within a session and flags those as rage clicks, then expresses the flagged sessions as a share of captured sessions over the window. Vortex IQ reads that rate and compares it to the prior period. See At a glance for the time window and the worked example below for a typical reading.Worked example
A representative reading of Rage Click Rate % for a typical merchant on Microsoft Clarity. A store saw rage clicks jump from 3% to 8% of sessions over 30 days, tripping the 5% alert. Opening the heatmaps, the merchant found visitors repeatedly clicking an “Apply discount” field that had stopped responding after a theme update. They used Vortex Mind to trace the spike to the deployment date, then asked Ask Viq in plain English which pages and elements drew the most rage clicks so engineering could fix the highest-impact one first.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_dead_click_rate | Dead clicks and rage clicks often share the same broken element. |
clr_javascript_errors | Errors frequently cause the unresponsiveness behind rage clicks. |
clr_frustration_signals_vs_cart_abandonment | Connects frustration to lost carts. |
clr_checkout_path_frustration_signals | Isolates rage clicks happening in the checkout flow. |
clr_health_score | Shows how rage clicks pull down overall UX health. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard insights for the rage click signal, or filter recordings and heatmaps to sessions flagged for rage clicks. Confirm the period and filter settings match the Vortex IQ profile. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses rolling windows by default; Clarity may use calendar periods. | Variable | Match the period range. |
| Sampling. Clarity may sample sessions on high-traffic sites; Vortex IQ reads what Clarity exposes. | Variable | Allow for sampling on busy stores. |
| Filter scope. Profile-level filters (device, channel, bot exclusion) may narrow the Vortex IQ view. | Variable | Match filter settings. |