The Smartlook alternative that keeps your web SDK and shows what to fix

• Keep your Smartlook web SDK. Your track, identify, properties, navigation and error calls keep working unchanged. Session replay continues on Sequential with the same session id as your events.
• Know which recording 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.
• Problems counted exactly. Cases group the same problem across your users' sessions and count exactly how many people hit it. Each case shows up to 5 sample sessions, and a sample with a ready recording opens at the moment the problem happened.
• 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. It states what changed.
• DevTools in each web replay. Each web replay can show the console, network requests, JavaScript errors and page speed from the user's browser, in sync with playback.

1. 01

   Create an account

   Create an account in the hosted preview. After sign-up, four steps follow: Organisation, Project, Install and Agent. The Smartlook tab in Settings › Setup shows your Sequential Smartlook ingest key.

2. 02

   Change two lines in your snippet

   In the script tag that your site already has, c.src loads /recorder.js from the Sequential API URL, and the init call uses your Sequential Smartlook ingest key with an empty options object.

3. 03

   Or keep the npm package

   With smartlook-client, keep the package and set relayProxyUrl to the Sequential API URL, as an origin only.

4. 04

   See the first events

   Sequential's recorder starts on its own while the project's replay key is live, with no separate replay line. Your project's Setup page shows a Smartlook line with "receiving" when the first event arrives.

    c.charset='utf-8';c.src='https://YOUR_SEQUENTIAL_API_HOST/recorder.js';   // was web-sdk.smartlook.com
    smartlook('init', 'YOUR_SMARTLOOK_INGEST_KEY', {});   // your Sequential key; drop { region: … }

import smartlook from 'smartlook-client';
smartlook.init('YOUR_SMARTLOOK_INGEST_KEY', { relayProxyUrl: 'https://YOUR_SEQUENTIAL_API_HOST' });

Your coding agent can also do the switch. Copy one prompt into it, and it adds Sequential to the analytics you already run, runs your build and tests, and lists every file it changed. You read the diff.

• Connect your coding agent. Connect Claude Code, Cursor, Codex, Claude Desktop or another MCP client. Your agent gets the problem, how many people had it and the replays. A new token starts with read access and Ask. It does not change data, with one exception: getting a fix brief marks the case as handed off.
• Release check. Record the release and name the case that it fixes. Sequential then counts the same problem before and after that release. It shows both rates. A Fixed result stays watched for 30 days.
• Ask. Type one plain sentence, for example "tried to pay and was blocked by a payment error". Sequential lists the sessions that likely show it, strongest first.
• Your Questions. You write the questions that Sequential asks about each judged session, such as "Did they send an invite?". You get answers in the words of your product.
• Changes. Changes is a timeline of releases, product changes, prices, campaigns and incidents. 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.

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