Productivity - Setup Guide

How to set up FullStory

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Session recording captures form inputs by default. PII (emails, passwords, credit cards) leaks into replay unless redaction is configured explicitly. FullStory has smart redaction rules but the default is not zero-trust [source: help.fullstory.com/hc/en-us/articles/360020623354].
• Session replay eats storage, and FullStory bills partly on session volume. High-traffic sites see cost climb fast.
• Session replay on mobile apps requires the FullStory SDK, which adds app size and battery cost.
• Replay only works if the DOM is capturable. Heavy Canvas, WebGL, or iframe content shows as blank in the replay.
• Customer data platforms and consent tools (OneTrust, Cookiebot) must be configured to allow FullStory or replay drops silently.

The 7-step setup

1. 1

   Create your FullStory account

   Sign up at the link below. Card required for the paid tier - most plans include a trial period; check the pricing section on this page first so you know what you're committing to.

   Open FullStory signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If FullStory pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire FullStory into the rest of your stack. The integrations that most people set up first: Segment, Snowflake, BigQuery, Redshift, Slack, Zendesk, Salesforce Service Cloud, HubSpot, Jira (auto-file bug with session link), Optimizely, LaunchDarkly, Mixpanel, Amplitude, Google Analytics.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how FullStory deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in FullStory - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend FullStory for mid-market to enterprise e-commerce and SaaS teams where session replay is a core workflow (support triage, checkout diagnosis, PM discovery). Recommend Microsoft Clarity for small businesses and startups that want the same replay concept for free. Recommend Hotjar for teams wanting heatmaps and surveys alongside replay at mid-market pricing.