Filter Trend Insights in EI using User filters and User breakdown

Aktualisiert am 26 Aug 2025
3 Minuten zu lesen

Drucken
Teilen
Dunkel
Licht
pdf

The content is currently unavailable in German. You are viewing the default English version.

Artikel-Zusammenfassung

Fanden Sie diese Zusammenfassung hilfreich?

Vielen Dank für Ihr Feedback

User filter

User filters enable you to narrow down the data shown by applying conditions based on user properties, such as browser, operating system, city, or country.

insights_select_user_filter_for_blank_values

Use case:

Find the number of users who started Flows across applications from the Chrome browser or from a specific location.

ei_trends_insights_user_filter_sample

User breakdown

User breakdowns enable you to group and visualize the filtered data by a specific user property, such as city, browser, or OS. This changes the chart to show how different groups of users behave within the selected segment.

insights_select_user_breakdown_for_blank_values

Use case:

For example, selecting the Flow started event and filtering users by the Chrome browser, with a City breakdown, shows a chart of where users started Flows while using Chrome.

ei_trends_insights_user_breakdown_sample

The following table lists the User filters and User breakdown available in Trend Insights:

Filters	Description
Device
Device Type	Filters data based on the hardware users use. Examples: Mobile phones, desktops, tablets, 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. Examples: Chrome, Firefox, Edge, and more.
OS version	Filters data based on the OS versions.
Language	Filters data based on the browser language. Examples: French (fr), Spanish (es), and more.
Model	Filters data based on the model of the user's device. Examples: Apple iPhone, the Linux Desktop, and more.
OS	Filters data based on the base software (Operating System OS) that runs on the hardware. Examples: iOS, Linux, Windows, and more.
Location
City	Filters data based on the city. This data is taken from the browser. Examples: Dallas, Beijing, Bengaluru, and more.
Country	Filters data based on country. This data is taken from the browser. Examples: United Kingdom, United States, and more. Info: Country names are shown as ISO country codes.
Region	Filters data based on geographical region. This data is taken from the browser. Examples: Camden, Kerala, Central Province, and more.
URL/IP
Event trigger page URL	Filters data based on where the event was launched. Example: https://salesforce.com/leads. Note: The following conditions are available for the Event trigger page URL: Contains, Starts with, Ends with, Is equal to, and Not contains. For more information, see How do conditions in the Event Trigger Page URL work?
User
User Id	Filters data based on the ID from which the Whatfix event is triggered. Example: johndoe@whatfix.com. Note: The User Id filter is case-sensitive. Ensure you add the exact User ID value to get the data. Use a comma to search for multiple User IDs. To filter based on a User ID that contains a comma, for example Doe, John, enclose the User ID in quotes "Doe, John" while searching. Add a comma after the quotes when filtering for more than one User ID with a comma. To exclude a User ID that contains quotes, for example "John", do not place a comma between the quotes.
User Attributes	Filters data 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.
Variables
Reserved variable 1	Whatfix reserves two variables as placeholders for additional properties required when sending event data. Reserved Variables are those properties captured along with Guidance events and App 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 gets incremented 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 those properties captured along with Guidance events and App 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 gets incremented every time the user logs in. For more information, contact support@whatfix.com. Data is filtered based on these additional properties.
Uncategorized
Extension version	Filters data based on the Whatfix browser extension version in use.
Extension name	Filters data based on the different Whatfix browser extension names.

Info:

To exclude specific filter values for which you don't require data, see How can I exclude filter values in Enterprise Insights?
To exclude blank filter values from your data, see How can I exclude blank filter values in Enterprise Insights?

War dieser Artikel hilfreich?

What's Next

Ereignissen mit Event Filters und Breakdown in Trend Insights für EI filtern

Inhaltsverzeichnis

User filter
User breakdown