# Distinct IDs (https://talivia.com/docs/distinct-ids)



Talivia is anonymous by default. The tracker creates a visitor key and session key in browser storage, then records page views without requiring a user id.

Use `identify` when your app knows who the visitor is.

```js
window.talivia.identify('user_123', {
  email: 'founder@example.com',
  name: 'Founder',
});
```

## Payment customer fields [#payment-customer-fields]

Talivia recognizes common payment/customer fields:

```js
window.talivia.identify('user_123', {
  stripeCustomerId: 'cus_123',
  providerName: 'stripe',
  providerCustomerId: 'cus_123',
  externalCustomerId: 'user_123',
  emailHash: 'sha256-email-hash',
});
```

These fields help connect Stripe or manual payments back to the visitor, especially when checkout happens later.

## What identify does [#what-identify-does]

Identify sends an `identify` collection event, stores session data, and links the current visitor/session to the customer identity.

## When to call it [#when-to-call-it]

Call identify after login, signup, account creation, or whenever a new payment customer is created.