What has changed in the new Visibility Rules experience?
- 09 Oct 2025
- 2 Minutes To Read
- Print
- DarkLight
- PDF
What has changed in the new Visibility Rules experience?
- Updated On 09 Oct 2025
- 2 Minutes To Read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Consider a scenario where you need to trigger a Pop-up during the execution of a Flow or based on the value of an element within the underlying application. Until now, you have achieved such configurations only through Advanced customizations.
With the new Visibility Rules experience, Whatfix enables you to configure the rules for displaying Whatfix content based on content events such as Flow Start, Pop-up closed, and more. Set up rules to display Whatfix widgets based on the data or elements present in the underlying application, as well as specific user roles.
Note
The new Visibility Rules are currently available for configuring widgets at the segment level. However, Role Tags, Page Tags, Step Display Rules, and Branching Rules are still configured using the existing Visibility Rules, even after upgrading to the new Visibility Rules experience. Eventually, the new Visibility Rules will support these configurations as well.
To know more about the new Visibility Rules, contact support@whatfix.com.
Why switch to the new Visibility Rules experience?
Features | New Visibility Rules | Existing Visibility Rules |
|---|---|---|
Triggers for widget display | Show widgets based on an extensive list of triggers such as:
| Existing Visibility rules offer limited triggers. |
Ease of use | New Visibility Rules have intuitive conditions with easier terminology and descriptions in a dedicated section. | Existing Visibility rules have complex terminology, which is not user friendly. |
User segmentation | Separate the Who section to segment content for user groups based on several conditions. | No dedicated section for user segmentation. |
Advanced use cases | Advanced use cases are easily achievable using the new Visibility Rules. For example, multiple content is linked using the Events related to Whatfix content rule as compared to using AC code earlier. | Limited opportunities to implement advanced use cases. Content creators need to configure AC code to achieve them. |
How do the new Visibility Rules differ from the existing Visibility Rules?
Criteria | New Visibility Rules | Existing Visibility Rules |
|---|---|---|
Widget evaluation | Evaluation of widgets is based on immediate conditions (Instant Action) or specific events or user actions (Scheduled Action). For more information, see Understand how content is shown based on the new Visibility Rules. | Evaluation happens based on page load or tag change. |
Widget prioritization | Widgets are prioritized dynamically based on multiple factors such as widgets linked to Whatfix events, User actions, number of conditions, and the most recent modification time. For more information on widget prioritization, see Understand the Prioritization Criteria in the new Visibility Rules. | Widgets are prioritized in a static manner, based on set conditions. The most recently modified widget appears first. |
Dynamic widget visibility | Widget visibility is continuously monitored, enabling dynamic display even after the page loads. Widgets automatically appear, disappear, or are replaced based on real-time conditions without page refreshes. For more information, see Understand Widget Behavior with the new Visibility Rules. | Widgets are evaluated after the page loads or when page tags change. Only one widget is displayed on the page. |
Note
To use the new Visibility Rules experience on existing widgets, you need to upgrade to the new Visibility Rules experience. For more information, see Upgrade your widgets from existing Visibility Rules to the new Visibility Rules.
Was this article helpful?