At a glance
Rage Click Rate % is a frustration-signal metric tracked from FullStory data. A rage click is FullStory’s name for the pattern where a visitor clicks the same element repeatedly in quick succession, the classic tell that something looks interactive but is not responding. This card reports the share of sessions that contained at least one rage-click event. When it rises, a button, link, or control is broken, slow, or unresponsive, and visitors are hammering it in frustration. It is one of the most direct early-warning signals of a broken UI on a revenue path.
| What it counts | The percentage of FullStory sessions in the period that included one or more rage-click events, as detected by FullStory’s frustration-signal engine. |
| Sample type | Backend API data from FullStory, refreshed on the standard data refresh. |
| Why it matters | Rage clicks are a leading indicator of a broken or unresponsive interaction. A rising rate on checkout, add-to-cart, or navigation elements is a direct revenue risk and usually precedes a conversion dip. |
| Reading the value | Compare the current period to the prior period. Any sustained rise warrants a replay review of the affected sessions to find the offending element. |
| Currency | percent |
| Time window | 30D vsP |
| Alert trigger | >5% of sessions |
| Sentiment key | fs_rage_click_rate |
| Roles | owner, marketing |
Calculation
Calculated automatically from your FullStory data. FullStory flags a rage-click event when a visitor clicks the same region repeatedly within a short window; Vortex IQ divides the count of sessions containing at least one such event by total captured sessions for the period. 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 Rage Click Rate % for a typical merchant on FullStory. Say the store captured 12,000 sessions in the last 30 days and 780 of them contained a rage-click event. That is a rage click rate of 6.5%, above the 5% guardrail. Filtering the affected replays shows most rage clicks landing on the “Apply discount” field at checkout, which silently fails on mobile. The fix is a single front-end change, but without this card the merchant would only have seen an unexplained checkout conversion dip. For deeper investigation, use Vortex Mind to trace the upstream cause; for natural-language exploration, ask Ask Viq which pages carry the most rage clicks.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fs_dead_click_rate | Frustration sibling: clicks on elements that do nothing. |
fs_error_click_rate | Frustration sibling: clicks that trigger a JS error. |
fs_frustration_score | The composite frustration number that rage clicks feed into. |
fs_dead_click_hotspots | Names the exact elements receiving the most dead clicks. |
fs_worst_frustration_pages | Ranks pages by frustration so you know where to look first. |
Reconciling against the vendor’s own dashboard
Where to look in FullStory’s own dashboard: FullStory surfaces rage clicks under its frustration-signals reporting and as a searchable event when building segments. Confirm period boundaries and segment filters match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses 30-day rolling by default; FullStory dashboards may use calendar periods. | Variable | Match the period range. |
| Time zone. FullStory uses the account time zone; Vortex IQ aligns to the merchant reporting time zone. | Marginal | Confirm time zone match. |
| Segment scope. A FullStory segment may exclude bots or internal traffic that the Vortex IQ profile includes, or vice versa. | Variable | Match segment and filter settings. |