Step 4: Start the A/B test and review the test results in the Firebase console
| Introduction: Optimize AdMob ad frequency using Firebase |
| Step 1: Use AdMob to create new ad unit variants for testing |
| Step 2: Set up an A/B test in the Firebase console |
| Step 3: Handle Remote Config parameter values in your app's code |
|
Step 4: Start the A/B test and review the test results in the Firebase console |
| Step 5: Decide whether to roll out the new ad format |
Now that you have everything set up, you're ready to start and run your A/B test. While the test is running, you can review results in the Firebase console.
Deploy your app and start the test
After you add the logic to handle the Remote Config parameter value (previous step), deploy the latest builds of your app that include them.
In the Firebase console, start the A/B test by clicking Start Experiment.
Review results
Firebase A/B Testing will run your experiment. After it's exposed users to the different variants, the Firebase console will display an improvement suggestion.
Review how each variant performed based on the metrics that you selected during test setup.
Firebase A/B Testing makes its judgement based on the primary metric that you selected, but A/B Testing also provides you with data for all the other secondary metrics that you selected. This allows you to take into account these secondary metrics when making a final judgement about the performance of a variant.
The image below shows an example of a test run with four variants, including the baseline (note that in this tutorial we kept it more simple with only three variants). In this example below, A/B Testing has determined that the winning variant is Variant A due to the improvements in the primary metric of Estimated total revenue.
Firebase console UI showing example A/B test results"
class="screenshot">
Step 3: Handle Remote Config parameter values Step 5: Decide whether to roll out the new ad format