Session Replay allows you to replay a web user session to see their interactions and browsing behaviour.
In order to use this functionality, you have the following implementation options:
Option 1: Mask Personal Information before sending the page content to ContentSquare
The HTML page content of the recorded pages will be sent to our servers, except for input and text-area fields.
You must make sure that all personal information is removed before this happens.
This can be done using a combination of:
- masking/unmasking full pages by their URLs
- masking/unmasking targeted HTML elements inside pages.
Applying Masking / Unmasking on a page level
You can choose to apply or remove anonymisation by URL path. This applies to both the URLs collected from natural and artificial pageviews.
As an example, this functionality would allow you to anonymise your checkout flow, which would most likely display PII, whilst removing the anonymisation from the rest of your site, clearly displaying most of the user-journey.
Enabling this functionality will not require any code changes and can be activated in our configuration by your dedicated Implementation Manager.
In order to proceed with this, please provide us with the URL pattern of the pages to whitelist/blacklist.
Applying Masking / Unmasking on targeted HTML elements
If the page is unanonymized, you can use the data-cs-mask data-attribute HTML page elements to prevent us from recording them.
The page will then be unmasked except from the hidden elements.
Important: This can also be done using CSS Selectors of the required elements without changing the actual elements (refer to the documentation link below).
If the page is anonymized, you can use the data-cs-capture data-attribute on HTML page elements to allow us to record them. The page will then be fully masked except from the unmasked elements.
Implementation instructions and suggestions can be found here: https://docs.contentsquare.com/uxa-en/#remove-content-from-the-recorded-html