Identify Users

Identify a user.

You can call setIdentity to associate users in Fullstory with your unique customer IDs. If you call setIdentity after a user login operation, that user will be associated with the FullStory session until an anonymize user call is made.

Depending on how your login flow works, you may choose to call setIdentity on every page, just to ensure that any post-login redirects capture the ID of the logged in user.

Type annotations for properties are no longer required. See Custom Properties.

Parameters

uid string required

A string containing your unique identifier for the current user.

properties object optional

A JSON object with key/value pairs that provides additional information about your user.

schema object optional

A JSON object with key/value pairs that provide explicit type inference for your properties. See Custom Properties.

Re-identification

Fullstory doesn't let you change the identity of a user once they have been assigned a unique user ID using FS('setIdentity'). If you attempt to change the user id of an identified user, Fullstory will recognize the new user ID and automatically split the session into a new session.

Limits

• Sustained calls are limited to 30 calls per page per minute with a burst limit of 10 calls per second.

Additional Information

• Identifying users
• If you only want to pass in properties you can use the FS('setProperties') function.
• Can I change a user's identity using FS('setIdentity')?
• Property name requirements
• Property value requirements

FS('setIdentity', { uid, properties })

Example Invocation

FS('setIdentity', {
  uid: '462718483',
  properties: {
    displayName: 'Daniel Falko',
    email: 'daniel.falko@example.com',
    custom_field: 1
  }
});