Use Filters in Custom Dashboards
- 24 Feb 2025
- 3 Minutes To Read
-
Print
-
DarkLight
-
PDF
Use Filters in Custom Dashboards
- Updated On 24 Feb 2025
- 3 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
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 of users from the United States.
Info
- Filters added in Dashboards function as an AND condition to the existing filters applied to Insights.
- 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. Example: Mobile phones, desktops, tablet, 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. Example: Chrome, Firefox, Edge, and more. |
| City | Filters data based on the city. This data is taken from the browser. Example: Dallas, Beijing, Bengaluru, and more. |
| Country | Filters data based on the country. This data is taken from the browser. Example: United Kingdom, United States, and more. Info The country names are shown as ISO country codes. |
| Event trigger page URL | Filters data based on where the event is launched. |
| User Id | Filters data based on the ID from which the Whatfix event is triggered. Example: johndoe@whatfix.com. Note
|
| Extension version | Filters data based on the browser Extension version in use. |
| OS version | Filters data based on the OS versions. |
| Extension name | Filters data based on the different browser Extension names. |
| Reserved variable 1 | Whatfix reserves two variables as placeholders for additional properties required when sending event data. Reserved Variables are these 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 these 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. |
| User Attribute | Filters data based on the captured User Attributes, such as, role and department. |
| Language | Filters data based on the browser language. Example: French(fr), Spanish(es), and more. |
| Region | Filters data based on the geographical region. This data is taken from the browser. Example: Camden, Kerala, Central Province, and more. |
| Model | Filters data based on the model of 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. Example: iOS, Linux, Windows, and more. |
| 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? |
| 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. |
| Stage name | Filters engagement data based on the stage (Ready or Production) in which the Whatfix content or widget is present. |
Info
- To exclude specific filter values for which you don't require data, see How can I exclude filter values in Product Analytics?
- By default, Product analytics data may contain identified users (identified by User ID) and unidentified users (not identified but denoted by cookie values) users. To filter unidentified users for clearer data, see How can I filter unidentified users in Product Analytics?
Was this article helpful?