Setelah menyiapkan semuanya, Anda dapat memulai dan menjalankan pengujian A/B. Selama pengujian berjalan, Anda dapat meninjau hasilnya di Firebase console.
Men-deploy aplikasi dan memulai pengujian
Setelah menambahkan logika untuk menangani parameter value Remote Config (langkah sebelumnya), deploy build terbaru aplikasi Anda yang menyertakannya.
Di konsol Firebase, mulai pengujian A/B dengan mengklik
Start Experiment.
Meninjau hasil
Firebase A/B Testing akan menjalankan eksperimen Anda. Setelah pengguna melihat berbagai varian, konsol Firebase akan menampilkan saran peningkatan.
Tinjau performa setiap varian berdasarkan metrik yang Anda pilih selama penyiapan pengujian.
Firebase A/B Testing membuat penilaiannya berdasarkan metrik utama yang Anda pilih, tetapi A/B Testing juga memberi Anda data untuk semua metrik sekunder lainnya yang Anda pilih. Dengan data tersebut, Anda dapat memperhitungkan metrik sekunder ini saat membuat penilaian akhir tentang performa varian.
Gambar di bawah menunjukkan contoh pengujian yang dijalankan dengan empat varian, termasuk dasar pengukuran (perhatikan bahwa dalam tutorial ini, kami hanya menggunakan dua varian agar tetap sederhana). Dalam contoh di bawah ini, A/B Testing telah menentukan bahwa varian yang dominan adalah Variant A karena peningkatan pada metrik utama dari Estimated total revenue.
UI Firebase console yang menampilkan contoh hasil pengujian A/B"
class="screenshot">
[null,null,["Terakhir diperbarui pada 2025-07-24 UTC."],[],[],null,["# Tutorial: Test adoption of new AdMob ad formats\n\nStep 4: Start the A/B test and review the test results in the Firebase console\n------------------------------------------------------------------------------\n\n\u003cbr /\u003e\n\n|--------------------------------------------------------------------------------------------------------------------|\n| Introduction: [Test new AdMob ad format adoption using Firebase](/docs/tutorials/test-ad-format-adoption) |\n| Step 1: [Use AdMob to create a new ad unit variant for testing](/docs/tutorials/test-ad-format-adoption/step-1) |\n| Step 2: [Set up an A/B test in the Firebase console](/docs/tutorials/test-ad-format-adoption/step-2) |\n| Step 3: [Handle Remote Config parameter values in your app's code](/docs/tutorials/test-ad-format-adoption/step-3) |\n| **Step 4: Start the A/B test and review the test results in the Firebase console** \u003cbr /\u003e |\n| Step 5: [Decide whether to roll out the new ad format](/docs/tutorials/test-ad-format-adoption/step-5) |\n\n\u003cbr /\u003e\n\nNow that you have everything set up, you're ready to start and run your A/B\ntest. While the test is running, you can review results in the\nFirebase console.\n\n### **Deploy your app and start the test**\n\n1. After you add the logic to handle the Remote Config parameter value\n (previous step), deploy the latest builds of your app that include them.\n\n2. In the Firebase console, start the A/B test by clicking\n **Start Experiment**.\n\n### **Review results**\n\n1. Firebase A/B Testing will run your experiment. After it's exposed users\n to the different variants, the Firebase console will display an\n improvement suggestion.\n\n2. Review how each variant performed based on the metrics that you selected\n during test setup.\n\n Firebase A/B Testing makes its judgement based on the primary metric that\n you selected, but A/B Testing also provides you with data for all the\n other secondary metrics that you selected. This allows you to take into\n account these secondary metrics when making a final judgement about the\n performance of a variant.\n\nThe image below shows an example of a test run with four variants, including the\nbaseline (note that in this tutorial we kept it more simple with only two\nvariants). In this example below, A/B Testing has determined that the winning\nvariant is *Variant A* due to the improvements in the primary metric of\n*Estimated total revenue*.\nFirebase console UI showing example A/B test results\" class=\"screenshot\"\\\u003e\n\n\u003cbr /\u003e\n\n*** ** * ** ***\n\n\u003cbr /\u003e\n\n[arrow_back_ios**Step 3** : Handle Remote Config parameter values](/docs/tutorials/test-ad-format-adoption/step-3)\n[**Step 5** : Decide whether to roll out the new ad formatarrow_forward_ios](/docs/tutorials/test-ad-format-adoption/step-5)\n\n\u003cbr /\u003e\n\n*** ** * ** ***"]]