FullStory Digital Experience Analytics: Autocapture and QA Testing Workflows

Most web analytics tools tell you what happened: 12% of users dropped off on the checkout page. FullStory tells you why: those users clicked the submit button, waited six seconds for a response that never came, clicked again, got a duplicate order error, and left. Every element interaction, every page transition, every moment of user frustration — captured automatically, without writing a single tracking call.

This guide explains how FullStory's autocapture approach differs from traditional analytics, how it supports QA workflows, and when to use it as part of your quality assurance process.

Autocapture: The Technical Foundation

Most analytics platforms require instrumentation — you write analytics.track('Button Clicked', {button: 'checkout'}) calls throughout your codebase. FullStory takes the opposite approach. Its JavaScript SDK captures all user interactions automatically by recording the DOM and every event that occurs within it.

When FullStory loads, it takes a snapshot of the full DOM state and then records every subsequent mutation, interaction, and network request. This means:

• You don't need to instrument individual features before you can analyze them
• Historical data exists for user behaviors you didn't anticipate measuring
• Retroactive analysis is possible — you can answer questions about past sessions without re-deploying

The tradeoff is data volume. FullStory captures everything, which means storage and processing at scale. For most applications this is fine; for very high-traffic sites, sampling strategies are necessary.

Session Replay

Like other tools in this category, FullStory's session replay shows you a video-like reconstruction of what users experienced. The distinguishing characteristic of FullStory's replay is fidelity — because it captures DOM mutations rather than screen video, replay accurately renders dynamic content, hover states, scroll positions, and custom UI components.

Each replay session is accompanied by:

An events sidebar: Every interaction shown as a chronological list — clicks, scrolls, inputs, page navigations, errors.

Dev tools integration: Console logs, JavaScript errors, and network requests displayed in context with the interaction timeline.

Frustration signals: FullStory automatically highlights rage clicks, error clicks, and thrashed cursors (mouse movement indicating confusion or frustration).

User identity: If you've called FS.identify(), sessions are tagged with user metadata so you can search by user.

Searching Across Sessions with Omnisearch

FullStory's Omnisearch is one of its most powerful features for QA teams. You can search across all recorded sessions using natural language queries:

• "Users who clicked the checkout button and then saw a 500 error"
• "Sessions containing the text 'Sorry, that item is out of stock'"
• "Users who visited /settings/billing more than three times in one session"
• "Mobile users who tapped the menu icon on the homepage"

This makes it possible to find sessions that exhibit a specific bug pattern without knowing in advance which sessions to look at. When a bug report comes in — "users are getting confused on the billing page" — you can search for sessions that match that pattern and immediately find examples.

For QA purposes, this is valuable after deployments. Search for sessions that touch the code you just changed and verify that users are flowing through as expected.

Funnels and Conversion Analysis

FullStory's funnel analysis connects session replay to conversion analytics. You define a funnel (a sequence of pages or events), and FullStory shows you where users drop off — but with the ability to click into any step and watch sessions from users who abandoned at that point.

The quantitative funnel data tells you that 23% of users who start checkout don't complete it. The session replay tells you that most of them are abandoning on the payment form, and watching five of those sessions shows you that they're all hitting a validation error on the card expiry field that only triggers when the user types the year with four digits instead of two.

This combination of quantitative and qualitative data is particularly useful for validating that a redesign actually solved the problem it was intended to solve — not just that conversion rates improved, but that users are no longer struggling with the specific friction point.

Heatmaps and Click Maps

FullStory generates heatmaps retroactively from captured interaction data, without requiring you to configure them in advance. For any page or URL pattern, you can generate:

Click maps: Where users click on a page, with frequency represented by color intensity.

Scroll depth maps: How far down the page users scroll before leaving.

Move maps: Where users move their cursor, useful for understanding attention patterns.

Because these are generated from existing captured data rather than a separate tracking implementation, they're available for any page that FullStory has observed, including pages you didn't think to add heatmap tracking to.

For QA, click maps are useful for detecting dead zones — areas users click expecting interaction that your application doesn't handle. A high click concentration on a non-interactive element is often a UX bug.

The DX Data Platform

FullStory markets itself as a "Digital Experience" platform rather than a session replay tool. The DX Data platform combines session replay data with:

Custom events: Structured events you send from your application that FullStory correlates with session data.

Data export: Raw event streams exportable to data warehouses for analysis with your existing BI tools.

Integrations: Connections to Segment, Amplitude, Mixpanel, and other analytics platforms that let you enrich your analytics data with FullStory's behavioral signals.

For larger organizations, this means session replay isn't a standalone debugging tool but part of a broader data pipeline that informs product decisions.

Privacy and Data Governance

FullStory provides granular controls over what data is captured:

Element exclusion: Mark elements with fs-exclude class to prevent their content from being captured. Useful for sensitive fields beyond passwords.

Page-level exclusions: Prevent FullStory from recording specific pages entirely.

Automatic masking: Input fields detected as sensitive (passwords, credit card numbers, SSNs) are masked by default.

Data residency: FullStory supports US and EU data residency for GDPR compliance.

Consent flows: Integration with consent management platforms to respect user opt-out preferences.

For financial services, healthcare, and other regulated industries, FullStory provides compliance documentation and contractual data processing agreements.

Integrating FullStory with Your QA Process

Bug triage: When a user reports a bug with their email address, search FullStory for their sessions from the reported timeframe. Watch the sessions to understand exactly what happened.

Release validation: After deploying a change, search for sessions that touch the affected feature. Verify that new flows work as intended and that previously problematic patterns are gone.

Cross-browser validation: Filter sessions by browser and device to identify browser-specific issues that automated cross-browser testing didn't catch.

Automated test gap analysis: Review sessions with JavaScript errors or rage clicks to identify user flows that your automated test suite doesn't cover.

Documentation: Share session URLs in Jira tickets instead of (or in addition to) written reproduction steps. Session replays are often clearer than written steps, especially for complex interaction sequences.

Basic Setup

// Add to your HTML <head> or as an npm package
window['_fs_debug'] = false;
window['_fs_host'] = 'fullstory.com';
window['_fs_script'] = 'edge.fullstory.com/s/fs.js';
window['_fs_org'] = 'YOUR_ORG_ID';
window['_fs_namespace'] = 'FS';

// Identify users when they log in
FS.identify('user_id_123', {
  displayName: 'Jane Smith',
  email: 'jane@example.com',
  // any custom properties
  plan: 'professional',
  company: 'Acme Corp',
});

// Track custom events
FS.event('Checkout Started', {
  cartValue: 149.99,
  itemCount: 3,
  couponApplied: true,
});

FullStory's free trial provides 1,000 sessions per month. Paid plans scale based on session volume.

When FullStory Adds Value for QA

FullStory is most valuable when the gap between "what we tested" and "what users actually do" is significant. Automated tests verify specific, predefined flows. Real users combine features in unexpected ways, arrive with unusual data, use assistive technologies, and encounter environmental conditions your test environment doesn't replicate.

Session replay tools like FullStory provide visibility into this gap. They don't replace functional testing — they extend it by showing you what's happening in production that your test suite didn't anticipate.