During Plug SDK initialization, you can provide custom attributes for session recording options. If no custom attributes are specified, the default options are used.
Plug SDK offers the ability to hide sensitive user information by masking it in session recordings. During session replays, masking replaces user-visible or typed content in specific elements with asterisks ("*"). This ensures that sensitive information is not displayed in the recordings, protecting user privacy.
During Plug initialization, you have several options to manually configure which elements should be masked. Masking is applied based on the element's ID, allowing you to control which specific fields are protected in the session replay.
1window.plugSDK.init({
2// Please ensure you replace the app_id with your unique app ID
Whether all input elements (irrespective of their types) should be masked during session recording.
False
maskInputOptions
Whether specific input element types should be masked during session recording.
The masking preference applies as follows: input elements with types email, tel, or password are masked during session recording, while other input types are not masked. For example, <input type="email"/> is masked, but <input type="text" name="email"/> is not masked.
captureMouseMove
Whether to capture the full mouse movement throughout the session or only track mouse clicks.
False
captureNetworkLogs
Whether network logs should be captured during the session.
True
captureConsoleLogs
Whether the session captures console logs or not.
True
recordCrossOriginIframes
Whether interactions occurring within the chat widget and search agent should be captured or not.
True
sessionDetails.sessionId
Field to pass session ID of the previous session to link.
null
sessionDetails.tabId
Field to pass the tab ID of the previous session to link.
null
maskTextFn
An option to customize the logic for masking sensitive text during session recording. This function accepts a callback that receives the text content and allows you to define how the text should be masked
In addition, you can use the following CSS classes to mask or unmask specific elements on your webpage:
Purpose
CSS classes
To mask all page elements, add the CSS class ue-mask to your app's body tag.
<body class="ue-mask"> ... </body>
To mask a specific element during capture, apply the CSS class ue-mask to it.
<div class="ue-mask"> Hello World </div>
Apply the ue-mask CSS class to images to mask them with a black overlay during capture.
<img class="ue-mask" src="…" >
Use the CSS class ue-input-mask to mask input elements, displaying their data as *** in session replays. NOTE: Password fields are masked by default, but applying the ue-input-mask class adds extra security.
<input class="ue-input-mask"/>
Use the CSS class ue-unmask to unmask text and input elements. This also unmasks texts found in child elements as well. For input fields, it is only applied on the direct input element consisting the class.
<div class="ue-unmask"> Hello World </div>
To block input data from being captured in the session replay, apply the ue-block class. This prevents the SDK from recording the input.
<input class="ue-block"/>
You can set a custom label for an element using the data-plug-label attribute, and this label appears in the web player timeline.
Attribute
Description
Example
data-plug-label
Custom attribute to set an element's label in the web player timeline.