> ## 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. # Worst Frustration Pages, FullStory > Worst Frustration Pages 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:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Page Analysis](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Worst Frustration Pages** ranks your pages by frustration score so you know exactly where to focus UX work first. Where the frustration gauges tell you the site-wide level, this table tells you the address. Each row is a page with its frustration score and usually the volume behind it, so you can weigh a high-frustration page against how many visitors it affects. It turns "the site feels frustrating" into a prioritised, page-by-page worklist. | | | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The pages with the highest frustration scores in the period, ranked, drawn from FullStory's frustration signals per page. | | **Sample type** | Backend API data from FullStory, refreshed on the standard data refresh. | | **Why it matters** | It converts a site-wide score into a ranked worklist. Fixing the top few pages usually moves the overall frustration and health numbers the most for the least effort. | | **Reading the value** | Read top down, but weigh score against traffic: a slightly less frustrating page with ten times the visitors may be the better fix. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `-` | | **Sentiment key** | `fs_worst_frustration_pages` | | **Roles** | owner, marketing | ## Calculation Calculated automatically from your FullStory data. Vortex IQ aggregates FullStory frustration signals by page, scores each page, and ranks them 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 **Worst Frustration Pages** for a typical merchant on FullStory.* The top row might be a specific product template with a high frustration score driven by dead clicks on its variant selector, the second the cart page, the third a collection filter. The product template is the priority because it spans hundreds of SKUs, so one fix to the shared template lifts every product page at once. For deeper investigation, use Vortex Mind to see which signal dominates each page; for natural-language exploration, ask Ask Viq which page to fix first. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | | [`fs_dead_click_hotspots`](/nerve-centre/kpi-cards/fullstory/dead-click-hotspots-by-element) | Drills from a frustrating page to the exact element. | | [`fs_frustration_score`](/nerve-centre/kpi-cards/fullstory/avg-frustration-score) | The site-wide score this table breaks down by page. | | [`fs_rage_click_rate`](/nerve-centre/kpi-cards/fullstory/rage-click-rate) | A common driver of a high page score. | | [`fs_checkout_path_frustration`](/nerve-centre/kpi-cards/fullstory/checkout-path-frustration-events) | The checkout-specific view when checkout tops the list. | | [`fs_xc_landing_page_perf_vs_bounce`](/nerve-centre/kpi-cards/fullstory/landing-page-performance-vs-frustration) | Ties frustrating pages to performance. | ## Reconciling against the vendor's own dashboard **Where to look in FullStory's own dashboard:** In FullStory, page-level frustration is visible through its page reporting and by segmenting frustration signals by URL. Confirm the period and page grouping match the Vortex IQ profile to reconcile cleanly. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------ | | **Page grouping.** Templated pages may be grouped or kept distinct differently between the two views. | Variable | Align the URL grouping. | | **Period boundary.** Vortex IQ uses 30-day rolling by default; FullStory dashboards may use calendar periods. | Variable | Match the period range. | | **Score weighting.** How signals combine into a page score can weight differently from a hand-built view. | Variable | Compare the component signals. | **Cross-connector reconciliation:** complement with the dead-click hotspots and frustration-score cards. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Worst Frustration Pages 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: Should I always fix the top row first?** Not blindly. Weigh score against traffic and revenue. A mid-ranked page on a high-value path can be a better fix than the single most frustrating but rarely visited page. **Q: Why does my FullStory dashboard show a different number?** The most common reasons are page grouping, period boundaries, and score weighting. Match these before assuming a real divergence. **Q: Can I customise the alert threshold?** This is a ranked table rather than a single threshold metric, but the underlying frustration sensitivity is configurable per profile in the Sensitivity tab. *** ### Tracked live in Vortex IQ Nerve Centre *Worst Frustration Pages* 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.