고품질 사용자 환경을 유지하면서 광고 게재빈도를 최적화하는 것은 까다로운 작업일 수 있지만, Firebase에서는 최적의 광고 게재빈도를 테스트하고 이에 대해 데이터에 기반한 의사결정을 내릴 수 있게 해주는 도구들이 제공됩니다.
Firebase를 사용하면 소규모 사용자 하위 집합을 대상으로 여러 가지 광고 게재빈도의 성능에 대해 A/B 테스트를 수행할 수 있습니다.
테스트 결과를 관찰하고 성능이 더 뛰어나고 유지율에 대한 영향이 최소화된 광고 게재빈도에 대한 Firebase의 권장사항을 검토할 수 있습니다.
변화에 따른 긍정적인 영향을 확신할 수 있으면 버튼 하나만 클릭하여 더 많은 사용자들에게 변경사항을 적용할 수 있습니다.
학습할 내용
이 다단계 튜토리얼에서는 Firebase를 사용하여 앱에서 Google AdMob 광고에 대한 여러 최대 게재빈도를 테스트하는 방법을 알아봅니다. 여기에서는 예제 테스트 사례로 전면 광고가 사용되지만, 이를 기반으로 해서 동일한 단계를 사용하여 다른 광고 형식에 대해서도 최대 게재빈도를 테스트할 수 있습니다.
이 튜토리얼에서는 앱에서 이미 AdMob을 사용 중이고 전면 광고 단위의 게재빈도를 변경하여 앱 수익 또는 기타 측정항목에 미치는 영향을 테스트한다고 가정합니다. 하지만 앱에서 아직 AdMob을 사용하지 않더라도 문제가 없습니다. 또한 이 튜토리얼의 단계를 통해 앱에 사용할 광고 게재빈도를 이해할 수 있습니다.
Google AdMob을 사용하면 앱 내에서 제공되는 여러 가지 광고 게재빈도 또는 새로고침 빈도를 사용하여 광고 단위를 만들 수 있습니다. AdMob을 Firebase에 연결하면 AdMob이 광고 전략 최적화를 향상시키기 위해 광고 수익 정보를 Firebase로 전송합니다.
Google Analytics
Google Analytics는 사용자 참여 및 유지율과 총수익, AdMob 수익, 구매 수익 등의 수익 창출 측정항목에 대한 유용한 정보를 제공합니다. 또한 사용자 잠재고객 및 세그먼트를 만들 수 있게 해줍니다.
Firebase Remote Config
Firebase Remote Config를 사용하면 새 앱 버전을 게시하지 않고도 원하는 사용자 세그먼트에 맞게 앱의 동작과 모양을 동적으로 변경하고 맞춤설정할 수 있습니다. 이 튜토리얼에서는 Remote Config 파라미터를 사용하여 사용자에게 표시되는 광고 단위를 제어합니다.
Firebase A/B Testing
Firebase A/B Testing은 앱에서 제품 및 마케팅 실험을 실행할 수 있는 인터페이스와 인프라를 제공합니다. 사용자에게 실험 변형을 배포한 다음 통계 분석을 실행하여 수익 또는 사용자 유지와 같은 선택한 주요 측정항목을 기반으로 실험 변형이 통제 그룹보다 우수한지 확인합니다.
[null,null,["최종 업데이트: 2025-08-23(UTC)"],[],[],null,["# Tutorial: Optimize AdMob ad frequency using Firebase\n\n### **Solution tutorial**\n\nOptimizing ad frequency while keeping a high-quality user experience can be\ntricky, but Firebase offers tools that help you test and then make data-driven\ndecisions about optimal ad frequency.\n\n- Using Firebase, you can A/B test the performance of various ad frequencies\n with a *small subset* of users.\n\n- You can observe the test results and review recommendations from Firebase\n about which ad frequency is performing better with minimal impact on\n retention.\n\n- Once you're confident that the changes will likely have a positive impact,\n you can roll out the changes to more of your users with a click of a button.\n\nWhat you'll learn\n-----------------\n\nIn this multistep tutorial, you'll learn **how to use Firebase to test various\nfrequency caps for Google AdMob ads in your app** . It uses\n[interstitial ads](https://support.google.com/admob/answer/7311435)\nas the example test case, but you can extrapolate and use these same steps to\ntest frequency capping for\n[other ad formats](https://support.google.com/admob/answer/6128738).\n\nThis tutorial assumes that you already use AdMob in your app and that you'd\nlike to test whether changing the *frequency* of an interstitial ad unit will\nhave an impact on your app's revenue or other metrics. However, if you don't already\nuse AdMob in your app, that's ok! The steps in this tutorial can also help\nyou understand what ad frequency you should use in your app.\n| **Tip:** If there's a term that you're not familiar with, check out the [glossary](#glossary) at the bottom of this page.\n\nLearn more about the business case and value for this solution in our\n[*Optimize AdMob ad frequency* solution overview](/docs/tutorials/optimize-ad-frequency/solution-overview).\n\nProducts and features used in this tutorial\n-------------------------------------------\n\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Google AdMob \u003e [Google AdMob](/docs/admob) enables you to create ad units with various ad frequencies or refresh rates that will be served within your app. When you link AdMob with Firebase, AdMob sends ad revenue information to Firebase to improve ad strategy optimization. Google Analytics \u003e [Google Analytics](/docs/analytics) gives you insight into user engagement, retention, and monetization metrics like total revenue, AdMob revenue, purchase revenue, and much more. It also allows you to create user audiences and segments. | Firebase Remote Config \u003e [Firebase Remote Config](/docs/remote-config) enables you to dynamically change and customize the behavior and appearance of your app for desired user segments --- *all without publishing a new version of your \u003e app* . In this tutorial, you'll use Remote Config parameters to control which ad unit is shown to your users. Firebase A/B Testing \u003e [Firebase A/B Testing](/docs/ab-testing) provides the interface and infrastructure to run product and marketing experiments in your app. It takes care of distributing experiment variants to users, and then performs statistical analysis to determine if an experiment variant is outperforming the control group based on your selected key metric, such as revenue or user retention. |\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nTutorial overview\n-----------------\n\n[Go\ndirectly to the step-by-step tutorial](/docs/tutorials/optimize-ad-frequency/step-1)\n\n1. [**Use AdMob to\n create new ad unit variants for testing**](/docs/tutorials/optimize-ad-frequency/step-1)\n\n 1. Create two new interstitial ad units in AdMob.\n\n 2. Set the *Frequency capping* of each ad unit to an impressions per user\n value that you want to test.\n\n 3. Implement the ad unit placements within your app's code.\n\n2. [**Set up an A/B test\n in the Firebase console**](/docs/tutorials/optimize-ad-frequency/step-2)\n\n 1. Define testing basics, targeting, and the goals that the test will run\n against.\n\n 2. Define test variants and set up the Remote Config parameter that\n will control which ad unit is shown to users in the test.\n\n3. [**Handle\n Remote Config parameter values in your app's code**](/docs/tutorials/optimize-ad-frequency/step-3)\n\n 1. Use the Remote Config parameter in your app.\n\n 2. Implement the logic for displaying the ad unit based on the parameter's\n value.\n\n4. [**Start the A/B test\n and review the test results in the Firebase console**](/docs/tutorials/optimize-ad-frequency/step-4)\n\n 1. After starting the test and allowing it to run for a few days or weeks,\n check the Firebase console for whether the A/B test has a winning\n variant based on the primary goal of the A/B test.\n\n 2. Review the impact on secondary metrics for each variant to ensure the\n variants didn't cause unintended negative impacts to those metrics.\n\n5. [**Decide whether to\n roll out the new ad unit with the updated ad frequency**](/docs/tutorials/optimize-ad-frequency/step-5)\n\n 1. If A/B Testing determines that the variant showing the new ad format\n is the winner, you can start showing the ad format to all users targeted\n in the experiment, all users of your app, or to a subset of your users.\n\n 2. If a clear winner isn't yet determined, you can either continue running\n the experiment to gather more data, or end the experiment if it's\n already been running for a long period with inconclusive results.\n\nWhat you'll need\n----------------\n\n- Your own app (iOS, Android, or Unity project)\n\n- Your app registered as a Firebase App that's linked to an AdMob App\n ([learn more](//support.google.com/admob/answer/6383165))\n\n- Access to your app's associated AdMob account, with permissions to create\n new ad units\n\n- Access to your app's associated Firebase project, with permissions to create\n and manage Remote Config and A/B Testing as well as to view\n Google Analytics\n\n- Your preferred IDE\n\nGlossary\n--------\n\n\u003cbr /\u003e\n\nView a list of common terms for this solution\n\n\u003cbr /\u003e\n\n- **AdMob revenue** : AdMob network and open bidding revenue\n\n- **IAP revenue**: In app purchases revenue\n\n- **Total revenue**: Total revenue\n\n- **Retention**: Retention as a key metric in A/B tests is tracked as 1 day,\n 2-3 days, 4-7 days, 8-14 days, or 15+ days user retention\n\n- **Remote Config parameter**: The configurable parameter used to control\n which ad unit is show to users. In this guide, it will be an ad unit ID.\n\n- **Baseline configuration** : The as-is configuration in any particular A/B test\n --- also known as the control. The control usually uses the default value for\n the Remote Config parameter, but it can be configured to use a new control\n value if needed.\n\n- **Variant configurations** : The variant configurations are the alternative\n configurations with different Remote Config parameter values that we would\n like to test against the baseline configuration.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n*** ** * ** ***\n\n\u003cbr /\u003e\n\n[**Step 1** : Use AdMob to create new ad unit variantsarrow_forward_ios](/docs/tutorials/optimize-ad-frequency/step-1)\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n*** ** * ** ***"]]
