Session replay that knows where to look

You have the recordings. Where do you look?

Sign-ups go down. Someone says "check the replays". You open one, play it fast, miss the moment and go back. At the end of the day you have a guess, three timestamps and no time left to decide.

The recordings were not the problem. The problem was where to look.

The answer first. The recording as evidence.

Sequential turns a session into a short text list of its events, such as clicks, page changes and form submits. The judge reads this text. It does not see the screen. The judge answers questions about the session, and each answer has a likelihood.

• Watch finds the sessions. Watch judges new sessions in the background and ranks them. A row with a clear key moment shows "Watch from m:ss". The replay opens just before that moment, with the answer open.
• Insights explains the session you open. It judges that one session and shows the answers below.

• Intent. What the person came to do, for example "Buy or subscribe".
• Outcome. How the session ended, for example "Switched to support".
• Friction and signals. For example "Noticeable struggle", with Rage clicks and Went in circles.
• Moments. Up to three with the default questions, such as where they struggled. Click one to go to half a second before it.

When the answer loads, a red mark on the timeline shows where the judge put the struggle. You see it before you press play. In our demo replay, the mark is at 0:35, on "Apply code".

Every answer shows its working

• A signal below 40% shows no chip. From 40% to 70% it says "unclear". Only 70% and more shows a number.
• Every moment points to one event. Go to that event and check it yourself.
• The questions are yours. Owners and admins edit them for each project.

In our demo replay, Rage clicks shows 95%. Product bug says "unclear". A signal at 21% shows no chip.

A worked example: the shipping address

This example is illustrative. Northlight Outfitters is our fictional demo shop.

Sequential finds a failed request on the shipping page. It hit 38 people. In plain words, people get stuck at the shipping address. Your agent links two sessions at the exact second: "Retyped the postcode four times, left" at 1:47, and "Postcode with a space is rejected" at 2:14.

The first session opens paused at 1:47. You do not watch 38 people struggle. You need one clear second.

Your agent files WEB-231 in your tracker. The team ships release 2026.10.09. Measured after the release: 41% → 12% of sessions on the shipping page. This is a measurement, not a verdict. You decide what it means.

Hand the second to a teammate or your agent

• A teammate. Press C. "Link copied — starts at m:ss." The link opens paused at that second, with the same panels open.
• Your agent. Ask your agent writes a prompt about this second for the Claude desktop app, Claude Code, Cursor or any agent. You review the prompt and send it. Sequential sends nothing itself.
• Or the agent asks. A connected agent gets sessions itself, with links to the moment.

One timeline. Web and mobile.

• All in one place. Your analytics events, clicks, page changes, JS errors and failed requests. Also the rage clicks, dead clicks and bounces that the player calculates.
• DevTools next to it. Console, network and performance. Sequential never keeps request headers or bodies.
• Mobile in the same player. iOS and Android, with a platform badge, touch rings and named screens. The recordings come from a stock open-source mobile SDK. iOS is tested with a real app on the simulator. Android is not tested with a real app yet.

Masked by default

On websites, the device masks the recording while it records. Strict is the default. It masks all text, every input and most attribute values. It blocks images and media.

Our servers scrub each recording again. That pass can only mask more. To loosen masking, you type a confirmation, and the change goes in the audit log. On mobile, you set masking in the app’s SDK.

What leaves for the answer. Insights sends the third-party service that judges sessions a text list of events: the kind, the time, the page path, and a label and a short detail, each cut to 80 characters. It also sends the session’s length, device, browser, operating system and country. The id you pass to identify stays out.

Good to know

• Keep ids and emails out of your events. Sequential does not filter them in event properties or page paths. They can go to the third-party service that judges sessions.
• Retention. The hosted preview keeps 7 days of data by default. Sequential deletes data in weekly blocks, so data stays 7 to 14 days.
• Mobile. Mobile replays have no Performance metrics and no JS errors. Sequential accepts React Native and Flutter recordings, but we have not verified them.
• Events, not pixels. The judge cannot see what shows only on the screen. The recording shows it.
• Cut-offs. Today the 40% and 70% cut-offs are the same for every project. They are not set for your product.
• Two judgments. Watch also counts DevTools errors. Insights reads only events. They can disagree, so check the moment.
• No live view. A recording is ready about 30 seconds to 6 minutes after upload. The open player checks again and loads it when it is ready.

Questions