Optimize your app's revenue with Firebase
summary
Uses AdMob + Google Analytics + Firebase Remote Config and A/B Testing to run real experiments that swap ad unit IDs at runtime, target 10% of users, and evaluate estimated AdMob revenue plus retention and purchase revenue. Concrete variants shown: 1 impression per 20 minutes versus 1 impression every 5 minutes, and reward sizes 1,000 vs 3,000 gems. Tests run without app redeploys, take weeks for significance, and Remote Config delivers per-user ad unit IDs while A/B Testing attributes results.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:41Figuring out our ad experiment strategy
- 3:18The solution framework to solve our ad questions
- 7:04Solving our first question - “What’s the impact of showing more ads to our users?”
- 7:23Creating ad variants in AdMob
- 10:00Creating an AdMob ad in code
- 11:10Parameterizing our AdMob ad unit ID with Remote Config
- 12:04Configuring our ad experiment and ad variants in A/B Testing
- 13:37Wiring up our app code with Remote Config
- 16:06Start running our tests
- 16:20Viewing test results
- 16:57Solving our second question - “What’s the optimal award amount for our rewarded ads?”
- 17:14Reusing our framework to run our second experiment
- 20:02What else can we solve with this framework?
related talks
29mLeverage Firebase to Optimize Your App’s Monetization Strategy
46mTweaking and AB Testing Your App on the Fly
13mCreate better user experiences with Remote Config for advanced app personalization
57mGrow your game profitably - Optimal Paid User Acquisition
46mGoogle Ads Checklist: everything you need before launching your game
40mSmart Strategies for Growing Your App Business with Ads
27mPower your monetization with AdMob
43mHave Your Cake and Eat It Too with A/B Testing