> ## 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.

# Session Frustration vs Cart Abandonment, FullStory

> Session Frustration vs Cart Abandonment 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:** [Cross-Channel: Revenue at Risk](/nerve-centre/connectors#connectors-by-type)

## At a glance

> **Session Frustration vs Cart Abandonment** is a cross-channel card that overlays FullStory's session frustration against your store's cart abandonment rate over time. The hypothesis it tests is the most actionable one in ecommerce UX: that visitors abandon carts because they hit friction, not just because of price or shipping. When a frustration spike and an abandonment spike line up on the same dates, you have evidence that fixing the experience will recover sales, and a replay queue to prove exactly what broke.

|                       |                                                                                                                                                                               |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | FullStory session frustration plotted on a dual axis against the store's cart abandonment rate across the period.                                                             |
| **Sample type**       | Backend API data from FullStory combined with the connected ecommerce platform, refreshed on the standard data refresh.                                                       |
| **Why it matters**    | It links a soft experience signal to a hard revenue outcome. Co-moving spikes turn "we should improve UX" into "this specific friction is costing this many abandoned carts". |
| **Reading the value** | Look for the two lines moving together. A frustration spike that precedes or coincides with an abandonment spike is the actionable pattern.                                   |
| **Currency**          | percent                                                                                                                                                                       |
| **Time window**       | `30D`                                                                                                                                                                         |
| **Alert trigger**     | `frustration spike co-occurs with abandonment spike`                                                                                                                          |
| **Sentiment key**     | `fs_xc_session_quality_vs_cart_abandonment`                                                                                                                                   |
| **Roles**             | owner, marketing                                                                                                                                                              |

## Calculation

Calculated automatically from your FullStory and ecommerce-platform data. Vortex IQ plots session frustration against cart abandonment on a shared timeline and flags windows where both rise together. 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 **Session Frustration vs Cart Abandonment** for a typical merchant on FullStory.* Suppose abandonment jumps from 68% to 79% over three days and the frustration line spikes on the same days. Opening the high-frustration replays from that window shows the shipping-options widget failing to load, leaving the total blank, so wary shoppers leave. The overlay made the link obvious; without it, the abandonment rise would have been blamed on price. Fixing the widget pulls abandonment back. For deeper investigation, use Vortex Mind to confirm the causal step; for natural-language exploration, ask Ask Viq whether frustration is driving abandonment.

## Sibling cards merchants should reference together

| Card                                                                                                       | Why merchants reach for it                  |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| [`ful_cart_abandonment_rate`](/nerve-centre/kpi-cards/fullstory/cart-abandonment-rate)                     | The abandonment side of this comparison.    |
| [`fs_frustration_score`](/nerve-centre/kpi-cards/fullstory/avg-frustration-score)                          | The frustration side of this comparison.    |
| [`fs_checkout_path_frustration`](/nerve-centre/kpi-cards/fullstory/checkout-path-frustration-events)       | Checkout-specific friction behind the link. |
| [`fs_form_abandonment_rate`](/nerve-centre/kpi-cards/fullstory/form-abandonment-rate)                      | Form friction that feeds cart abandonment.  |
| [`fs_high_frustration_sessions`](/nerve-centre/kpi-cards/fullstory/high-frustration-sessions-review-queue) | The replays that prove the cause.           |

## Reconciling against the vendor's own dashboard

**Where to look in FullStory's own dashboard:**

The frustration line comes from FullStory; the abandonment line comes from your ecommerce platform. Reconcile each against its own source over identical dates, then compare the timing of the spikes.

**Why the Vortex IQ value may legitimately differ:**

| Reason                                                                                                     | Direction | What to do                               |
| ---------------------------------------------------------------------------------------------------------- | --------- | ---------------------------------------- |
| **Abandonment definition.** How the platform defines an abandoned cart affects the line.                   | Variable  | Align the abandonment definition.        |
| **Period boundary.** Vortex IQ uses 30-day rolling by default; source dashboards may use calendar periods. | Variable  | Match the period range.                  |
| **Timing alignment.** Frustration and the resulting abandonment may not fall on the exact same hour.       | Variable  | Allow for a short lag between the lines. |

**Cross-connector reconciliation:** this card is itself a join, so use Vortex Mind to confirm the causal direction when the lines move together.

## Known limitations / merchant FAQs

**Q: How often does Session Frustration vs Cart Abandonment 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 co-movement prove causation?**
Not on its own, but it is strong evidence and it points you straight to the replays that confirm it. Watch the high-frustration sessions from the spike window to see the actual cause.

**Q: Why does my FullStory dashboard show a different number?**
The most common reasons are the abandonment definition, period boundaries, and timing alignment between the two lines. Align these before assuming a real divergence.

**Q: Can I customise the alert threshold?**
Yes, the co-occurrence sensitivity is configurable per profile in the Sensitivity tab. Tune how closely the spikes must align to trigger.

***

### Tracked live in Vortex IQ Nerve Centre

*Session Frustration vs Cart Abandonment* 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.
