Documentation
Current user
A user id on events turns event counts into people counts.
What it does
When you send a stable user id with errors, Retrace Kit can attribute events to that account.
Use your own database id — not a session token (tokens rotate; ids do not).
Aggregation
With id on events:
- Users column on the issues table — distinct people per issue
- prioritization — many events from one tester vs many accounts
- filtering internal noise (pair with
environmentor tags)
In the dashboard
On an issue, the latest event and the affected users list show the id you sent. Look up name, email, or account details in your own systems — Retrace Kit stores only the id.
Privacy
Send only identifiers you are allowed to store. An internal user id is enough for counts and follow-up — no need to put email or other PII into Retrace Kit.
In the SDK
Call setUser({ id }) after login (and clear or replace it on logout). API:
SDK → Current user.