Filter Insights data using User filters and User breakdown
- 26 Mar 2024
- 4 Minutes To Read
-
Print
-
DarkLight
-
PDF
Filter Insights data using User filters and User breakdown
- Updated On 26 Mar 2024
- 4 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
User filter
Using the User filter module, you can limit the scope of the events based on different criteria. It helps you drill down and get granular insights by filtering data based on user attributes such as browser, city, country, and OS.
Your title goes here
User filters are available in both Trend and Funnel Insights.
For example,
Trend Insights: For the Flow start event, you can refine the results to show data only for those who fired the Flow from the Chrome browser or from a specific location.
Funnel Insights: For a particular Funnel event (Flow, User Action, or Page View), you can refine the results to show data only for those who engaged with the Funnel steps from the Chrome browser or from a specific location.
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, the 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?
User breakdown
Using the User breakdown module, you can modify the chart to group users based on various properties. For example, for Flow completed event with User Filter set as the Chrome browser, configuring the breakdown as City, displays the chart based on all the locations from where the Flow was completed by users using the Chrome browser.
Your title goes here
User breakdown is available only 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, tablet, etc. |
| Browser | Users are filtered based on their browser type to access their websites. Example: Chrome, Firefox, Edge, etc. |
| City | User is filtered based on the city. This data is taken from the browser. Example: Dallas, Beijing, Bengaluru, etc. |
| Country | User is filtered based on the country. This data is taken from the browser. Example: United Kingdom, United States, etc. 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 |
| 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, there are two variables that 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, there are two variables that 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. |
| Event Attribute | This filter contains the captured Event Attributes, that is, contextual information in the application. For example, text on the button, title of the page where the action was performed, etc. For more information on how to use an Event Attribute as a filter, see Add Event Attributes to Trend Insights. Your title goes here You cannot add Event Attributes as a User filter in Funnel Insights and User Journey. |
| User Attribute | User is 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 | 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?