- 24 Feb 2025
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
What are Static Cohorts (User lists)?
- Updated On 24 Feb 2025
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Introduction
Are you facing the following issues while analyzing data?
The need to manually exclude testing or internal users from data analysis.
The need to manually add each user to run A/B tests.
The lack of an easy way to exclude or group users to target content.
With Static Cohorts (User lists), Whatfix enables the upload of a CSV file containing a list of User IDs to create a Cohort for that specific group. This Cohort can be used to target Whatfix content to that group of users or include or exclude them from data analysis.
Your title goes here
The User IDs added to the CSV file must match the User IDs configured by Whatfix to identify the user uniquely on the application. For example, if you’re using email IDs to uniquely identify users, the same email IDs must be included in the CSV file.
Whatfix enables you to reuse the same User list across multiple Cohorts.
Currently, Whatfix enables you to use User lists only in Cohorts for various use cases.
Use cases
Create Whatfix content for targeted user groups
Consider that you want to target Whatfix content, such as a Pop-up only to a specific team in your organization. Previously, you would have to set up a User Attribute or an integration to identify the team members. With Static Cohorts (User lists), Whatfix enables you to upload a CSV file containing the User IDs of the team members to your Whatfix Analytics dashboard. Create a Cohort based on the User list and use this Cohort as a Visibility rule to display the Pop-up to the required team.
To perform A/B testing on Whatfix content or widgets, upload User lists for both groups and create two separate Cohorts. Use these Cohorts to target the required Whatfix content or widget to the specific groups.
Your title goes here
Using Cohorts as a Visibility Rule is a Beta feature. Contact support@whatfix.com to enable it. For more information, see Add Cohorts as Visibility Rules.
Filter test users from data analysis
Consider that you want to exclude test users from the application engagement analysis done using Trend Insights. Previously, you would have to manually add all the User IDs that you want to exclude in the User filter section. However, with Static Cohorts (User lists), upload a CSV file containing the list of test users and create a Cohort. While creating a Trend Insight for analysis, exclude the Static Cohort (User list) from the User filter section. For more information, see Add Cohorts in Trend Insights.
Compare end-user engagement
Consider that you’ve rolled out an Onboarding Task List for the Marketing team and you’d like to analyze how many team members have completed the Task List and how many team members have yet to complete the Task List. Upload a User list of the Marketing team.
To analyze the users who’ve completed the Task List, create a Cohort with the following conditions:
Users belonging to the Marketing team (uploaded as a User list) and Users who completed the Onboarding Task List
To analyze the users who’ve not completed the Task List, create a Cohort with the following conditions:
Users belonging to the Marketing team (uploaded as a User list) and Users who have not completed the Onboarding Task List