Your users are not uniform, and you shouldn’t treat them as such. By targeting and localizing your experiments for different segments of users, you can truly optimize your app for all users instead of just the majority.

Sample Size

Sample Size allows you to control the amount of users that will be included in the experiment. There are currently two options for sample size: Unlimited and Percentage. Selecting Unlimited will place no sampling restriction on your experiment. Selecting Percentage will mean that only the specified percentage of users will be included in the experiment.

Mobile A/B Testing Sample Size in the Splitforce Dashboard


Targeting allows you to control which users are included in your experiment based on conditions that you can set in the experiment builder interface. Some examples of targeting include: Device Type, Number of Prior Sessions or Date of First App Launch.

To define a group of end users that will be targeted for experimentation, simply select the property, operator and characteristic for which you want to filter. Here are a few examples:

Example #1

  • Property: Device Type
  • Operator: is
  • Characteristic: Tablet
Splitforce Mobile App Testing Dashboard - Segment by Device

Example #2

  • Property: Number of Prior Sessions
  • Operator: is greater than
  • Characteristic: 5
Segment App Users by Number of Prior Sessions with Splitforce

Example #3

  • Property: First Run?
  • Operator: true
Splitforce iOS, Android and Unity App Testing - Segment by First Run

One of Splitforce’s most powerful features is its wide-open flexibility in defining user segments; but this flexibility opens up the possibility of overlapping segments. When segments overlap, Splitforce takes the ‘union’ of the segments you provide to determine which variations the device you’re testing can use. In this case, the dashboard might include results from sub-segments. If you want to make sure you don’t end up with overlapping segments, all you have to do is make sure your conditions themselves don’t overlap.

For example: numberOfPriorSessions < 5 will overlap with firstRun = true. To prevent an overlap like this, you can simply set a combination of conditions, like this: numberOfPriorSessions < 5 && firstRun = false.


Localization allows you to set localized versions of each Element and for each Variation. The locale of an end user is defined by the ‘Language’ setting on their device.

To set a localized version of an Element, just click on the Localization option next to the Element Value you want to localize, identify the target languages and then enter the localized Element Value in the respective field.

Mobile App Testing Localization in the Splitforce Dashboard