Docs Set up your stack

Identify your users

Tell Relia who your signed-in users are, so a problem names the people it hit ("3 customers on Pro") and you can look anyone up on the People page.

Without this, when something breaks Relia can only say "3 visitors". Once it knows your users, it says "3 customers on Pro", and you can find any person by e-mail, name or id. It takes one or two lines in your code.

Before you start

Steps

In your web app

  1. Where sign-in finishes, and when an already signed-in user loads the app, call Relia.identify with the user's id and details:

    import { Relia } from "relia-sdk"
    
    Relia.identify(user.id, { email: user.email, name: user.name, plan: user.plan })
    

    Calling it again with the same id updates the details, for example after an upgrade.

  2. On sign-out, call:

    Relia.reset()
    

With Supabase or Firebase, set it up once next to the client:

// Supabase
supabase.auth.onAuthStateChange((_e, session) =>
  session ? Relia.identify(session.user.id, { email: session.user.email }) : Relia.reset())

// Firebase
onAuthStateChanged(auth, (u) =>
  u ? Relia.identify(u.uid, { email: u.email ?? undefined, name: u.displayName ?? undefined }) : Relia.reset())

On your server

Servers send only the user's id and plan, never an e-mail.

  • Node.js (Express): nothing to add if your sign-in sets req.user.id; Relia reads it by itself. To add the plan, or if your user lives elsewhere:

    require("relia-sdk/node").setUser(req, { id: user.id, plan: user.plan })
    
  • Python: where your app knows the signed-in user (a dependency, middleware or view):

    import relia
    relia.set_user(user.id, plan=user.plan)
    
  • Laravel: the signed-in user's id is sent by itself. To add the plan, call this in a middleware:

    \Relia\Relia::setUser(auth()->id(), auth()->user()?->plan);
    

    In plain PHP, call \Relia\Relia::setUser($userId, $plan) once the user is known.

  • Other languages (OpenTelemetry): set the span attributes relia.user_id and relia.user_plan on the request span.

Tip: your AI assistant can add these lines for you. Ask it to Set up Relia in this repository and say yes to the users question. See Set up Relia with your AI assistant.

What Relia keeps

  • The user's id, e-mail, name and plan. You may add up to 12 plain custom details of your own, about 1 KB in all.
  • Details that look like secrets or sensitive data (passwords, tokens, card numbers, phone numbers, addresses, health data and similar) are dropped in the browser and again on Relia's servers. Pass only id, e-mail, name and plan.
  • Who your users are is never sent to the AI and never appears in alerts (e-mail, Slack). Alerts and AI explanations only use counts and plan names.
  • Visits from the same browser before the person signed in are added to their history.

The People page

Once users arrive, People in the menu lists them. Search by e-mail, name or id and filter by plan. Open a person to see their plan over time, sessions, requests and errors. Lists show e-mails partly hidden; every time someone opens a person's profile, it is recorded in the audit log.

Owners and admins can also:

  • Export everything Relia has on a person, as a file.
  • Erase their identity: their sessions stay, without the name, e-mail or details.

Check it worked

Sign in to your app once. On your project's Setup tab, Who your users are changes from Optional to Arriving, and the person appears on People.

On Growth and Pro (and during the Pro trial), incidents now say who was hit, such as "3 customers on Pro". On Free, incidents show what was found and how big it is; who was affected is part of the explanation that paid plans unlock.

Tip: watch How to read a production incident: what broke, who it hit, how to fix it (2 min).

If something's wrong

  • Still "Optional" after signing in: make sure Relia.identify runs after a successful sign-in, and also on page load for users who are already signed in.
  • Someone else's sessions under one person: call Relia.reset() on sign-out, so the next user on the same browser starts clean.
  • No plan shown: pass plan in Relia.identify, or with setUser / set_user on the server.

Next

Last checked against the product: 1 Nov 2026