Using FullStory?

FullStory funnels or exclusions misbehaving? We ship it properly.

FullStory earns its keep when the exclusion rules, custom events and session identity are all wired to your real product. When they are not, you get replays of people who opted out, funnels that undercount signups by a quarter, and warehouse exports that will not reconcile with any other analytics tool you own. We work through the setup until the data matches reality.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

fullstory-health.log

still broken

What it is

FullStory at a glance

FullStory is a digital experience platform that combines session replay with product analytics, funnels, heatmaps and warehouse export. Where a pure analytics tool only sees aggregate numbers, FullStory keeps the underlying session detail, which means a funnel drop can be opened and watched rather than guessed at.

The company was founded in Atlanta in 2014 and now serves many enterprise web and mobile teams. Pricing is session-based with enterprise add-ons for data export, HIPAA, mobile SDK and advanced analytics. Instrumentation is a single snippet plus a growing set of SDKs for iOS, Android, React Native and Flutter.

Type
Digital experience analytics and replay
First released
2014
License
Proprietary SaaS, session-based pricing
Maintained by
FullStory, Inc.
Typically used for
Product analytics on web and mobile, funnel debugging, support replay, conversion research

The honest version

FullStory pros and cons

No technology is all upside. This is where FullStory earns its place and where it tends to cause trouble.

Where FullStory is strong

  • Funnels you can actually openA drop in conversion between step two and three is not a mystery number, it is a list of sessions where that drop happened and you can press play on any of them.
  • Private by default stanceText inputs are masked unless you explicitly allow them, which is the opposite of several competitors and far easier to defend in a privacy review.
  • Warehouse export is first classDaily or hourly loads into BigQuery, Snowflake or Redshift mean your BI team can join FullStory events to orders, subscriptions and support tickets.
  • Mobile coverage is realThe iOS and Android SDKs capture gestures and view hierarchy, which closes the gap left by most competitors who treat mobile as an afterthought.
  • Frustration signals built inRage clicks, dead clicks and error clicks are detected out of the box and surface as metrics you can alert on.

Where FullStory bites

  • Session stitching is fragile across loginsAnonymous to identified handoff requires a specific call order. Miss it and the same user shows up as two sessions, which breaks funnels in subtle ways.
  • GDPR shutdown is your responsibilityFullStory ships helper APIs, but deciding when to call them based on consent state, region and user type is work that falls on your code and your legal review.
  • Enterprise pricing without published tiersYou negotiate per-session rates and add-ons individually, which makes budgeting across a fiscal year harder than it should be.
  • Custom events have size limitsProperties larger than the per-event cap are silently dropped, so a well-meaning analytics engineer ships a schema that looks like it is working and is quietly missing data.
  • Cross-frame recording needs the snippet inside the frameCheckouts rendered inside a payment iframe show up as blank in replay unless the vendor cooperates, which is usually a conversation rather than a code change.
  • ITP and ad blockers chip away at session countsSafari and Firefox tracking protection, plus browser extensions, quietly reduce the sample. Reconciling FullStory numbers with your warehouse takes care.

Sound familiar?

Common FullStory problems we fix

The FullStory problems that bring people to us, and what you have once each one is fixed.

FS.identify called before FS('setIdentity') ready

Logged-in users show up as anonymous

The identify call fires before the FullStory snippet has booted, so the first page of a session is attributed to an anonymous visitor and the funnel never joins them up.

Identities stitched end to end

Excluded element selector did not match any nodes

Private data is leaking into replays

An exclusion rule pointed at a class that got renamed in a design refresh, so PII that used to be masked is now visible in recent replays.

Exclusions aligned with the live DOM

GDPR region detected, shutdown API not called

EU visitors recorded without consent

The consent banner loads after the FullStory snippet, so a short window of recording happens before the user chooses. We move the gate and add a shutdown call on refusal.

Consent respected at the first paint

Session export to BigQuery: late-arriving rows

Warehouse numbers disagree with the dashboard

Late events arriving after the export window closed, or a custom event schema that was changed without coordinating with the warehouse load.

Export reconciled to the dashboard

Custom event 'checkout_started' dropped

Events are being silently dropped

A property payload over the per-event limit, or a type that fails validation. The dashboard looks healthy and the event never shows up in funnels.

Schema that actually ingests

iFrame recording requires snippet inside the frame

Replays are blank through the checkout

The payment vendor renders in an iframe without the FullStory snippet, so replay shows the parent but not the critical step where people drop.

Checkout visible in replay or clearly annotated

Mobile SDK: session not uploaded

Mobile sessions are missing

Offline buffers filling on long trips or bad networks, uploads throttled by the app going to background, or a crash before the session was flushed.

Mobile sessions reliably uploaded

What we do

FullStory help, from rescue to upkeep

Call us for one broken funnel, or let us run the FullStory account for you.

Rescue
Funnels that disagree with the warehouse, replays that leak data, or consent that is firing after the snippet. We stabilise and explain the gap.
Instrumentation
Custom events, user traits and session identity designed around your real product flows, with naming conventions your BI team can live with.
Privacy and consent
Exclusion rules audited against the live DOM, consent gating around the snippet, and a shutdown path that works for EU, HIPAA and internal-only users.
Warehouse export
BigQuery, Snowflake or Redshift loads reconciled to the dashboard, with late-arriving row handling and a schema BI can join against.
Managed Tech
Ongoing watch on ingest health, SDK upgrades alongside your framework releases, review of new exclusion rules before they ship, and a person to call when a funnel starts drifting.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running FullStory alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

FullStory questions

Something else? Call+1 737 727 7327

Why do my FullStory funnels disagree with my warehouse?

Three common reasons. Anonymous to identified handoff is not stitching, so one person is two users in funnels. Custom events are being dropped because the property payload is over the size limit. Late-arriving rows land after the export window, so the warehouse snapshot is always a bit behind. Each is fixable once you know which one you have.

How do I mask sensitive fields in FullStory?

FullStory masks text inputs by default, which covers most cases, but custom rich text widgets, contenteditable elements, and anything inside a canvas need explicit exclusion rules. We audit the DOM, write selectors that will not rot at the next rename, and add a test that catches regressions.

Does FullStory work with GDPR consent banners?

Yes, if the snippet is gated correctly. The usual mistake is loading FullStory on the first paint and then calling shutdown when consent is refused, which still records the first few seconds. Loading conditionally based on consent state, and keeping a shutdown path for consent withdrawal, keeps you on the right side of the regulation.

Why do I see blank replays during checkout?

The checkout is almost certainly rendered inside an iframe from your payment vendor. FullStory can only record what is in the same frame as its snippet, so the parent page is captured and the critical step is not. Fixes range from a vendor-side snippet install to annotating the gap with custom events.

Can we use FullStory for mobile apps?

Yes. The iOS and Android SDKs record gestures and view hierarchies, and React Native and Flutter wrappers exist. The gotcha is that mobile sessions are uploaded in batches, so a crash before flush loses the tail, and a long offline period fills the buffer. We set the limits based on your app's traffic pattern.

How much does FullStory help cost?

Estimates do not cost anything. Tell us the account, the flows that are drifting, and we send back a price before any work starts.

Free estimate

FullStory giving you trouble?

Share what the dashboard says, what the warehouse says, and where the two diverge. We read it and come back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.