At a glance
Clarity UX Health Score is a composite 0-100 headline number that blends frustration signals, scroll depth, and quick-backs into a single read on how healthy your on-site experience is. It exists so an owner can glance once and know whether the experience is helping or hurting. A score sliding toward the alert line is your cue to dig into the underlying behaviour cards before it shows up in revenue.
| What it counts | A composite 0-100 score combining frustration signals, scroll depth, and quick-back behaviour from Clarity. |
| Sample type | Behavioural session data from Microsoft Clarity (heatmaps and session recordings), refreshed on the standard data refresh. |
| Why it matters | It gives leadership one number to track UX health without reading every behaviour signal individually. |
| Reading the value | Higher is better on a 0-100 scale; a drop below the threshold signals deteriorating experience worth investigating. |
| Currency | count |
| Time window | RT/7D |
| Alert trigger | <70 |
| Sentiment key | clr_health_score |
| Roles | owner, marketing |
Calculation
Vortex IQ blends several Clarity behavioural signals - including frustration indicators, how far visitors scroll, and how quickly they leave - into a single 0-100 composite, where higher reflects a healthier experience. The exact weighting is tuned per profile. See At a glance for the time window and the worked example below for a typical reading.Worked example
A representative reading of Clarity UX Health Score for a typical merchant on Microsoft Clarity. A store’s score dropped from 82 to 66 over a week, breaching the 70 alert. Drilling in, the owner saw rage clicks and quick-backs had both risen after a checkout redesign. They used Vortex Mind to trace which underlying signals pulled the composite down and when, then asked Ask Viq in plain English to summarise the worst-affected pages so the team could roll back the change.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
clr_rage_click_pct | A key frustration input behind the composite score. |
clr_quick_back_rate | Quick-backs are a core driver of the health score. |
clr_avg_scroll_depth | Scroll depth feeds the engagement side of the composite. |
clr_javascript_errors | Errors often explain a sudden health-score drop. |
clr_frustration_signal_spike | Flags the moment frustration jumped and dragged the score down. |
Reconciling against Microsoft Clarity
Where to look in Microsoft Clarity’s own dashboard: Clarity does not publish this exact composite, so reconcile by reviewing the component signals (frustration insights, scroll depth, and quick navigation behaviour) in the Clarity Dashboard insights. 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. |