How to Install FullStory and Mask Sensitive Data Before Your First Recording

October 31, 2026

FullStory records sessions plus experience analytics, has no free tier, and pricing starts around $199/month. Before you ship the snippet, decide what gets masked — FullStory records DOM text by default, and un-redacting after the fact is not a supported workflow.

What does FullStory record, exactly?

A reconstruction of the DOM, mouse movement, clicks, and text content in most elements. That means a session replay can show a customer’s name, address and the last email subject they read. Masking is a configuration decision, not an afterthought.

Two levels exist: exclude (element is not recorded at all) and mask (layout is recorded, text is replaced with asterisks). Use mask for layout-critical areas, exclude for anything that should never leave your infrastructure.

How do you install the snippet safely?

  1. Create the project in FullStory and copy the snippet.
  2. Set privacy defaults to strict in project settings before installing anywhere. Do this first — defaults apply to new recordings only.
  3. Add the snippet to your app shell.
  4. Call FS.identify() with a stable user ID on login.
  5. Load one session on staging and review the replay for leaked fields.
  6. Only then promote to production.

Step 2 is the one that gets skipped because the onboarding flow pushes you straight to installation. Strict defaults mask all text by default and force you to opt elements back in, which is the safer direction.

Which elements must be masked or excluded?

A starting list for most SaaS apps:

  • Payment forms — exclude the entire form, not just the card number field.
  • Password and API-key inputs — exclude.
  • Personal data tables — mask by column, not by page.
  • Chat and support widgets — exclude; transcripts are easy to leak.
  • Admin impersonation views — exclude unless you have a documented reason.

The robust approach is attribute-based: add data-fs-exclude or the equivalent class to your sensitive components once, in the design system, rather than hunting through pages.

How do you verify masking actually worked?

Open a recording where you personally triggered the flow. Type a fake card number, submit, then watch the replay. If you can read the number, masking failed for that element — and it will be readable for every real customer too.

Test at least three flows before launch: signup, checkout, and settings/profile. Those three cover most regulated data.

Also check your error tracking. Unhandled exceptions often include form values in the stack context, and FullStory recording plus an unmasked error report is a worse combination than either alone.

What else should you configure before going live?

Set the retention period deliberately. Longer retention is more expensive and increases exposure; 30 to 90 days covers most debugging needs.

Decide whether to record internal accounts. Most teams exclude employees from recordings, then forget trial accounts used by sales demos — those sessions pollute your analytics.

Finally, connect your support tool if you use one. FullStory’s replay links inside a ticket are the feature that pays for the subscription. Teams running Hotjar for heatmaps will usually consolidate to one replay vendor rather than paying twice.

When is FullStory the wrong choice?

Small sites with under a few thousand sessions a month. At $199/month with no free tier, a solo product cannot justify it, and Hotjar‘s free 35-session-per-day plan or a free Clarity account will do most of the job.

It is also the wrong pick if your team will not maintain masking. A replay tool without a masking owner is a liability with a dashboard attached. And if you want replay plus self-hosted analytics in one bill, compare PostHog.

Key Takeaways

  • FullStory has no free tier; pricing starts near $199/month and scales with sessions.
  • Set privacy defaults to strict in project settings before installing the snippet.
  • Exclude payment, password and chat widgets entirely; mask personal data by column.
  • Verify by watching your own test recording of signup, checkout and settings.
  • Set retention at 30–90 days and exclude internal and demo accounts.