Skip to main content
Without identify, sessions still arrive, but nobody can tell whose they are. An investigation into “Priya cannot export her report” needs Priya’s session, and identify is how Hinto finds it.

When to call identify

Call identify wherever the signed-in user becomes known. Call it again after a user switch, and call identify(null) at sign-out.
With Native Support, the conversation runtime sets the identity: { kind: "external_id" } with the support token’s sub. Do not call identify with an email or any other kind once support runs. It replaces the identity the conversation checks, and every send fails. Put the name, email, and company in the support token instead.
You can also identify by your own user id:

Optional fields

Since 0.3.0 you can pass optional fields that improve the customer record in the Hinto console:
When name is omitted, the customer record uses the identifier itself (for example the email address).

Identify for Native Support

Native Support requires an external_id identity. Identify with the same id the support token carries in its sub claim: the id your server signs, or, when the token comes from your sign-in provider, that provider’s user id (Supabase session.user.id, Firebase user.uid, Clerk userId, Auth0 user.sub):
The support conversation does not read name, email, or company from identify. Put them in the signed support token as the name, email, and company claims, read from your server session. See Issue a token on your authenticated server. A token from your sign-in provider gives the name, and the email only when the provider marked it verified. See Use your sign-in provider’s token. When the support token’s sub differs from the subject the app passes, the SDK refuses the token with auth_invalid before it reaches Hinto.

What happens without identify

Sessions arrive unattributed. Investigations cannot cite them as evidence for a specific customer. The SDK step in onboarding stays waiting until a session with a linked customer is received.