- 08 Oct 2025
- 3 Minuten zu lesen
- Drucken
- DunkelLicht
- pdf
Understand Advanced Visibility Rules for Content
- Aktualisiert am 08 Oct 2025
- 3 Minuten zu lesen
- Drucken
- DunkelLicht
- pdf
Note:
Advanced Visibility Rules are available as Visibility Rules and Element Precision Rules on Studio. Currently, this update is in the Beta stage. To enable this feature, contact support@whatfix.com.
Overview
Whatfix enables you to configure Advanced Visibility Rules using Studio for various content such as Flow steps, Launchers, Beacons, and Branching in Flows.
When you configure Advanced Visibility Rules in Studio, the rules apply only to the specific step (for example, an individual Flow step) and not the entire Flow or other content.
Advanced Visibility Rules on Studio enable you to:
Target elements precisely, ensuring guidance appears exactly where it’s needed.
Continuously observe user input and display guidance dynamically based on user interactions.
Create a more personalized experience by showing content based on conditions such as date range, something on the application, user performing an action, and more.
Ensure content appears accurately in the intended location.
Note:
Click the following accordions for more details.
Visibility Rules
Visibility Rules enable you to determine where, when, and to whom content is displayed. When you configure Visibility Rules in Studio, the rules apply only to a specific step.
The following table lists all the conditions used while configuring the Visibility Rules for content. Such conditions determine when, where, and to whom content is displayed on your application.
Clause | Visibility Rule Condition | Corresponding Previous Display Rule Condition | Description | Supported content types (Flow steps, Smart Tips, Beacons, Launchers, Blockers) |
---|---|---|---|---|
When does the content start appearing? | Specific date range | NA | Show content if the current date and time fall within the specified range. | Flow steps, Beacons, Smart Tips, Launchers, Blockers |
Something on the application | Other Element on Page | Show content based on the presence of a specific element on the page. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
User performing an action | Based on user action | Previously available under Smart Tip Triggers, this rule enable you to show a Smart Tip when the end user interacts with a specific element on your application. | Smart Tips, Blockers | |
Events related to Whatfix content | NA | Show content based on callbacks from existing content or widgets, such as Flows, Pop-ups, and Surveys. | Blockers | |
Where does the content appear? | URL | URL | Show content when the current page URL matches the specified URL | Flow steps, Beacons, Smart Tips, Launchers, Blockers |
Domain | URL Hostname | Show content when the domain of the current page matches the configured domain. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
URL path | URL Path | Show content when the path of the current page URL matches the specified path. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
URL parameter | URL Parameter | Show content when the current page URL matches specified parameter(s). | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
URL hash value | URL Hash |
Show content if the hash value in the URL matches the specified value. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
Page tags | NA | Show content if the page matches the specified page tags. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
Who does the content appear to? | Enterprise Attributes | Enterprise Attribute | Segment content based on user roles, departments, geography, accounts, and more. | Flow steps, Beacons, Smart Tips, Launchers, Blockers |
User Attributes | User Attribute | Segment content based on end-user information from your application. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
Cohorts
| NA | Show content to specific user groups (Cohorts) based on certain use cases. | Flow steps, Beacons, Smart Tips, Launchers, Blockers | |
Salesforce Objects
| NA | Salesforce Lightning objects are properties that help Whatfix serve relevant content to Salesforce Lightning users based on existing Salesforce Lightning properties that help identify different users. Using Salesforce Lightning objects helps you to show relevant content to your users. | Flow steps, Beacons, Smart Tips, Launchers, Blockers |
For more information on Visibility Rules for various content types, see:
Element Precision Rules
Element Precision Rules help ensure that content appears on the correct UI component, preventing misalignment or flickering. Such rules provide precise control over positioning, ensuring the content consistently appears in the intended location.
Types of Element Precision Rules
Rule | Description | Example |
Using CSS selector | Identifies an element using a CSS selector. It is useful when elements have unique identifiers or specific class names. CSS selectors help in precisely targeting elements based on attributes such as class, ID, or hierarchy. | Display the content if an element with .help-button exists. |
Using jQuery selector | Identifies an element using a jQuery selector, which enables more advanced element selection, including filters and conditions. It is useful when you need to select elements dynamically based on complex conditions. | Display the content when an element matching |
Using Element Text | Identifies an element based on the visible text it contains. It is useful when targeting buttons, labels, or other text-based elements. | Display the content if the button text is Log in. |
Note:
Adding CSS Selectors ensures that Whatfix can easily find the required element and reduce the chances of displaying content on the wrong element.
For more information on Element Precision Rules for various content types, see: