> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Cursor Thrashing Rate %, FullStory > Cursor Thrashing Rate % for FullStory stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Frustration Signals](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Cursor Thrashing Rate %** is a frustration-signal metric tracked from FullStory data. Thrashing is the erratic, back-and-forth mouse movement that signals a confused or lost visitor scanning a page for something they cannot find. FullStory detects the pattern from cursor telemetry. This card reports the share of sessions that contained it. A rising rate points to pages where the layout, labelling, or information hierarchy is failing to guide people to what they came for. | | | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The percentage of FullStory sessions in the period that contained erratic, thrashing cursor movement, as detected by FullStory. | | **Sample type** | Backend API data from FullStory, refreshed on the standard data refresh. | | **Why it matters** | Thrashing is a softer signal than a rage or error click, but it flags disorientation before the visitor gives up. It points to navigation and layout problems rather than broken code. | | **Reading the value** | Compare the current period to the prior period. Pair with the worst-frustration-pages card to find where confusion concentrates. | | **Currency** | percent | | **Time window** | `30D vsP` | | **Alert trigger** | `>5% of sessions` | | **Sentiment key** | `fs_thrashing_rate` | | **Roles** | owner, marketing | ## Calculation Calculated automatically from your FullStory data. FullStory flags a thrashing event from erratic cursor-movement patterns; Vortex IQ divides 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 **Cursor Thrashing Rate %** for a typical merchant on FullStory.* Say the rate climbs to 6% after a navigation redesign. Replays show desktop visitors sweeping the cursor across the header repeatedly, hunting for the search box that moved into a collapsed menu. Restoring a visible search field brings thrashing back under control. Without this card the redesign would have looked fine on conversion for a while before the slow drag showed up. For deeper investigation, use Vortex Mind to see which pages drive the thrashing; for natural-language exploration, ask Ask Viq where visitors look most lost. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | [`fs_dead_click_rate`](/nerve-centre/kpi-cards/fullstory/dead-click-rate) | Confused visitors often click things that do nothing. | | [`fs_rage_click_rate`](/nerve-centre/kpi-cards/fullstory/rage-click-rate) | Frustration sibling: repeated clicks on an unresponsive element. | | [`fs_worst_frustration_pages`](/nerve-centre/kpi-cards/fullstory/worst-frustration-pages) | Ranks pages by frustration so you know where to look first. | | [`fs_frustration_score`](/nerve-centre/kpi-cards/fullstory/avg-frustration-score) | The composite frustration number this feeds into. | ## Reconciling against the vendor's own dashboard **Where to look in FullStory's own dashboard:** FullStory surfaces cursor and movement frustration through its frustration-signal reporting and session search. 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. | | **Device mix.** Thrashing is a cursor signal, so a session base skewed toward touch devices will read lower. | Variable | Check the device split. | | **Segment scope.** A FullStory segment may narrow the sessions included relative to the Vortex IQ profile. | Variable | Match segment and filter settings. | **Cross-connector reconciliation:** complement with the dead-click and worst-frustration-pages cards for the full picture. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Cursor Thrashing 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: Does this apply to mobile?** Thrashing is a cursor signal, so it is most meaningful for desktop traffic. On touch devices the equivalent confusion shows up as dead clicks and erratic scrolling instead. **Q: Why does my FullStory dashboard show a different number?** The most common reasons are period-boundary differences, device mix, and segment scope. Match these settings before assuming a real divergence. **Q: Can I customise the alert threshold?** Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. The 5% default is a starting point; tune it to your own baseline. *** ### Tracked live in Vortex IQ Nerve Centre *Cursor Thrashing 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.