Step 1. Input A/B Test Details

Test Name

Fill in the name the test. This will only be used by you to reference the test.

Test ID

Add the Unique ID of the test. This will only be used by you to help identify the test in the dashboard filters.

Set Start/End Date

Set the start date for the test.

Select End Date (Optional)

You can also set a end date for the test.

Step 2. Input A/B Test Filters

Select User Filters

Select user filters you'd like the A/B Test to target users by such as: User Geo, Device, Language, and Os Version.

Set New Users Percentage

Slide the meter to set the percentage of new users you want to be included in the test.

Step 3. Create A/B Test Groups

Add Varient Test Groups

Add user groups to your test equal to the number of configs you want to distribute in the experiment. Each time you add a new group, the user share percentage will adjust to evenly distribute new users to that group.

Input your config key value pairs into your different groups

Input the key value pairs into each group you've added. A/B tests will be distributed like a remote configs to users.

Remember your config key's. These keys will be used when retreiving the remote configs in the SDK.

Step 4. Select A/B Test Goals

Choose your Goal Metric

Select your test's goal metric you'd like to analyze during the experiment.

Add Extra Metrics

Using the dropdown, select any other metrics you'd like to track during the test. You can select as many metrics as you'd like.

Edit A/B Testing Details

The following attributes on an A/B Test's Details can be edited:

Change Name

You can change the name of the A/B Test.

Change Goal Metric

If you want to start analyzing a different the goal metric, you can update your selected Goal Metric.

Update Extra Metrics

You can add or remove metrics you want to track using the Extra Metrics dropdown.

Edit A/B Configs

The following attributes on an A/B Test's Configs can be edited:

A/B Test Configuration

You can add configs or change the config keys and values. However, you cannot remove configs.

Stage Rollout

Stage rollouts allow you to select a winning variant and roll it out against the control group individually. Other variants apart of the test will stop delivering to new users, however existing users in the group will still be apart of the group until the test is in Full Rollout.

Select Group to Stage Rollout

Select a group you want to elect to run parallel with Control Group. All new users will only be added to your staged group and the control group.

Note: If you only have 2 varient groups you will not be able to stage rollout.

Full Rollout

Full rollout allows you to select the variant that won and distribute it as a global remote config to all your players. This will end the A/B Test.

Select Group to Full Rollout

Select the group you want to full rollout to all your players. This group's configs will be turned into Remote Configs that will reach all users on your game and end the test.

Full Rollouts will end the test and put the test into an Archive state.

States of A/B Tests

On the platform there are different states an A/B Test can be in. The following are a list of possible A/B Test states.

1. Active

Active A/B Tests are running and distributing the test to new users.

2. Pause

Paused A/B Tests will stop distributing the test to new users, but will still deliver the group configs to current users already apart of the test.

If a test is paused, you can resume the test and make it active again.

3. Archive

Archived A/B Tests will stop distributing the test to all users and will not deliver group configs to current users that were apart of the test.

In an Archived state, you will still be able to see the user data from the test in the dashboard and filters.

Archived test cannot be resumed.

4. Delete

Deleted A/B Tests will be fully removed from the entire game and even removed from dashboard filters.

Deleting a test cannot be undone.