The Fullstory alternative that shows you what to fix

• Know which replay to open. Sequential ranks new sessions. In each judged replay, the judge's reading tells you what the person came to do, how the session ended and where they struggled.
• Evidence puts broken sessions first. Evidence ranks your judged sessions by how much they need a look: sessions that broke for the person first, then sessions where the person struggled, then the rest.
• Cases counted exactly. Sequential groups the same problem across your users' sessions and counts exactly how many people hit it. It checks for exceptions, failed requests, dead clicks, rage clicks and dead ends every 15 minutes by default.
• A check after the release that fixes a problem. Record the release and name the case that it fixes. Sequential then counts the same problem before and after that release. The result reads, for example, Improved or Fixed.
• DevTools in each web replay. See the console, network requests, JavaScript errors and page speed from the user's browser, in sync with playback. All four captures are on by default.
• Your coding agent, connected. Connect Claude Code, Cursor, Codex or another MCP client. Your agent gets the problem, how many people had it and the replays.

1. 01

   Create your account

   Create an account in the hosted preview with your work email and a password. Setup has four steps: Organisation, Project, Install and Agent.

2. 02

   Add the Sequential tag

   Paste the sequential.js tag once into your site's head. It is one tag for analytics and session replay, about 21 KB gzipped, and it loads the replay recorder after it reads the project's settings. For Google Tag Manager, use the tag's Google Tag Manager (Custom HTML tag) version. For apps with a build step, use the npm package @usesequential/browser and call init() one time with the project key and the API host.

3. 03

   Move your identify call

   Where you call FS('setIdentity') at sign-in, call sequential.identify(id). Call sequential.reset() at sign-out. Earlier anonymous visits from that browser then count under the same person.

4. 04

   See the first events

   Your project's Setup page changes from "no events yet" to "receiving" when the first event arrives. Events usually show within about a minute.

<script async src="https://cdn.usesequential.com/sdk/sequential/v1/sequential.js"
        data-key="YOUR_SEQUENTIAL_INGEST_KEY"
        data-api="https://YOUR_SEQUENTIAL_API_HOST"></script>

Your coding agent can do the install. Copy one prompt into your coding agent. It adds Sequential, runs your build and tests, and lists every file it changed. You read the diff.

• Release check. Record the release with one call from your deploy, and name the case that it fixes. Your agent can make the call with a token that can write releases. Sequential then counts the same problem before and after that release and shows both rates.
• A fix brief for each case. Every case comes with a fix brief: what users hit, where, the evidence, since when, and how Sequential checks the fix after the release. Copy it into a ticket or open a GitHub new-issue page with the brief filled in.
• Your Questions. Write the questions that Sequential asks about each judged session, such as "Did they send an invite?". Start from twelve default questions. Owners and admins can reword, switch off or add questions, up to 24.
• Changes. Changes is a timeline of what your company changed: releases, product changes, prices, campaigns, incidents and more. Sequential shows what happened near a change.
• Backend SDK for Node. @usesequential/node sends events from your server and puts them on the same person as the browser events. An error from your server opens a case at its first occurrence.
• Calibration. Your team marks each of the judge's readings Right or Wrong. After at least 20 checks on a question's current wording, "How often people agree with the judge" shows if its answers are right as often as the judge says, on your own sessions.

Sequential is not affiliated with Fullstory. Fullstory is a trademark of its owner. Facts about Fullstory come from its public pages, checked on 2026-10-22.