Anonymous on Monday, signed up on Tuesday. One person.

One customer, the whole story

Example: Northlight Outfitters, a fictional demo shop.

Thursday, 4:40 pm. Mara writes in: "Your checkout did not take my postcode." Her signed-in session starts halfway through, on the shipping page. Everything before sign-up is under an anonymous id that you cannot find. After an hour of guessing, you have half a story.

In Sequential, you open Users and click Mara. User detail shows the anonymous visit on Monday and the sign-up visit on Tuesday under one person. Click Watch on the Tuesday session: she types her postcode four times.

How does Sequential know that both visits are hers? Your app told it. At sign-in, the identify call of the Sequential SDK sends her id and the anonymous id that it replaces. Sequential joins the two each time it shows data. It never guesses.

She is not the only one. A Sequential finding, a failed request on the shipping page, counts 38 people. In the checkout funnel, click the drop at the shipping step. Under Who, the drop panel lists the people who left there. Their steps before and after sign-up count as one journey.

How it works

1. 01

   Call identify at sign-in and reset at sign-out.

   Call sequential.identify(id) when a person signs in, and sequential.reset() when they sign out. Pass your own value as text, not as a number: a user id, an email or an account key.

2. 02

   The SDK sends the anonymous id that it replaces.

   This links the visit to the person.

3. 03

   Sequential shows one person.

   Earlier anonymous visits from that browser count under the person on Users, Sessions, funnels and retention. Sequential never changes the stored events.

// At sign-in
sequential.identify(id);

// At sign-out
sequential.reset();

Every device: send the same value on every device and browser, and the signed-in sessions of the person belong to one person.

Sequential takes your word for who a person is. It never guesses that an email and an id are one person, and it never ranks id types. Two values are two users, so you can explain every count.

Do you not want to add it by hand? The Identify your users guide has a Copy prompt. With it, your coding agent adds identify and reset in every analytics SDK that sends to Sequential.

Accounts, for B2B

See which company, team or workspace your people belong to. Accounts lists every account with its plan, people, sessions and health, with the accounts that have problems first. Open an account to see its people, its findings, its activity and its properties.

You can filter funnels and retention to one account. A line under the list counts the sessions in the date range that had no account.

A list written for people

The Users list shows a person as you describe them aloud: a name with the email below it, from your identify calls, or "Anonymous visitor 01a0f6…". Then it shows sessions, top pages, problems and last seen.

Events with no user id never become a false person. One line counts them, for example: "399 events in 11 sessions in this period aren't linked to a user."

What your agent sees: ids, not names

Connect your own agent over MCP, with a project access token that has the analytics:read scope, and ask who left the checkout funnel. It gets up to 100 ids to follow.

Its lists of people have ids and counts. They never have a name, an email, an IP address, a page or a property. If it asks for a breakdown by email, it gets this answer: "Agents can't filter or break down by a person's or account's name, email or other identity fields."

The judge that reads sessions never sees the user id either. It sees only "identified" or "anonymous".

Each call returns up to 100 rows, from up to 30 days back, but never past your data retention. The hosted preview keeps 7 days of data by default. If your user ids are emails, send opaque ids.

Good to know

• Joining visits needs an SDK that sends the link. That is the Sequential SDK, or a vendor SDK that the Identify your users guide names. With other SDKs, the anonymous id and the signed-in id stay two users, and the sign-up session counts two times.
• Accounts come from the Sequential SDK or from one vendor SDK. Use sequential.account() in the Sequential SDK, or the account field of one vendor SDK (see Works with your SDK). Its other fields become account properties. Sequential does not use group calls from other SDKs for accounts yet.
• Funnels and retention count people, not accounts. You can filter them to one account.
• Anonymous visits join only from a browser where someone signed in. On other browsers, only the signed-in sessions of the person join.
• A new link can take up to 5 minutes to show.
• Sequential does not redact ids. If your user ids are emails, agents see them as ids.
• Sequential keeps the full IP address with every event. It uses the address to find the country. Connected agents never get it.

Questions, answered straight

Know who it was. Give your agent ids, not names.

People need names. Agents need ids. Neither needs a guess.