Every drop-off is a person you can open.

You have the chart. Now meet the people behind it.

A chart shows that a number fell. The work is to find who left and what they saw.

Funnels, flows and retention count people through the events that your SDK sends. Findings come from fixed checks for five kinds of problem, such as an error or a click that does nothing. Each finding shows how many people it hit.

How it works

1. 01

   Keep your SDK and your tracking calls.

   Keep a supported SDK and your tracking calls. Change its key and its host. Or use the Sequential SDK. A click means a click, whichever SDK sent it.

2. 02

   Ask your questions.

   Chart events, build a funnel, see the routes that people take and see who comes back.

3. 03

   Open the people behind the number.

   Click a drop to see who left. Open one person: the events of the last step they reached are highlighted. A session with a recording has a ▶ button.

The same panel shows the findings in the sessions where they left, and how long they stayed on the step before they left.

Example: Northlight Outfitters, our fictional demo shop

From a falling number to the person who left

The head of product at Northlight builds a funnel: cart, shipping, payment. The biggest drop is at shipping. She opens one person who left and presses ▶. The customer types a postcode with a space. The form rejects it. They type it again four times, then they leave.

Sequential had already counted the failed request behind that moment as a finding: 38 people. In plain words, people get stuck at the shipping address.

The team’s agent files WEB-231 in their tracker. The team ships release 2026.10.09, and their deploy records the release in Sequential. Sequential measures again: 41% → 12% of sessions on the shipping page. That is a measurement, not a cause. The team decides what it means.

What is in the box

• Events. Charts by hour, day, week or month, grouped by page, browser or campaign source. A recent event opens its replay when the recording is ready.
• Funnels. People, not events, through steps in order, also across sessions. Each step shows the share of the step before it and the average time from it.
• Flows. Routes between up to three steps, with loops and detours, and where people left.
• Retention. Choose a start event and a return event. See who comes back on the days you choose, up to day 365, by day or by week.
• Filters. AND, OR and NOT. Before you run a filter, you can see it in one plain line.

A dashboard that you do not have to build

On your first visit, the dashboard is already filled from your last 30 days: traffic, top pages, errors, frustrated clicks and sessions that are worth a look. A tile shows only when real data is behind it. An empty tile reads "None seen in the last 30 days", never a bare 0.

Key actions shows the custom events whose names mean "finished what matters". Sequential picks a name only when it is sure. If it picks none, the tile shows your most frequent events.

Your agent can ask too

Connect your own agent and it runs the same analyses. Ask "Where does checkout lose people this week?" and it gets the funnel back, with the ids of the people who left. It can ask the retention question too: "Of the people who started a trial, how many invited a teammate on day 7?"

• Ids, not profiles. Your agent gets people as ids. It never gets identity fields, and filters on them are refused. Sequential also removes, best effort, names, emails and phone numbers that your app sent.
• Who acts. Sequential answers. Your agent decides what it files, and where.

Good to know

• No conversion window. In a funnel, the date range is the only time limit.
• Flows: three steps. With four or more steps, the labels of the later steps are wrong.
• One SDK, one host. You keep the code and the calls, but that SDK then sends to Sequential, not to your current tool.
• Replay with another SDK. Web replay with another SDK needs the Sequential recorder line.
• Sign-up in a funnel. With the Sequential SDK and some other SDKs, a person who signs up during a funnel counts as one person. This can take up to 5 minutes. With the other SDKs, keep a funnel on one side of sign-up.
• History. The hosted preview keeps 7 days of data by default. So day 30 and the 30-day dashboard show less. Sequential sets the period for your organisation: 7, 30, 90, 180 or 365 days. Dates are in UTC.
• No export. There is no CSV, no export endpoint and no scheduled report. Your agent can query the data.
• Your agent’s reach. The last 1 to 30 days. Funnels of 2 to 10 steps, with up to 100 ids for each drop. Ids arrive as your project sends them: if they are email addresses, your agent sees them.

Straight answers