Frustration Score Available (v1)
A single value from 0 to 100 per session — it condenses the individual frustration signals into one number, so you can tell at a glance how smoothly a session (and, on average, your whole site) went.
Where in the dashboard
Frustration — the gauge sits at the top of the page: the average score over the selected window (7 / 30 / 90 days), its band, an inverted trend arrow (up = more frustration) and the 30-day trend line. Every session in Recordings also carries its own score.
Core concept
The score is computed server-side in the nightly pass — no ML, just a transparent, traceable rule over the six frustration signals of a session:
- Each signal has a fixed weight; the severity order is rage click → error click → dead click → quick back → U-turn → excessive scroll.
- A signal’s contribution grows log-dampened with its frequency — so ten rage clicks don’t count ten times as bad as one.
- Contributions are summed and capped at 100:
score = min(100, Σ contributions). - Because it is derived from the regular events, the score exists only for consented sessions; detected bots are excluded.
The gauge also shows the top signals by contribution — so you see not just how high the frustration is, but what it is made of.
The four bands
- Healthy (0–30) — hardly any friction, the site runs smoothly.
- Elevated (31–60) — noticeable friction, worth a look.
- High (61–80) — clear problems, worth digging into.
- Critical (81–100) — heavy friction, fix it urgently.
Related
- Frustration Signals — the six raw signals behind the score
- Session Recordings — replay a high-scoring session
- Filtering & Segmentation — narrow to sessions above a score threshold
- JS Error Tracking — the source behind the error-click contribution
Last updated:
Last updated on