AppLovin MAX integration enables in-app bidding mediator for optimal ad network setup in mobile app monetization. With Server-Side Verification (SSV), rewarded ad eCPM is maximized. Our MAX SDK Android and iOS implementations compare waterfall vs bidding in ad mediation, achieving 95%+ fill rate and up to 30% higher eCPM. Typical savings from MAX integration: $500–$1,000 per month in increased eCPM.
Imagine your fill rate drops to 72% and eCPM fluctuates from $2 to $8 — your monetization budget is unstable. This is typical for waterfall: networks are tried sequentially, and bids don't participate in an auction. We integrate AppLovin MAX, a mediator with in-app bidding. MAX holds an auction among all networks simultaneously, picks the highest bid, and the ad is shown immediately. Fill rate rises to 95%+, eCPM stabilizes. For example, after switching from waterfall to MAX, our client increased ad revenue by 25% in a month. With MAX, you earn $8 to $15 per rewarded impression — waterfall often delivers under $6.
Stack: iOS (Swift 5.9+, SwiftUI), Android (Kotlin, Jetpack Compose), Flutter (Dart 3.x). MAX SDK is unified across platforms. Mediation management is done via Dashboard. We support Google AdMob, Meta Audience Network, Unity Ads, IronSource, Vungle, and others. Each network requires a separate adapter. We add adapters as runtime dependencies in build.gradle. Adapter versions are synchronized with MAX SDK.
Why MAX Outperforms Waterfall
| Parameter | Waterfall | MAX (in-app bidding) |
|---|---|---|
| Fill rate | 70–85% | 95%+ |
| eCPM | 15–30% lower | optimal (auction) |
| Latency | 500–1500 ms | 100–300 ms — 5x faster |
| Setup | manual network prioritization | automatic via RTB |
SDK Initialization
// Android — AppLovin SDK AppLovinSdk.initializeSdk(this) { sdkConfig -> // SDK initialized, can load ads initializeAds() } // Optional — pass User ID for server-side verification rewarded AppLovinSdk.getInstance(context).settings.userIdentifier = currentUser.id The sdk_key is set in AndroidManifest.xml as meta-data. On iOS — in Info.plist.
Example MAX Dashboard Configuration
In Dashboard, create an Ad Unit with type rewarded/interstitial/banner. For each Ad Unit, select a mediation group with networks. You can set up waterfall or bidding. In MAX, waterfall is legacy; bidding is recommended.
Connected Networks in MAX
MAX supports over 20 ad networks: Google AdMob, Meta Audience Network, Unity Ads, IronSource, Vungle, Mintegral, Pangle, and others. Each network is connected via a separate adapter:
// build.gradle — example adapter dependencies implementation 'com.applovin.mediation:google-adapter:23.x.x' implementation 'com.applovin.mediation:facebook-adapter:6.x.x' implementation 'com.applovin.mediation:unityads-adapter:4.x.x' Each adapter must be initialized per the network's requirements (App ID, Placement ID). Adapter versions must be compatible with MAX SDK version — updates must be coordinated. We check compatibility and update adapters with every release.
Rewarded Interstitial — The Highest eCPM Format
val rewardedAd = MaxRewardedAd.getInstance("YOUR_AD_UNIT_ID", activity) rewardedAd.setListener(object : MaxRewardedAdListener { override fun onAdLoaded(ad: MaxAd) { isReady = true } override fun onAdLoadFailed(adUnitId: String, error: MaxError) { // MAX automatically retries — no manual retry needed } override fun onUserRewarded(ad: MaxAd, reward: MaxReward) { grantReward(reward.amount, reward.label) } override fun onAdHidden(ad: MaxAd) { rewardedAd.loadAd() // Preload next ad } }) rewardedAd.loadAd() MAX automatically manages retry logic on load failures — no need to implement custom exponential backoff.
How to Set Up Server-Side Verification?
MAX supports SSV (Server-Side Verification) for rewarded ads: after viewing, MAX sends a POST to your specified server with encrypted parameters (user_id, reward, timestamp, HMAC signature). The server verifies the signature and grants the reward. This protects against client-side fraud: users cannot claim rewards without actually watching an ad. We configure the SSV endpoint and ensure correct processing.
A/B Testing and Analytics
The AppLovin Dashboard shows eCPM per network in mediation, win rate of the bidding auction, DAU×eCPM. Built-in A/B testing allows comparing mediation configurations without deployment. We use it to optimize: for example, we shift traffic share to a new network and observe eCPM. More details at the MAX SDK documentation.
What's Included in MAX Integration
- SDK initialization — integrate MAX SDK with correct
sdk_key, configure settings (User ID, consent, GDPR). - Connect 3–5 ad networks — install adapters, configure Placement IDs, test.
- Set up Server-Side Verification — server endpoint, signature verification.
- Integrate all formats — rewarded, interstitial, banner, native. Optimize show timings.
- A/B testing — compare mediation configurations.
- Documentation and training — checklist for store submission, update recommendations.
- Support — monitor fill rate and eCPM, resolve issues promptly.
Our Process
- Analysis — collect current monetization metrics, define target fill rate and eCPM.
- Integration — connect MAX SDK, configure network adapters, implement SSV.
- Testing — test on real devices via TestFlight and Firebase App Distribution, verify test Ad Unit IDs.
- Deployment — publish update to App Store and Google Play.
- Monitoring — track performance, adjust configuration as needed.
Timelines: from 2 to 5 days depending on number of networks and SSV complexity. Contact us for a project assessment — we'll prepare an integration plan and estimate costs.
Our team has over 5 years of experience in mobile app monetization and 50+ projects with ad SDKs. We guarantee a stable 95%+ fill rate and compliance with App Store Review Guidelines (Section 4.2, 5.1). Reach out to discuss details.