At a glance
This is a real-time alert that fires the moment frustration signals (dead clicks, rage clicks, or JavaScript errors) surge on your cart and checkout pages. Because these pages sit directly on the path to revenue, a spike here often means shoppers are stuck right where it hurts most. Catching it within minutes, rather than at the end of the day, can be the difference between a quick fix and a lost trading session.
| What it counts | The number of frustration-signal events detected on cart and checkout pages that have crossed the spike trigger in the current 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 pages is the most direct cause of abandoned orders and lost revenue. |
| Reading the value | A non-zero or rising value means a frustration spike is active right now and needs investigation; zero means checkout behaviour looks normal. |
| Currency | count |
| Time window | RT |
| Alert trigger | frustration signals on checkout pages spike |
| Sentiment key | clr_alert_conversion_drop |
| Roles | owner, marketing |
Calculation
Microsoft Clarity continuously detects frustration signals (dead clicks, rage clicks, and JavaScript errors) per page and per session. Vortex IQ watches the subset of those signals occurring on cart and checkout pages and raises this alert when their volume crosses the spike trigger relative to the recent baseline. See the At a glance table for the trigger and time window, and the worked example below for how it reads in practice.Worked example
A representative reading of Checkout-Path Frustration Spike for a typical merchant on Microsoft Clarity. On a normal afternoon a store sees a handful of frustration signals on its checkout step. After a theme update, Clarity starts logging dozens of rage clicks on the “Place order” button within ten minutes, and this alert fires. The merchant opens Vortex Mind to trace the spike upstream and finds a broken payment widget introduced by the deploy, then uses Ask Viq to ask “which checkout step is generating the most rage clicks right now?” in plain English and rolls back the change before the trading day is lost.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_checkout_path_frustration | The underlying 7-day count of frustration signals on checkout pages that this alert watches. |
clr_alert_event_volume_drop | Site-wide frustration spike alert, to see whether the problem is checkout-specific or everywhere. |
clr_dead_click_pct | The share of sessions with a dead click, a key component of checkout frustration. |
clr_rage_click_rate | Rage click rate, the other major component driving this spike. |
clr_alert_tracking_broken | Rules out a tracking break when checkout signals suddenly look abnormal. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Open the Clarity Dashboard insights for dead clicks, rage clicks, and JavaScript errors, then filter 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. |