Note: We officially released V2 of our Identify Users Browser API (e.g.
setIdentity)
on
November 1st, 2023. If you're still using V1 of our Browser API (e.g.
FS.identify),
please refer
to
our V1 API documentation found
here.
If you were using Fullstory prior to August 3rd, 2023 and aren't sure which version of our Browser API is compatible with the data capture snippet deployed on your website, please refer to these instructions to confirm.
Once a unique User ID has been assigned using our Identify Users API, it cannot be changed for a specific user.
If you were to call our Identify User API on a previously identified user using a different User ID (uid), the session will automatically be split into a new session and a new User will be created in Fullstory.
The User ID value in question refers to the first parameter (uid) of the API call. Here's how it appears within the Fullstory user interface when viewing an individual session:
What about User Variables?
Note: We officially released V2 of our Set User Properties Browser API (e.g. setProperties) on November 1st, 2023. If you're still using V1 of our Browser API (e.g. FS.setUserVars), please refer to our V1 API documentation found here.
If you were using Fullstory prior to August 3rd, 2023 and aren't sure which version of our Browser API is compatible with the data capture snippet deployed on your website, please refer to these instructions to confirm.
Other user variables set using either our Identify Users API or our Set User Properties API are not static and can be changed as the user's information changes.
For example, you might update a user variable like lifetimeValue_real each time a user purchases something on your site, or update the displayName and email if the user changes their contact information. However, as described above, you can't change their core User ID value.
If you're interested in learning how to search for historical user variables, please check our this help article.