Error Click Rate %, FullStory

Error Click Rate % for FullStory stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Frustration Signals

At a glance

Error Click Rate % is a frustration-signal metric tracked from FullStory data. An error click is a click that coincides with a console or JavaScript error firing in the page. Unlike a dead click or a rage click, this one carries hard technical evidence: the visitor interacted with something and the code threw. This card reports the share of sessions containing at least one error click. It is the closest FullStory gets to handing engineering a reproducible bug, with the exact replay attached.

What it counts	The percentage of FullStory sessions in the period in which a click coincided with a logged console or JavaScript error.
Sample type	Backend API data from FullStory, refreshed on the standard data refresh.
Why it matters	Error clicks are direct evidence of a broken interaction, not just a confusing one. Each affected session is a reproducible defect with the replay attached, which is gold for the engineering backlog.
Reading the value	Compare the current period to the prior period. A sudden rise usually maps to a recent deploy; pull the affected replays and check the release timeline.
Currency	percent
Time window	30D vsP
Alert trigger	>3% of sessions
Sentiment key	fs_error_click_rate
Roles	owner, marketing

Calculation

Calculated automatically from your FullStory data. FullStory flags an error-click event when a click is followed by a captured console or script error; Vortex IQ divides the count of sessions with 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 Error Click Rate % for a typical merchant on FullStory. Imagine the error click rate jumps from 1.2% to 4.5% overnight, breaching the 3% guardrail. The spike lines up with a Tuesday theme deploy. Opening three affected replays shows the same console error firing on the “Add to cart” button for variant products. Engineering rolls back the change and the rate returns to baseline within a day. Without this card the defect would have surfaced only as a slow bleed in add-to-cart conversion. For deeper investigation, use Vortex Mind to correlate the spike with the deploy; for natural-language exploration, ask Ask Viq which pages threw the most errors.

Sibling cards merchants should reference together

Card	Why merchants reach for it
fs_rage_click_rate	Frustration sibling: repeated clicks on an unresponsive element.
fs_dead_click_rate	Frustration sibling: clicks on elements that do nothing.
fs_frustration_score	The composite frustration number that error clicks feed into.
fs_high_frustration_sessions	The prioritised replay queue where error-click sessions surface.
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 error clicks under its frustration-signals reporting and exposes the underlying console errors on each session replay. 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 bot or internal traffic the Vortex IQ profile includes.	Variable	Match segment and filter settings.

Cross-connector reconciliation: complement with the rage-click and dead-click cards for the full frustration picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Error Click Rate % update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard.

Q: Do all console errors count? Only errors that coincide with a click are counted here, since the goal is to surface broken interactions rather than every background warning. Benign third-party script noise can still inflate the figure, so review the replays.

Q: Why does my FullStory dashboard show a different number? The most common reasons are period-boundary differences, time-zone alignment, and segment scope. Match these settings before assuming a real divergence.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. The 3% default is a starting point; tune it to your own baseline.

---

Tracked live in Vortex IQ Nerve Centre

Error Click Rate % is one of hundreds of KPI pulses Vortex IQ tracks across FullStory and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.