Identify users

After a user logs in, call:

rc("identify", "user_123", { name: "Jane Doe", email: "[email protected]" });

The first argument is a stable id from your system. The second is optional traits: up to 20, each a string, number or true/false. Anything else (null, an object, a list) is left out, and the rest are kept; text is cut at 256 characters, keys over 64 are dropped. An empty or missing id is ignored.

Each call adds to what is known about the person: sending { plan: "pro" } later keeps the name sent earlier. A different id means a different person, and starts fresh.

If the script may not have loaded yet when you call it, add this line first and early calls are queued:

window.rc = window.rc || function () { (window.__rcq = window.__rcq || []).push([].slice.call(arguments)); };

Send name and the dashboard calls them that everywhere - the people list, the recordings list, the person drawer and any alert that goes to email or Slack. Without a name it falls back to the email, then to the id you passed, then to Visitor 53f51ebb. The id is never preferred over something a person can read: an internal user id or a UUID is the identity, not the label.

Keep the id stable and unique. It is how two browsers are recognised as the same person: the People page shows one row per person, with every browser they have used, and visits made before they signed in on a browser join them too. So it should be your user's row id, not their name: two people called Jane Doe would otherwise become one, and anyone who changes their name would become two.

Call it on every page load where the user is logged in, not just once at login, because sessions can start on any page.

When somebody logs out, call:

rc("reset");

What was recorded so far stays with them, and the browser starts again as a new, anonymous visitor, so whoever uses it next (a shared computer, a family laptop) is not filed under their name.

Never send passwords, tokens, balances, or anything you would not want stored. Traits are stored as plain text on the session.

Search on the Recordings and People pages and in the top bar matches the name, the id, the email, the anonymous visitor id, or a name or email the visitor typed into chat, and shows the whole person it finds.