Use the built-in filtering options available in Dashboards to refine and visualize data based on specific conditions.
Example: Filter all Insights in the Dashboard to show data for users from the United States.
Note:
Filters added to Dashboards function as an AND condition to the existing filters applied to Insights.
The Stage name filter applied in Dashboards takes precedence over the Stage selected within individual Insights. For example, if you set the Stage to Ready in an Insight but apply the Stage name filter as Production at the Dashboard level, the Dashboard filter overrides the Insight-level filter. Hence, the Insights data reflects the engagement in the Production stage.
There is no limit to the number of filters you can add to your Dashboards.
If you have multiple tabs in your Dashboard, the filters you apply are tab-specific.
The badge indicates the number of filters added.
The following table lists the filtering options associated with Dashboards:
Filters | Description |
Device Type | Filters data based on the hardware users use. Examples: Mobile phones, desktops, tablets, and more. Info: For more information on the different types of devices that are captured, see What are the device types captured by Product Analytics? |
Browser | Filters data based on the browser type users use to access the application. Examples: Chrome, Firefox, Edge, and more. |
OS version | Filters data based on the OS versions. |
Language | Filters data based on the browser language. Example: French(fr), Spanish(es), and more. |
Model | Filters data based on the model of the user's device. Example: Apple iPhone, Linux Desktop, and more. |
OS | Filters data based on the base software (Operating System OS) that runs on the hardware. Examples: iOS, Linux, Windows, and more. |
City | Filters data based on the city. This data is taken from the browser. Examples: Dallas, Beijing, Bengaluru, and more. |
Country | Filters data based on country. This data is taken from the browser. Examples: United Kingdom, United States, and more. Info: Country names are shown as ISO country codes. |
Region | Filters data based on geographical region. This data is taken from the browser. Examples include Camden, Kerala, Central Province, and more. |
Event trigger page URL | Filters data based on where the event is launched. Example: https://salesforce.com/leads Note: The following conditions are available for the Event trigger page URL: Contains, Starts with, Ends with, Is equal to, and Not contains. For more information, see How do conditions in the Event Trigger Page URL work?
|
User Id | Filters data based on the ID from which the Whatfix event is triggered. Example: johndoe@whatfix.com. Note:
|
User type | Filters data based on whether Whatfix is able to detect and identify users by their User ID when they log in to the application. There are two types of users: identified and unidentified users. For more information, see How can I filter unidentified users in Product Analytics? |
User Attribute | Filters data based on the captured User Attributes, such as, role and department. |
Reserved variable 1 | Whatfix reserves two variables as placeholders for additional properties required when sending event data. Reserved Variables are those properties captured along with Default and Custom events. They are dependent on events and user interaction and capture data only when all necessary conditions are met. For example, you can set up a ‘session count’ Reserved Variable that will increment every time the user logs in. For more information, contact support@whatfix.com. Data is filtered based on these additional properties. |
Reserved variable 2 | Whatfix reserves two variables as placeholders for additional properties required when sending event data. Reserved Variables are those properties captured along with Default and Custom events. They are dependent on events and user interaction and capture data only when all necessary conditions are met. For example, you can set up a ‘session count’ Reserved Variable that will increment every time the user logs in. For more information, contact support@whatfix.com. Data is filtered based on these additional properties. |
Analytics Variable | Filters data based on the captured Analytics Variables, such as Context Variables and User Attributes configured in Advanced Customisation. For more information, see Configure Analytics Variables. |
Stage name | Filters engagement data based on the stage (Ready or Production) in which the Whatfix content or widget is present. |
Cohort | Filters data based on the Cohorts users belong to. For example, filter new users (grouped using specific conditions as a Cohort) who engage with a feature. |
User List | Filters data based on the User Lists users belong to. For example, evaluate Task List completion for users added during a training program. |
Extension version | Filters data based on the browser Extension version in use. |
Extension name | Filters data based on the different browser Extension names. |
- To exclude specific filter values for which you don't require data, see How can I exclude filter values in Product Analytics?
- To exclude blank filter values from your data, see How can I exclude blank filter values in Insights?