What is Sequential

Examples from a SaaS product:

With JS errors and With failed requests read counts taken from the recording. So they return only recorded sessions that Sequential checked.

• Sequential picks up a session no sooner than 30 minutes after its last event. It checks every 5 minutes.
• A session needs at least three meaningful events. Its last event must be within the past 7 days.
• When judging is turned on, it covers sessions from the past 7 days, not older history.
• Each project has a daily judging allowance. If the allowance runs out, judging pauses. It starts again after the allowance resets at midnight UTC.
• Sequential judges each session once. Changes to your questions apply to sessions judged afterwards. Sequential marks older verdicts "judged with an earlier rubric".
• Background judging reads your stored events, not the screen recording. Sequential judges sessions without a recording too. It does not judge a recording with no analytics events behind it.

The default questions cover:

• Intent: what they came to do.
• Outcome: did they get there.
• Friction: how much it hurt.
• Signals such as Hit an error, Product bug and Worth watching.
• Moments such as Where they struggled and Where they gave up. Each moment points at one event.

Sequential keeps each answer as a probability. The model writes no prose. Sequential assembles the sentences you read from those numbers.

The summary leaves out the user id. Page addresses lose their host and query string. Page paths and short labels, such as visible click text, stay in the summary. So an id inside a path (/users/123) or on a button still reaches the model. See AI and third parties.

Owners and admins can change the questions. To change them, open Settings → Projects → your project → Insights.

Watch

• Where it can, Watch links to the key moment in the replay.
• Watch from m:ss opens the replay at the key moment, such as where they struggled or gave up. The replay opens on the Insights tab.
• The thumbs-up and thumbs-down on a row record whether the verdict was right. They never re-judge.

Ask

• Each search judges up to 200 of the newest 2,000 sessions in your date range. The sessions that Watch ranks highest go first.
• Search … more continues the search.
• If Ask can point to the moment, the row shows Watch from here.
• Ask leaves out weaker matches.
• Ask finds sessions. It does not count them.
• Ask in the app has its own daily allowance. It does not use the allowance of background judging.

Insights

• It shows the verdict, key moments you can click to jump to, and timeline marks where the struggle was.
• New judgments use a separate daily allowance.
• Re-run gets a fresh answer at most once every 10 minutes per session.
• It works from the recording's timeline. So it can disagree with Watch about the same session.

• In the browser, Sequential takes events from PostHog, Mixpanel, Amplitude, Pendo or Smartlook. In mobile apps, it takes events from PostHog's SDKs.
• A website with no analytics SDK can use the Sequential SDK: one tag for analytics and replay.
• You point your SDK at Sequential with your project's key. For Pendo, you register your own Pendo API key with the project instead.
• You do not fork your SDK or add a second analytics SDK.
• Sequential sorts each event on arrival into one of nine classes, such as page view, click, error or custom. It does this for every SDK.
• On the web, the Sequential SDK and Sequential's Smartlook script (Moving from Smartlook) start the recorder themselves.
• With PostHog, Mixpanel, Amplitude or Pendo, you add Sequential's recorder script next to the SDK. The recorder picks up your SDK's session id. This is how your events appear on the replay timeline at the moment they happened.
• In mobile apps, Sequential plays back the PostHog SDK's own recording.
• On the web, the DevTools drawer also shows JavaScript errors and page performance.
• By default, Sequential keeps each console call's level, how often it happened and where. It does not keep the logged text. Each project can opt in to keeping message text.
• Mobile apps report less in DevTools.
• The replay player marks rage clicks and dead clicks that it finds in the recording.

• Events: events over time, breakdowns and the event list, with a filter builder.
• Funnels: ordered steps, conversion and drop-off. It shows the users who dropped out at each step.
• Flows: the paths people take between steps you define, as a Sankey diagram.
• Retention: the share of people who come back to do a return event N days after their start event. By default, it groups new users by the day of their first event, when that day is in your date range. Count can also include everyone active in the range. It shows the share active again exactly N days later. The defaults are 1, 7, 14 and 30, and you can change them. A long-standing user counts as new on their first day in the range.
• Users and Accounts: users and accounts, with their sessions. Users lists every user. Accounts lists the accounts, from Pendo data and from sequential.account(), the ones with problems first.

From 11 October 2026, the rail shows, from the top: the project switcher, Search…, Agents (owners and admins only), Findings, Watch, Dashboard and Explore.

• Findings shows the number of open findings at the stage New. See Findings and fixes.
• Watch shows the number of sessions that broke for the user in the last 7 days: the Broke for the user group in Watch. The number shows alone, in the same style as the other numbers in the rail. Point to it to see the sentence, for example "4 sessions broke in the last 7 days". When the number is 0, or Sequential cannot read it, no number shows. Watch opens Sessions. Latest and Ask are tabs on that page.
• Explore opens in place: Events, Funnels, Flows, Retention, Users, Accounts and Heatmaps. Only roles that can play recordings see Heatmaps. Explore is folded the first time. Your browser remembers if you leave it open. On a page inside Explore, it is open and that page is marked.
• On a phone, the same items are in the menu (≡).

Settings is at the bottom of the rail. In a wide window, your account button, Help and Settings are side by side there. Settings is an icon button with the tooltip "Settings". Your account button shows your initials, and also your name when all of it fits. Its tooltip shows your name and email, and its menu starts with them. The mark at the top of the rail, next to the project switcher, opens the Dashboard.

To go to a page fast, press ⌘K on a Mac or Ctrl K on other computers. You can also click Search… at the top of the rail. Type the name of a page, a setting, a project ("Watch" is the Sessions page: "sessions" and "latest" find it too), or a saved filter, funnel, flow or retention view of the project. You can also find a person, a finding or a docs page, run commands for the page that you are on, and paste an id to open a session, a user or a finding. See Search or jump to.

From 13 October 2026, press ? to open Help: it searches these docs, lists the pages for the screen you are on, and has Send feedback and Contact support. Pages from Help open in a new tab. The Help button next to Settings at the bottom of the rail opens it too. On a phone, it is the ? at the top. In Help, Keyboard shortcuts shows the keys that work anywhere, in the search and in the replay player. In the replay player, ? shows the player's own shortcuts.

• Session id: Sessions, Watch and Ask group events by session id, so events need one. Sessions explains where it comes from.
• One identifier for each person: pick one identifier, such as a user id, an email or an account key. Pass that same value every time you identify the person. Sequential uses the value exactly as you send it.
• Events the judge can read: the judge reads page views, named screens, clicks and custom events, plus a few session facts and error counts.