The Hotjar alternative for heatmaps, replays and what to fix

• Heatmaps that stay on the element. Sequential stores clicks against the element that people clicked, not a point on the screen. At any screen width and under privacy masking, the heat stays on that element.
• 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.
• 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.
• Funnels that lead to the replay. Funnels count people through steps in order. Click a drop to see who left, and play their sessions from the moment they left.
• 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.

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, where the Hotjar Tracking Code was. If the Hotjar Tracking Code was in Google Tag Manager, use the tag's Google Tag Manager (Custom HTML tag) version there. 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 and event calls

   Call sequential.identify(id) at sign-in and sequential.reset() at sign-out. Send your own events with sequential.capture.

4. 04

   See the first events

   The Install step of setup changes from "Waiting for the first event." to "It works" 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.

• Evidence. Evidence ranks your judged sessions by how much they need a look. "Watch" opens the replay close to where the person struggled.
• 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. 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.
• Connect your coding agent. Connect Claude Code, Cursor, Codex or another MCP client. Your agent gets the problem, how many people had it and the replays, and it gets heatmaps as data.
• Flows, retention and accounts. Flows show the routes between steps. Retention shows who comes back. Accounts lists each company with its people, sessions and health.
• 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.

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