Filter Insights data using User filters and User breakdown in Mirror
- 19 Jul 2024
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Filter Insights data using User filters and User breakdown in Mirror
- Updated On 19 Jul 2024
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
User filter
Using the User filter module, limit the scope of the events based on different criteria. It helps you drill down and gain granular insights by filtering data based on user property or attributes.
Your title goes here
User filters are available in both Trends and Funnel Insights.
For example,
Trend Insights: For the Mirror, refine the results to show data only for those who launched the Mirror from the Chrome browser or from a specific location.
Funnel Insights: For a particular Funnel event (Flows, Custom events, or Page view), refine the results to show data only for those who engaged with the Funnel steps from the Chrome browser or a specific location.
User breakdown
Using the User breakdown module, modify the chart to display data based on the various properties.
Your title goes here
User breakdown is only available in Trend Insights.
For example, Trend Insights: If you select Browser as a User filter and Country as a User breakdown, the chart displays data of all users who launched the Mirror using the Chrome browser from any country.
.png?sv=2022-11-02&spr=https&st=2024-12-25T17%3A04%3A49Z&se=2024-12-25T17%3A14%3A49Z&sr=c&sp=r&sig=EXJcGD%2ByJrL7ye5RDci%2BvsCvaHTQ92H2e0DibHLkB74%3D)
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. For example, mobile phones and desktops. |
Browser | Users are filtered based on their browser type to access their websites. For example, Chrome or Firefox. |
City | Users are filtered based on the city. This data is taken from the browser. For example, Dallas and Beijing. |
Country | User is filtered based on the country. This data is taken from the browser. For example, the United Kingdom and the United States.
|
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. For example, johndoe@whatfix.com.
|
OS version | Users are filtered based on OS versions. |
Reserved variables | 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, 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. |
Language | Users are 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. |
User type | Users are filtered based on whether Whatfix is able to detect and identify their User ID when they login to the application. |
Was this article helpful?