At a glance
Checkout-Path Frustration Spike is the real-time alert that fires when frustration events on cart and checkout pages surge within a short window. It is the watchdog version of the checkout-frustration metric: instead of waiting for you to open the dashboard, it raises an alert the moment friction at the point of purchase jumps. Because checkout is where money changes hands, this is one of the alerts worth waking up for, a sudden spike usually means a deploy or third-party script just broke the buy flow.
| What it counts | Real-time alerts raised when frustration-signal events on checkout and cart pages spike within a one-hour window, listed as they occur. |
| Sample type | Backend API data from FullStory, evaluated continuously against the alert rule. |
| Why it matters | A spike on the checkout path is a live revenue leak. Catching it within the hour, rather than at the next dashboard review, can save a day’s worth of lost orders. |
| Reading the value | Each entry is a fired alert. Open the linked sessions immediately, the spike almost always traces to one broken control or a recent change. |
| Currency | count |
| Time window | RT |
| Alert trigger | frustration events on checkout pages spike in 1h |
| Sentiment key | fs_alert_conversion_drop |
| Roles | owner, marketing |
Calculation
Calculated automatically from your FullStory data. Vortex IQ watches the rate of frustration-signal events on checkout and cart URLs and raises an alert when it spikes against the recent baseline inside a one-hour window. 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 Checkout-Path Frustration Spike for a typical merchant on FullStory. Suppose an alert fires at 14:10 on a Tuesday. Checkout frustration events jumped from a trickle to dozens in under an hour, right after a payment-widget update went live. Opening the linked replays shows the card field failing to render on Safari. The team rolls back the widget within 20 minutes. Without the alert the breakage would have run until the next morning’s report, costing a full afternoon of checkouts. For deeper investigation, use Vortex Mind to tie the spike to the deploy; for natural-language exploration, ask Ask Viq what triggered the alert.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fs_checkout_path_frustration | The underlying metric this alert watches. |
fs_alert_event_volume_drop | The site-wide frustration-volume alert. |
fs_error_click_rate | A spike often shows up as error clicks. |
fs_high_frustration_sessions | Where the affected sessions land for review. |
ful_cart_abandonment_rate | The downstream commerce impact. |
Reconciling against the vendor’s own dashboard
Where to look in FullStory’s own dashboard: FullStory supports its own alerting on frustration signals and segments. To reconcile, compare the Vortex IQ alert window and checkout URL definition against any equivalent FullStory alert or saved segment. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Window length. A one-hour spike window will read differently from a daily FullStory alert. | Variable | Align the evaluation window. |
| Checkout URL pattern. Which URLs count as checkout must match. | Variable | Align the URL definition. |
| Baseline method. How the “normal” rate is computed affects when a spike triggers. | Variable | Compare the baseline logic. |