Capture: Optimize Your Data Capture Configuration in Fullstory

Your data capture configuration is the foundation of everything you do in Fullstory. When it's set up correctly, you get clean, complete data across all of your sites, which means more accurate session replays, better analytics, and a stronger signal for your team.

This article walks you through three key configuration tasks in Settings > Data Capture and Privacy > Data Capture. Each one directly improves your Data Capture health score.

• Task 1: Start capturing on one domain
• Task 2: Enable console data capture
• Task 3: Block common user agents

Task 1: Start capturing on one domain

Fullstory captures session data from the domains you've explicitly added to your account. If you run your product across multiple domains or subdomains, each one needs to be added—otherwise Fullstory won't record activity there.

Why it matters: Fullstory's configuration only captures data from approved domains. Missing domains mean gaps in your session data.

Steps

1. In Fullstory, go to Settings > Data Capture and Privacy > Data Capture.
2. In the Capture data by domain section, click Add Domain.
3. Enter the full domain URL (e.g., app.yourcompany.com).
4. Click Add.
5. Repeat for each additional domain or subdomain where Fullstory should capture data.

Further reading: Can I disable data capture for specific domains?

Task 2: Enable console data capture

Fullstory can capture browser console logs and exceptions directly within session replays. This gives you visibility into JavaScript errors and warnings that happen during a user's session, right alongside the recording of what they did.

Why it matters: Console errors are often invisible to end users but directly cause frustration, broken flows, and drop-offs. Capturing them means you can connect the error to the exact moment something went wrong.

Steps

1. In Fullstory, go to Settings > Data Capture and Privacy > Data Capture.
2. Locate the Console Data Capture section.
3. Toggle Console Data Capture to On.

Further reading: How do I use the Fullstory Console?

Task 3: Block common user agents

By default, Fullstory captures sessions from all visitors, including your own team, QA testers, bots, and automated tools. Blocking those user agents keeps your session data clean and ensures your analytics reflect real user behavior, not internal or inauthentic traffic.

Why it matters: Internal and bot traffic skews your session counts, frustration signals, and funnel data. Adding user agent rules filters that noise out automatically.

Steps

1. In Fullstory, go to Settings > Data Capture and Privacy > Data Capture.
2. Scroll to the Block User-Agents section.
3. Click Add Blocked UA.
4. Enter the user agent string you want to block (e.g., your company's internal browser agent, common bot strings like Googlebot, DatadogSynthetics, etc.). You may also click Block popular bot UAs to add the full list of blocked bots automatically.
5. Click Add to save the rule.
6. Repeat for each user agent you want to exclude.

Further reading: Can I block unwanted sessions by IP address or User-Agent or bot?

What's next

Once you've completed these three tasks, you're in good shape on Data Capture. Your next step is to work through your Data Management configuration—defining your pages and building your element library so Fullstory can surface meaningful insights.

Questions? Reach out to your Fullstory team or join us at Office Hours.