Run A/B tests on your store listing

To help optimize your store listing on Google Play, you can run experiments to find the most effective graphics and localized text for your app. You can run experiments for your main and custom store listing pages.

For published apps, you can test variants against your current version to see which one performs best based on install data. Before setting up a test, review the best practices for running effective experiments.

Note: Global experiments have been renamed to default graphics experiments. They maintain the same functionality that they had prior to being renamed.

Experiment types

For each app, you can run one default graphics experiment or up to five localized experiments at the same time.

Default graphics

Using a default graphics experiment, you can experiment with graphics in your app's default store listing language. You can include variants of your app's icon, feature graphic, screenshots, and promo video.

If your app's store listing is only available in one language: Default graphics experiments will be shown to all users.
If you've added any localized graphic assets in a specific language: Users viewing your app in that language are excluded from your app's default graphics experiments. For example, if your app's default language is English and it has a localized feature graphic in French, users viewing your app in French will be excluded from the experiment (even if you're testing your icon).

Localized (for text and graphics)

Using a localized experiment, you can experiment with your app's icon, feature graphic, screenshots, promo video, and/or your app's descriptions in up to five languages. Experiment variants will only be shown to users viewing your app's store listing in the languages you choose.

If your app's store listing is only available in one language, localized experiments will only be shown to users viewing your app in its default language.

Step 1: Create an experiment

You can create an experiment using your Play Console. When you're ready to review and apply results, you can use your Play Console or the Play Console app.

Default graphics

Sign in to your Play Console.
Select an app.
On the left menu, click Store presence > Store listing experiments.
Click New experiment.
Under "Default graphics," click Create.
Proceed to the instructions under "Step 2: Set up your experiment."

Localized

Sign in to your Play Console.
Select an app.
On the left menu, click Store presence > Store listing experiments.
Click New experiment.
Under "Localized," choose a language.
Click Create.
Proceed to the instructions under "Step 2: Set up your experiment."

Once you've made a localized experiment live in one language, you can add up to four other languages. To add more experiments:

Go to back to your Store listing experiments page.
Select New experiment.
- If you can't select New experiment, make sure you don't have an experiment saved in draft. Any draft experiments need to be live before you add new languages.

Step 2: Set up your experiment

After you've created an experiment, you can select the store listing, variants, and attributes that you want to test.

To set up your experiment:

Follow the on-screen instructions to select a store listing and add your targeting information, attributes, and variants.
- For more information and tips, review the table below.
To begin your experiment, go to the top of the page and click Run experiment. To finish setting up your experiment later, click Save.

See field descriptions, examples & tips

Field	Description	Examples & tips
Name	Your experiment name is only visible on the Play Console to identify the experiment and isn't visible to users.	"Bright icon experiment" "Logo feature graphic" "Short description with new slogan"
Store listing name	The store listing (main or custom) that you want to test.	After you start an experiment, your custom store listing's name is displayed with the name it had at the start of your experiment. If you update the name of your custom store listing after your experiment starts, it won't be changed in your experiment. To avoid confusion when running experiments, it's a good idea to delete unused custom store listings, and then create new ones when needed.
Audience	The percentage of users that see a variant of your experiment. Your audience percentage will be divided equally between your experiment variants.	If you type 30% as your audience, the remaining 70% of visitors to your store listing page will see your page's current version. If you have a 30% audience and two variants in your experiment, each variant will be shown to 15% of users. During the course of an experiment, each user will only see a single variant or your page's current version.
Attributes	Select the item type you want to test compared to your current listing.	To run experiments most effectively, test one attribute at a time. You can only test your short description and full description during a localized experiment. If you're testing graphic assets, make sure to follow size and file type requirements.
Variants	To add a new version to your experiment, click Add another variant.	You can add up to 3 variants per experiment, in addition to your current version.

Step 3: Review & apply results

After you’ve set up experiments, you'll see the following details on your Store listing experiments page. To get more details, select an experiment.

Live experiments

Experiment: Name of your experiment
Status: Number of variants being served to a percentage of users
Start date: When your experiment started
Results: Experiment results or data status

Completed experiments

Experiment: Name of your experiment
Type: Default graphics or localized
Start date: When your experiment started
End date: When your experiment ended
Results: Applied or not applied

Using the Play Console website

Sign in to your Play Console.
Select an app.
On the left menu, click Store presence > Store listing experiments.
Select the experiment you want to review.
Next to “Metric,” select a metric.
View your results.
- To apply a variant that outperformed your app's current version, select Apply winner. You can review the changes to your store listing before the changes go live.
- To keep your current version, select Keep. This will update your store listing to use your current version and end the experiment.
- If your experiment results in a tie, select Stop experiment.
- Note: Depending on the metric you select, the performance results of individual variants may differ. For best results, review all available metrics before deciding on which variant to use.

Using the Play Console app

Open the Play Console app .
Select an app.
Scroll down to the "Experiments" card. For more information on your app's experiments, tap View details. From the detailed view, tap on a variant to see the audience, current, and scaled installs for that experiment.
- To apply a variant that outperformed your app's current version, select Apply winner. You can review the changes to your store listing before the changes go live.
- To keep your current version, select Keep current. This will update your store listing to use your current version and end the experiment.
- Note: Performance results are based on first time installers. To view results based on additional metrics, visit the Play Console website.

See descriptions of statistics, metrics, & examples

After you select an experiment, you can view user and install metrics that summarize how each variant performed.

User metrics

Metric	Definition
First-time installers	Unique users who installed your app for the first time during the experiment. Data is scaled to account for audience share.
Retained installers (1-day) - only available on the Play Store website	Unique users who installed your app for the first time and kept it for at least 1 day following installation during the experiment. Data is scaled to account for audience share.

Results

You can view metrics that show the results of your experiment in two different ways:

Current: Number of unique users
Scaled: Number of unique users divided by audience share

If you want to review absolute data on installers, use current data. If you want to review data that’s been scaled to account for different audience shares (example: If 90% of your audience saw one version and 10% of your audience saw another), use scaled data.

Metric	Definition & examples
Installers	Number of unique users who installed your app for the first time.
Retained installers	Number of unique users who installed your app for the first time and kept it for at least 1 day following installation.
Performance	Estimated change in install performance compared to the current version. There is a 90% chance that the variant would perform within the displayed range over time. Since the range is based on a variant's performance, these numbers will vary during the experiment. The average between your variant's high and low approximate change in install performance represents your variant's estimated change in performance. Example: If one of your variants had a performance range of +5% to +15%, the most likely change in performance would be the middle number between the two, about +10%. Performance will only be displayed once your experiment has enough data. In general, as an experiment has more time to run and collect data, a variant's performance range will become more narrow and accurate.
Installs (scaled) - deprecated	Number of installs during the experiment divided by audience share. Included for experiments started prior to January 24, 2019. For example, if you ran an experiment with two variants that used 90% / 10% audience shares and the installs for each variant were A = 900 and B = 200, the scaled installs would be shown as A = 1000 (900/.9) and B = 2000 (200/0.1).
Installs (current) - deprecated	Number of installs that are still installed today. Included for experiments started prior to January 24, 2019.

Install metrics (deprecated)

The following metrics were used for experiments started prior to January 24, 2019. Experiments that started prior to this date still include these statistics, but new experiments only use first-time installers and retained installers (1-day) user metrics.

Metric	Definition & examples
Installs on active devices	Number of active devices on which each variant of the application is currently installed, scaled up to compensate for the different audience levels.
Installs by user	Number of unique users who installed each variant of the app in a given day, scaled up to compensate for different audience levels.
Uninstalls by user	Number of uninstalls of each variant of the app in a given day, scaled up to compensate for different audience levels.

Sign up for experiment notifications

To receive notifications on the Play Console and by email when your experiments are complete, you can set up your notification preferences.

To learn more about email notifications, go to manage your developer account information.

Was this helpful?

How can we improve it?