Identify users

Call identify after sign-in

window.revfaro?.('identify', {
  user_id: user.id,
  email: user.email,
  name: user.name,
});

All three fields are optional, but send at least one. Call it:

• right after a successful sign-up or login, and
• when your app loads for a visitor who is already signed in.

The script must be on the page; if your code can run before it loads, add the queue snippet first.

Identify with the npm SDK

For an npm SDK installation, use your shared tracker instance:

tracker.identify({ user_id: user.id, email: user.email, name: user.name });

The SDK includes its own TypeScript definitions and does not create window.revfaro. The script queue and global declaration below apply only to script installations.

What identify changes

Real names instead of nicknames. Anonymous visitors get a friendly generated name such as "teal fox" and an illustrated avatar, so you can tell them apart. Once identified, the visitor shows their name (or email) in Journey, Users, the visitor profile and goal alert emails. Their earlier anonymous visits stay part of the same profile.

More payments matched. When a payment arrives without a visitor ID, Revfaro looks for a visitor you identified with the same email as the buyer. See how payments are matched.

Search by name or email. The search box on the Users and Journey tabs finds identified visitors by name or email.

Details

• user_id can be up to 128 characters, email up to 200 and name up to 128. Emails are stored in lower case.
• Calling identify again with new values replaces the old ones.
• Identify works with the cookieless script too, for the day the visitor is recognized.
• Using TypeScript? Declare window.revfaro once so the calls type-check:

declare global {
  interface Window {
    revfaro?: ((cmd: 'goal' | 'identify' | 'pageview', a?: unknown, b?: unknown) => void) & {
      attribution?: () => { rf_visitor_id?: string; rf_session_id?: string };
    };
  }
}
export {};