Notification

You can now request help from the Help page in your Play Console account.  If you don't have access to Play Console, ask your account admin for an invite.

Run A/B tests on your store listing

To give developers more control and statistical robustness we've recently made some changes to store listing experiments in Play Console. We've made improvements in a few key areas:

  • underlying data;
  • a calculator to estimate time to completion; and
  • improved the flows to guide you to the most optimal testing setup.

This page has been updated to reflect these changes.

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

For published apps, you can test variants against your current version to see which one performs best based on install/open 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, and screenshots.

  • 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, 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.

Create an experiment

To create an experiment in Play Console:

  1. Open Play Console and go to the Store listings page (Grow users > Store presence > Store listings).
  2. In the "Experiment" column for a store listing, click Set up.

Alternatively, click the arrow at the right end of the row to open the Details page for that store listing, then click Set up experiment if it’s available. If it’s not available, follow the prompt at the top of the Details page to fully roll out your store listing and get it ready for experiments, then return to this step to set up your experiment.

  1. Enter the experiment details:
  • Experiment name: Enter the name of your experiment (50 characters or fewer). Note: This name is just for your convenience. Users won't see it.
  • Experiment type: Choose Graphics experiment on default listing or Experiment on a localized listing. For localized listings, select the languages you want to test.
  • Target metric: The metric used to determine your experiment’s result. Choose Unique user install clicks, Unique user open clicks or Unique user pre-registration clicks.

The experiment creation page estimates the time and number of acquisition, opens or pre-registrations your experiment will need to show a statistically significant result.

  1. (Optional) Review the advanced settings. The default experiment settings will give you results in the shortest time with reasonable accuracy, and changing them can make your experiment run for longer before providing useful results, but if necessary you can adjust the following:
  • Number of variants: The number of experimental variants to test against the current store listing (you can choose up to 2 variants).
  • Experiment audience percentage: The percentage of store listing visitors that will see an experimental variant instead of the current listing. These visitors will be split equally across your experimental variants.
  • Minimum detectable effect: The minimum difference between variants and control required to declare which performs better. If the difference is less than this, your experiment will be considered a draw.
  • Confidence level: How often the confidence interval provided by the experiment will contain the true performance of the store listing. Increasing the confidence level decreases the likelihood of a false positive.
  1. Click Next.
  2. Select the type of asset you want to test. We recommend testing changes to one asset at a time, so you can be as certain as possible of what causes any changes to your store listing performance.
  3. Provide the test variants of the asset.
  4. Review your asset variants, then click Save. You now have the option to return to the Details page, or go to the publishing overview page to submit your changes for review.

Review and apply results

To review and apply your results:

  1. Open Play Console and go to the Store listings page (Grow users > Store presence > Store listings).
  2. You can view the status of your experiments in a few ways.
  • The Experiments tab shows all your experiments, and you can navigate to your specific experiment from there.
  • In the Listings tab, click the cell in the "Experiment" column for your chosen store listing to view the experiments associated with this listing.
  • In the Listings tab, click the right arrow in the row for your chosen store listing to view details, including information about all experiments you’ve run on that listing.
  1. In the "Results" section, view a summary of your experiment's results based on your target metric.

    The results tell you which of the options is performing best, or performing better than your current Store Listing. You'll also see an explanation of this result, based on its confidence interval and minimum detectable effect, and a recommended action (if applicable). You may receive the result "More data needed" if not enough data has been collected to return a result.
  2. Your next action depends on your experiment results:
  • If a variant performed well, you may see a recommendation to apply that variant.
  • If your result is "More data needed," come back later.We will advise if you have less than a week before we expect a result to be ready.
  • If more than one variant performed better than your current listing, or if your result was a "Draw," review the results to decide which variant you want to apply.
    • If your current store listing performed the best, click Keep current listing.

User metrics

Metric Definition
Unique user install clicks The number of users who installed your app, who didn't have it installed on any other devices at the time.
Unique user open clicks The number of installed users who opened your app.
Unique user pre-registration clicks The number of users who have pre-registered for your app.

Experiment autocompletion

Store listing experiments stop automatically after running for 6 months. After this time, no new data will be collected, no variants will be applied, and traffic will revert to the current listing. You can still access your completed experiment in Play Console and see the data it collected.

Sign up for experiment notifications

To receive notifications and email when your experiments are complete, make sure that you set your preferences on the Notifications page in Play Console.

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

Was this helpful?

How can we improve it?
false
Search
Clear search
Close search
Main menu
4092762670339364628
true
Search Help Center
false
true
true
true
true
true
92637
false
false
false
false
false