User identification

Put a name to the visitor.

Call `window.supr("identify")` when someone signs up or signs in, and their name and email appear in the live view, their journey, the Inbox and the recordings list. Their earlier visits stay attached.

Start free trial How it works

14-day free trial · No card required · From $9/month

One call after sign-in.

window.supr("identify", { user_id: "usr_123", email: "ada@example.com", name: "Ada Lovelace" }). Send any of the three; calling it again replaces the values.

Where the name shows.

Anonymous visitors get a friendly alias, like "brown slug". Identified ones are named everywhere you see them.

Live view and journeys: Their name and avatar on the live view and the User panel, and their journey found by name or email.
Inbox: Chats from an identified visitor carry their name or email instead of an alias.
Recordings: The recordings list shows the visitor's name or email.
Goal alerts: Alert emails can include {{visitor.name}} and {{visitor.email}}.
Payments: A payment that arrives without a visitor id is matched to the visitor with the same email.
Retention: Every browser identified with the same user_id counts as one person in the retention report, on any device.

What stays private.

Names and emails never appear on a public dashboard. Payments name visitors too: the email and name from your payment provider are added to a visitor who doesn't have them yet.

How it works, in detail.

The docs page “User identification” goes through it step by step.

How it works

Limits worth knowing

A journey follows one browser: the same person on a phone and a laptop has two journeys
Only the Retention report counts a person's browsers as one, by user_id
Only user_id, email and name are kept; other fields are dropped
There's no identify call from the server; identify in the browser after sign-in

Questions, answered.

When should I call identify?

After signup, after login, and when a signed-in session loads, so returning users are named on every browser they use.

Are earlier visits linked?

Yes. Identify names the browser's visitor, so the visits it made before signing in and the ones after are on the same journey.

Does it merge a person's devices?

Not in journeys: each browser stays its own visitor. The Retention report is the one place that counts browsers with the same user_id as one person.

Can I send events for a known user from my server?

Yes, with their visitor id and the goals API. A payment sent with an email also names the visitor when they have no email yet.

Are names shown on public dashboards?

No. Names and emails stay private, along with journeys and single payments.

More features

All features

See it on your own website.

Every feature is on every plan, with a free trial and no card.

Start free trial

14-day free trial · No card requiredPricingHow it worksAll features