At a glance
This card counts the dead clicks and rage clicks recorded on your cart and checkout pages over the last seven days. Those signals are direct conversion blockers: when a shopper clicks something that does nothing, or clicks the same spot in frustration, they are seconds away from abandoning. Watching this number keeps the most important pages on your site honest.
| What it counts | The number of dead-click and rage-click events recorded on cart and checkout pages over the window. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | Frustration on checkout-path pages directly blocks purchases, so even small counts can cost real orders. |
| Reading the value | Lower is better; any value above zero on cart or checkout pages is worth investigating. |
| Currency | count |
| Time window | 7D |
| Alert trigger | >0 on cart / checkout pages |
| Sentiment key | clr_checkout_path_frustration |
| Roles | owner, marketing |
Calculation
Microsoft Clarity records dead clicks and rage clicks per page from real shopper sessions. Vortex IQ sums those frustration signals across your cart and checkout pages over the window to give a single conversion-blocker count. See the At a glance table for the alert trigger and time window, and the worked example below for how it reads in practice.Worked example
A representative reading of Checkout-Path Frustration Signals for a typical merchant on Microsoft Clarity. Over a week a store logs 42 frustration signals on its checkout pages, up from a usual handful. The merchant opens Vortex Mind to trace them upstream and finds most are rage clicks on a discount-code field that silently rejects valid codes. They ask Ask Viq “which checkout element is generating the most frustration clicks this week?” in plain English, fix the field validation, and watch the count fall back toward zero over the following days.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_alert_conversion_drop | The real-time alert that fires when this count surges. |
clr_dead_click_pct | Site-wide dead click rate, for context beyond checkout. |
clr_rage_click_rate | Rage click rate, the second signal making up this count. |
frustration_signals_vs_cart_abandonment | Links checkout frustration to actual cart abandonment. |
clr_javascript_errors | JavaScript errors that often cause clicks to do nothing. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard insights for dead clicks and rage clicks, then filter heatmaps and recordings to your cart and checkout URLs. Confirm the period and any device or channel filters 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. |