Use the Session Replay module to find replays for a specific user based on a unique identifier. Use this feature to help investigate the root cause of issues detected in Session Replay and to identify user pain points.
What is the user identifier
A user identifier is a unique value used on websites, apps, or online services to identify a specific user.
For example:
- User name
- Account number
- Email address
How do we encode data?
As these values are typically Personal Identifiable Information, from the moment the Tracking Tag is collecting the user identifier, we immediately encode the value using a hashing algorithm so that the information is hidden and can never be accessed.
Before being hashed, the collected value is first passed through the trim
function and then tolowercase
function. This means that searches are not case sensitive and leading/trailing space are not taken into account.
What is the difference between the CS user ID and user identifier?
CS user ID | User identifier |
A number | An explicit identifier |
Randomly generated | Supplied by end user |
Anonymous data | Private/personal data |
Stored as is in the database | Encoded data |
How to implement a specific page event
Collecting the user identifier value requires a trackPageEvent command and a pageEvent request. (A specific page event with additional characteristics is required):
- specific prefix: @user-identifier@
- the prefix will route the request to the right place, no additional parameters are needed
Example:
window._uxa.push(['trackPageEvent','@user-identifier@hubert.blabath@oss.com']);
- specific data processing:
- the data is immediately hashed (encoded in a one way format)
- the data is then stored in our database
How to use the user identifier in Session Replay
In the Session Replay module enter the value for your search into the user identifier search box. You can use multiple values for your search (for example: First Name, Last Name, email etc) however you can only use one value at a time in the search box.
Searches are not case sensitive. E.g. jon.snow@gmail.com is considered the same as Jon.Snow@gmail.com
Searches are space-sensitive and special character sensitive.