FullStory doesn't let you change the identity of a user once they have been assigned a unique user ID using FS.identify. If you attempt to change the user id of an identified user, the action will generate a highlight warning you of the issue. (For example: "The user previously identified as "Alice" cannot be changed to be identified as "Bob".)
It's not that we don't approve of self-determination; the problem is that there are a lot of different things such a change might mean, and no way to separate them.
We can't tell, and some of those would be hard to do (although we are looking at exactly what would be involved). Because of that, identity is permanent. If you try to change it once assigned, the new identity and any variable assignments set in that call to FS.identify will be ignored.
Identity is stored as part of the "user cookie," so if you discover that an identity has changed (for example, if two of your users share a computer and browser profile), you might use FS.clearUserCookie on your login page, to start a new session and to get rid of any old identity.
Specifically, we recommend calling
FS.clearUserCookie(true) in this sort of situation. The
true parameter will allow anonymous users to keep their existing, un-identified cookie.
User Variables set using FS.setUserVars 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 spends on your site, or update displayName and email if the user changes their contact information. However, as described above, you can't change their core identity.
The FullStory team awaits your every question.Contact Us