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
Using FullStory?
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.
What it is
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.
The honest version
No technology is all upside. This is where FullStory earns its place and where it tends to cause trouble.
Sound familiar?
The FullStory problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
Call us for one broken funnel, or let us run the FullStory account for you.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Share what the dashboard says, what the warehouse says, and where the two diverge. We read it and come back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: