At a glance
Replay Capture Coverage % is the data-quality metric for FullStory itself. It measures the share of expected sessions that were successfully captured as full replays. Because every other FullStory card depends on capture working, this is the card that tells you whether you can trust the rest. When coverage drops, the FullStory snippet is failing to load somewhere: a tag-manager change, a consent-banner block, a deploy that dropped the script. A blind spot here quietly understates every frustration and conversion signal downstream.
| What it counts | The percentage of expected sessions that FullStory successfully captured as replays in the period. |
| Sample type | Backend API data from FullStory, refreshed on the standard data refresh. |
| Why it matters | It is the trust gauge for the whole connector. If capture is low, every other FullStory metric is reading a partial picture, so this card belongs at the top of any investigation. |
| Reading the value | Higher is better. A drop usually means the snippet stopped firing on a template, a device, or behind a consent gate; reconcile with recent deploys. |
| Currency | percent |
| Time window | 30D vsP |
| Alert trigger | <80% |
| Sentiment key | fs_replay_capture_coverage |
| Roles | owner, marketing |
Calculation
Calculated automatically from your FullStory data. Vortex IQ compares the sessions FullStory captured against the expected session baseline for the period and expresses the ratio as a coverage percentage. 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 Replay Capture Coverage % for a typical merchant on FullStory. Suppose coverage runs at 94% then drops to 71%, under the 80% guardrail. The drop maps to a new consent-management platform that holds the FullStory snippet until opt-in, so a large slice of EU traffic never gets captured. The fix is to load FullStory under the correct consent category. Until then, every frustration card understates reality for that audience. For deeper investigation, use Vortex Mind to see which pages or regions lost capture; for natural-language exploration, ask Ask Viq where capture dropped.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fs_session_count | The raw captured-session count this coverage ratio sits on top of. |
fs_health_score | Capture health is a pillar of the UX health composite. |
fs_alert_tracking_broken | The alert that fires when capture collapses. |
fs_frustration_score | Reads low when capture is incomplete, so check coverage first. |
Reconciling against the vendor’s own dashboard
Where to look in FullStory’s own dashboard: FullStory exposes capture health through its settings and data-capture diagnostics, and you can see captured session volume in session search. Confirm period boundaries and any sampling settings match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Sampling. If FullStory capture is sampled, the expected baseline must account for it. | Variable | Confirm the sampling rate. |
| Period boundary. Vortex IQ uses 30-day rolling by default; FullStory dashboards may use calendar periods. | Variable | Match the period range. |
| Baseline definition. Expected sessions can be drawn from different traffic sources. | Variable | Align the baseline source. |