Users
Easily tag and identify users with errors, session replays, and traces.
Overview of User Fields
Users in Decipher are identified by calling Sentry.setUser
and passing at least one of the following fields:
- email: The user’s email address. This is the strongly recommended identifier if available.
- id: Your internal identifier for the user.
- username: The username, typically used as a more readable label than the internal id.
Below is the full list of natively supported fields in Decipher, but you can add any arbitrary key/values in the setUser
call as well.
Field in setUser | Meaning |
---|---|
email | Recommended identifier to set |
id | Optional: use if email not available |
username | Optional: use if email not available |
account | Recommended: Which account/organization is this user a member of? |
created_at | Recommended: date this user signed up |
role | Optional: what is this user’s role/type? |
We strongly recommend providing the created_at
field to tell Decipher when the user originally signed up.
You can also provide arbitrary additional key/value pairs beyond these reserved names, and Decipher will store them with the user information. For example,
you can set a key like “paymentTier” to values like "free"
or "paid"
to represent your user’s payment plan, and any other field specific to your application or users
Anywhere in your application where you have user information, call the setUser
(or set_user
, depending on language) method.
setUser
in your frontend to ensure replays are tagged correctly.