At a glance
Frustration Signal Volume Anomaly is the site-wide watchdog for frustration. It fires when the volume of rage clicks and error clicks jumps well above the normal baseline, statistically, more than two standard deviations out. Where the checkout-spike alert watches one path, this one watches the whole site for any sudden surge in friction. It is the alert that catches a broken interaction you did not know to look for, anywhere a recent change might have introduced one.
| What it counts | Real-time alerts raised when site-wide rage-click or error-click volume exceeds roughly two standard deviations above the rolling baseline. |
| Sample type | Backend API data from FullStory, evaluated continuously against the alert rule. |
| Why it matters | It is the broad early warning for on-site breakage. A surge in frustration volume usually means a deploy, a third-party script, or an outage just degraded the experience somewhere. |
| Reading the value | Each entry is a fired alert. Use the worst-pages and hotspots cards to localise the surge, then open the affected replays. |
| Currency | count |
| Time window | RT |
| Alert trigger | rage / error click volume >2sigma vs baseline |
| Sentiment key | fs_alert_event_volume_drop |
| Roles | owner, marketing |
Calculation
Calculated automatically from your FullStory data. Vortex IQ tracks the rolling baseline of rage-click and error-click volume and raises an alert when current volume exceeds roughly two standard deviations above it. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Frustration Signal Volume Anomaly for a typical merchant on FullStory. Suppose an alert fires on a Friday evening. Site-wide error clicks have tripled against the baseline. The surge is not on checkout, so the checkout-spike alert stayed quiet, but a marketing-landing template went live with a broken video embed throwing console errors on every click. The team pulls the embed and volume normalises. This alert caught a problem outside the usual high-value paths that no single-page watchdog would have flagged. For deeper investigation, use Vortex Mind to localise the surge; for natural-language exploration, ask Ask Viq where frustration spiked.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fs_alert_conversion_drop | The checkout-specific frustration alert. |
fs_rage_click_rate | One half of the volume this alert watches. |
fs_error_click_rate | The other half of the volume this alert watches. |
fs_worst_frustration_pages | Localises a site-wide surge to specific pages. |
fs_frustration_score | The composite that a volume surge moves. |
Reconciling against the vendor’s own dashboard
Where to look in FullStory’s own dashboard: FullStory supports alerting on frustration-signal volume. To reconcile, compare the Vortex IQ baseline window and sigma sensitivity against any equivalent FullStory alert configuration. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Baseline window. A longer or shorter rolling baseline changes when an anomaly registers. | Variable | Align the baseline window. |
| Sensitivity. The sigma multiplier sets how extreme a surge must be to fire. | Variable | Compare the sensitivity setting. |
| Signal scope. Whether the alert includes dead clicks alongside rage and error clicks affects volume. | Variable | Confirm which signals are counted. |