Use Filters in Custom Dashboards
- 03 May 2024
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Use Filters in Custom Dashboards
- Updated On 03 May 2024
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
You can use the built-in filtering options available in your Dashboards to refine and visualize data based on a specific condition.
Your title goes here
- The filters added in Dashboards are included as an AND condition to the existing filters applied on Insights.
- There is no limit to the number of filters you can add to your Dashboards.
The following table lists the filtering options associated with Dashboards.
| Filters | Description |
| Device Type | Users are filtered based on the hardware they use. Example: Mobile phones, desktops, tablet, and more. |
| Browser | Users are filtered based on the browser type they use to access their websites. Example: Chrome, Firefox, Edge, and more. |
| City | User is filtered based on the city. This data is taken from the browser. Example: Dallas, Beijing, Bengaluru, and more. |
| Country | User is filtered based on the country. This data is taken from the browser. Example: United Kingdom, United States, and more. Your title goes here The country names are shown as ISO country codes. |
| Event trigger page URL | User is filtered based on where the event is launched. |
| User Id | User is filtered based on the ID from which the Whatfix Event is triggered. Example: johndoe@whatfix.com. Your title goes here
|
| Extension version | Users are filtered based on the browser Extension version they are using. |
| OS version | User is filtered based on the OS versions. |
| Extension name | User is filtered based on the different browser Extension names. |
| Reserved variable 1 | Whenever Whatfix sends any event data, two variables are reserved as placeholders for any additional properties that may be required. 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. Users are filtered based on these additional properties. |
| Reserved variable 2 | Whenever Whatfix sends any event data, two variables are reserved as placeholders for any additional properties that may be required. 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. Users are filtered based on these additional properties. |
| User Attribute | User is filtered based on the captured User Attributes, such as, role and department. |
| Language | User is filtered based on the browser language. Example: French(fr), Spanish(es), and more. |
| Region | User is filtered based on the geographical region. This data is taken from the browser. Example: Camden, Kerala, Central Province, and more. |
| Model | User is filtered based on the model of their device. Example: Apple iPhone, Linux Desktop, and more. |
| OS | User is filtered based on the base software(Operating System OS) that runs on the hardware. Example: iOS, Linux, Windows, and more. |
| User type | Users are filtered based on whether Whatfix is able to detect and identify 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? |
Was this article helpful?