Whatfix enables you to configure Session Replay settings to control how sessions are captured and how sensitive information is handled across your application. You can define which URLs to activate for session capture and set conditions to determine which sessions get recorded. This includes masking Persönlich identifizierbare Informationen (PII) such as email addresses, phone numbers, and passwords, or masking all input fields entirely.
For example, in an e-commerce application, you can capture sessions on your product listing and cart pages but exclude the checkout page where users must enter payment or personal details.
Use the following steps to configure Session Replay settings:
On the Whatfix Analytics Dashboard, click Settings.
Under Analytics, click Session Replay.
To add a capture rule and define which sessions Whatfix records, click + Add rule.
Enter a name for the capture rule.
Under Where do you want to capture sessions from?, select a condition from the Capture on dropdown.
Info:
Expand the following accordion to learn more about the capture rule conditions:
Where do you want to capture sessions from?
Define the specific pages of your application, using URL or page conditions, where Whatfix captures sessions.
The following table lists all the where conditions you can set for the capture rule:
Capture on
Description
URL
Use this condition to show the widget on the entire URL specified.
Domain
Use this condition to show the widget on a specific domain. The domain or the hostname is the first part of the URL.
URL path
Use this condition to show the widget on a specific section of a URL. The section or path is the part of the URL after the domain name but before parameters or hashes.
URL parameter
Use this condition to show the widget based on parameters in the URL.
URL hash value
Use this condition to show the widget based on the hash value of the URL. Hashes are often found in Single Page Applications developed using AngularJS or ReactJS.
Click + Add condition to include additional capture rules.
Choose OR or AND based on your requirements. For more information, see How to use AND and OR Conditions inside Widget Segments.
Under Who do you want to capture sessions for?, select a condition from the How would you like to identify the user? dropdown.
Info:
Expand the following accordion to learn more about the capture rule conditions:
Who do you want to capture sessions for?
Define the users whose sessions Whatfix captures, based on user types or attributes such as role, cohort, or enterprise-specific attributes.
The following table lists all the who conditions you can set for the capture rule:
Capture for
Description
Cohorts
Create Cohorts for specific users based on certain use cases to show Whatfix Inhalt. For example, show a Pop-up to new users who have spent 7 days or less in the system and have completed 3 Tasks about the latest version of the application. For more information, see Add Cohorts as Visibility Rules.
Note:
Adding Cohorts as Visibility Rules is a Beta feature. For more information, contact support@whatfix.com.
User Attributes
If you need to segment content based on end-user information from your application, User Attributes enable you to fetch this data for use within Whatfix. For more information, see Attributes as Visibility Rules.
Enterprise Attributes
Attribute condition rules enable you to fetch specific information based on roles, departments, geography, accounts, and more, and segment content to show to particular users. Once the attributes are integrated with Whatfix, you can see them in the visibility rules of widgets for content segmentation. For more information, see Attributes as Visibility Rules.
If you need to fetch your application information for content segmentation, Enterprise Attributes can enable you to fetch this data for use within Whatfix.
Roles
Whatfix enables you to show different content to different users with the use of Role tags. For example, an admin user can be shown more and different content when compared to a basic user. This helps in targeting information based on what users can do on your application. For more information, see Tags as Visibility Rules.
Click + Add condition to include additional capture rules.
Choose OR or AND based on your requirements. For more information, see How to use AND and OR Conditions inside Widget Segments.
Click Save.
To manage what information to mask or block for compliance, click Manage privacy.
Under Input masking, select the required option to apply additional masking beyond mandatory fields.
Info:
Use the following options:
Secure Fields (Mandatory): By default, Whatfix masks input fields where users enter passwords or authentication credentials, such as login or account verification fields.
Contact Info (Mandatory): By default, Whatfix masks input fields that capture personally identifiable information such as email addresses or phone numbers.
Standard Text: Input fields where users enter plain text or messages, such as contact form fields or comment boxes.
Date and Time Selection: Input fields where users select a date or time, such as booking, appointment, or date-of-birth fields.
Number or Range: Input fields where users enter or select a numerical value or range, such as age, quantity, or price filter fields.
Dropdown Menus: Input fields where users select an option from a predefined list, such as country, category, or preference selectors.
Search: Input fields where users enter search queries to look up content or products within your application, such as a product search bar or a help center search field.
Inline Text Editors or Rich Text Fields: Input fields where users enter freeform text, such as support tickets, feedback forms, or detailed notes.
Note:
Choose Maximum Privacy to mask all text and input values across all input fields during session capture. This option disables all individual input masking selections. In such cases, session replays do not display any text content.
Under CSS Selector, enter the CSS selector for the element you want to target. Use this to define the exact elements Whatfix must mask or exclude from session replays.
Info:
Click + Add rule to include additional CSS Selectors.
Under Action, choose one of the following options based on your requirements:
• Mask with ‘*’: Masks all content captured in the specified CSS selector with an asterisk (*). Visible text and input values appear as ‘*’ characters in the session replay.• Block element: Excludes the targeted element from session capture and displays it as an empty placeholder in session replays.
Click Save.
Enable the Session Replay toggle.
The following video shows how you can configure Session Replay settings to mask an address field with '*' and block a phone field from being captured entirely on the checkout page of an e-commerce application:
Info:
After you add the required capture rules and configurations, click Publish All to reflect your Session Replay settings in production. For more information, see Publish all Whatfix content and widgets to Production and Access Session Replay.