Get advanced filtering control over your experiments
This article shows you how to use Taplytics' powerful user-segmentation controls and allows you to target an experiment to a very specific segment of your users.
What good is an A/B test if you can't reach the right segment of your users? Taplytics allows you to use all of the information about your user's device, from OS version and device type to app version. We even filter by more advanced information like the device's location, language, and session count.
To get the most out of user segmentation, you should send custom "App User" data about your users. Not only will this data help populate your Taplytics "User" page with useful information about your users, but you can also use it to deeply segment your users. Follow the instructions below to set up "User Attributes" for your app.
Choose any of the following segmentation filters for your experiment.
The app version filter lets you filter your users by the version of your app they are running. We highly recommend applying an app version filter to all your visual experiments because your visual elements can change from one app version to the next and Taplytics may have difficulty identifying the same element if it has changed position or appearance across app versions. Apply a filter for code experiments that are equal to or greater than the app version that you used to introduce the code block into your app.
These filters are powered by the custom data that your app passes into the Taplytics iOS or Android SDKs. We allow you to select any key value you pass in. Taplytics currently supports any string, number, or boolean value. The auto-fill dropdown helps you select data that you have sent to Taplytics.
This filter sets your experiment to distribute to iOS or Android devices. If you add a filter for both iOS and Android (as seen below), your experiment will be distributed to both device types.
This filter allows you to distribute an experiment to iOS devices running specific iOS Versions. You can also use the operator field to filter devices with greater than or less than a specified iOS Version.
The Android version filter allows you to distribute your experiment to Android devices running specific Android versions.
The iOS device types filter allows you to choose multiple iOS devices to distribute an experiment too. This filter is useful for making UI changes for specific device types like the iPhone 6+.
This filter segments users by number of sessions. A session is defined by the number of times an app has been opened while remaining in the background for less than 10 minutes. You can use this filter to test changes with your most active users.
This filter only distributes the experiment to users on their first app session. This filter is made for testing experiments with new users on their first launch of your app.
This filter distributes your experiment based on when each user signed up. For example, this allows you to distribute an experiment to users who signed up in the last week.
This filter distributes your experiment based on when each user last opened your app. For example, this filter lets you distribute your experiment to users who haven't opened your app in the last day.
This filter distributes your experiment to users within a defined age range. Make sure you are sending in the age parameter to the Taplytics User Attributes in the SDK as explained above, or else none of your users may get this experiment.
This filter distributes your experiment to users of the specified gender. Make sure that you are sending the gender attribute to the Taplytics User Attributes in the SDK (as explained above) or your users may not receive the experiment.
This filter distributes your experiment to users in the specified country. Taplytics uses IP location to determine the user's location. As a backup, we also use the country specified by the user's device.
This filter distributes your experiment to users who have set their device's preferred language to the specified language.
This filter distributes your experiment to users who view your app in the selected language. The app language may be different than the device language because your app may not support a user's preferred language and will default to another language, like English.