Integrate Checksum SDK
- Add Checksum SDK To Your Main HTML
- Initialize Checksum as soon as your app is mounted.
- [Optional] Identify user login and logout
When the user logs in, identify the user (you can use any consistent ID. Checksum does not need to know the user identity)
When the user logs out, reset
Simply explained, without any filters or masks, the collection includes data necessary to reconstruct the web page. This includes assets such as CSS files, text, image URLs, HTML elements and inner text (in JSON format), and user activity like clicks and types.
However, we do offer very strong privacy tools to minimize user data processed by Checksum. There are a few levels of protection:
- Hashing: Checksum can hash all inner text and input values automatically for all elements on the client side, so the raw data doesn’t leave your user browsers.
- Masking: Checksum automatically replaces inner text with “*” automatically for sensitive elements like passwords, zip code, SSN, email addresses, any text with only numbers. You can also customize which elements are masked.
- Blocking: On very rare occasions, hashing and masking the inner text and inputs is not enough. For example, when sensitive data is added to HTML attributes or when just the interaction with an element might be sensitive regardless of the inner text. In that case, you can manually block the entire elements and all related events.
By default, Checksum does not hash any text and only masks passwords. You can customize this behavior in Checksum by passing a
sessionRecording object to your init function as follows:
Hashing and Masking Example
A typical configuration, for example, would be to mask all sensitive elements and hash all text and inputs in production. For that, initialize Checksum as follows
Custom Masking Function
If you would like to customize which elements are masked, you can pass a custom masking function. For example, the code below will mask all elements of type search