Filter Insights data using User Filters and User Breakdown
- 25 Feb 2025
- 4 Minutes To Read
-
Print
-
DarkLight
-
PDF
Filter Insights data using User Filters and User Breakdown
- Updated On 25 Feb 2025
- 4 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
User filter
User filters enable you to limit the scope of events based on various criteria. It helps you drill down and gain granular insights by filtering data based on user attributes such as browser, city, country, and OS.
Info:
User filters are available in Trend, Funnel Insights, and User Journey.
For example,
Trend Insights: For the Flow start event, refine results to display data only for users who started the Flow from the Chrome browser or from a specific location.
Funnel Insights: For a specific Funnel event (Flow, User Action, or Page View), refine results to display data only for users who engaged with the Funnel steps from the Chrome browser or from a specific location.
User Journey: Understand the Journey followed by a specific user based on their User ID.
your title goes here
- 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 (users identified by User ID) and unidentified users (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?
User breakdown
User breakdown enables you to modify the chart and group users based on various properties. For example, for the Flow completed event with User filter set to the Chrome browser, configuring the breakdown as City, displays the chart based on all locations from which users completed the Flow using the Chrome browser.
Info:
User breakdown is only available in Trend Insight.
The following table lists the User filters and User breakdown available in Insights:
| Filters | Description |
| Device Type | Users are filtered based on the hardware they use. Example: Mobile phones, desktops, tablets, and more. Your title goes here For more information on the different types of devices that are captured, see What are the device types captured by Product Analytics? |
| Browser | Users are filtered based on their browser type to access their websites. Examples: Chrome, Firefox, Edge, and more. |
| City | User is filtered based on the city. This data is taken from the browser. Examples: Dallas, Beijing, Bengaluru, and more. |
| Country | User is filtered based on the country. This data is taken from the browser. Examples: United Kingdom, United States, and more. Info: Country names are shown as ISO country codes. |
| Event trigger page URL | Users are filtered based on where the event is launched. |
| User Id | Users are filtered based on the ID from which the Whatfix Event is triggered. Example: johndoe@whatfix.com. Info:
|
| Extension version | Users are filtered based on the browser Extension version they are using. |
| OS version | User is filtered based on OS versions. |
| Extension name | Users are filtered based on different browser Extension names. |
| Reserved variable 1 | Whenever Whatfix sends event data, two variables serve as reserved placeholders for additional properties. Reserved Variables are 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 event data, two variables serve as reserved placeholders for additional properties. Reserved Variables are 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 Attributes | Users are filtered based on the captured User Attributes, such as, role and department. For more information on how to use User Attributes as a filter, see Add User Attributes in Trend Insights and Add User Attributes in Funnel Insights. |
| Language | User is filtered based on the browser language. Example: French(fr), Spanish(es), and more. |
| Region | Users are filtered based on their geographical region. This data is taken from the browser. Examples: Camden, Kerala, Central Province, and more. |
| Model | Users are filtered based on the model of their device. Examples: Apple iPhone, Linux Desktop, and more. |
| OS | Users are filtered based on the base software(Operating System OS) that runs on the hardware. Examples: iOS, Linux, Windows, and more. |
| Cohort | Users are based on the Cohorts they belong to. For example, filter new users (grouped using specific conditions as a Cohort) who engage with a feature. |
| User type | Users are filtered based on whether Whatfix can 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?