Mobile Ad SDK Integration and Optimization

Integration is the part of mobile monetization that fails quietly. This guide walks through the steps in order, from first SDK call to the KPIs that tell you whether the setup works.

Data checked: November 2026

Before you start

Most integration problems begin before any code is written. Settle four things first. Decide which formats the app can carry without hurting the experience. Make sure your store listing points to a developer website you control, because that site will host app-ads.txt. Decide how the app collects consent and how it handles child-directed settings. And pick the one network you will launch with, so the first release changes one thing at a time.

Integration steps

The order below holds for any network. Details differ, so keep the network’s own getting-started guide open while you work.

  1. Create the account. AppLovin notes that its account may require approval, so start before your release date.
  2. Register the app and create ad units. One ad unit per placement keeps reports readable.
  3. Add the SDK and initialize it at launch, following the network’s documentation for your engine and platform.
  4. Load and show ads with test settings. See testing before release for what Google documents for AdMob.
  5. Wire consent and child-directed flags. Do this before the first real request, not after. The FTC’s COPPA FAQ is the starting point for apps that children may use.
  6. Release to a small share of users and watch crash rate and session length next to earnings.

Testing before release

Test ads exist so that developers never click live ads, which Google warns can get an account flagged for invalid activity. Google’s AdMob guide describes two routes: demo ad unit IDs, which are not tied to your account, and test devices registered against your own ad unit IDs. It tells developers to replace the demo IDs with their own before publishing, and to remove test-device code before release. Mediated ads do not show the Test Ad label, and test ads must be enabled for each mediation network separately, so do not click mediated ads during development when you are unsure whether the adapter supports test mode.

Other networks have their own test modes, so read the equivalent page before the first build. Source: Google AdMob test ads guide, updated November 16, 2026 · checked November 2026

Mediation and bidding setup

Mediation adds a layer between your app and the networks. In AppLovin MAX, supported networks bid in real time, while traditional networks sit in a waterfall ordered by price and can use auto-CPM, which updates their prices from network-reported CPMs. Each network you mediate needs its own account, its own app registration and its own approval, so budget time for that paperwork.

Keep SDK and adapter versions aligned with each network’s notes, since an outdated adapter is a common reason ads stop loading silently. When you add a network, add it alone, wait for stable data, and only then add the next. Source: AppLovin MAX getting-started guide · checked November 2026

app-ads.txt

app-ads.txt is a text file the developer publishes on the developer website to declare which sellers may sell the app’s ad inventory. The IAB Tech Lab describes it as an extension of ads.txt for mobile and over-the-top video apps, and says buyers use it to purchase through approved seller accounts. The specification explains how to find the developer’s website from the app’s store listing, which is why the store listing must point to a site you control.

Check that the file loads at the root of the domain linked on your store listing and that every network you use appears in it. A missing line is a common reason a network earns less than expected. Each network publishes its own line to add, so copy it from the network’s documentation rather than from a forum post. Read the IAB Tech Lab app-ads.txt page.

KPIs: fill rate, eCPM and ARPDAU

Three numbers describe an ad setup well.

  • Fill rate = ads shown ÷ ad requests. Low fill points to missing demand or a technical problem.
  • eCPM = ad revenue ÷ impressions × 1,000. It makes networks and formats comparable.
  • ARPDAU = ad revenue ÷ daily active users. It ties ads to how many people actually use the app.

Enter your own numbers below. The calculator runs in your browser and sends nothing anywhere.

Press Calculate.

The sample values are placeholders, not benchmarks. Replace them with a real day from your dashboard.

Troubleshooting low fill rate

When fill rate drops, check the cheap explanations first. Confirm that the app uses real ad unit IDs and that no test mode was left on. Check that app-ads.txt loads and lists every network. Look at consent and child-directed flags, since a restrictive setting can reduce the demand a network is allowed to send. Compare SDK and adapter versions against each network’s notes. Then look at geography: a country with little advertiser demand will fill poorly on any network. Change one thing at a time and give each change a full day of data before judging it.

A/B testing placements and frequency caps

Change one variable at a time. Test a placement against no placement, a new position against the old one, and a frequency cap against a looser cap. Split users randomly, run the test for full weeks so weekday effects cancel out, and judge it by three results: ad revenue per user, session length and day-one or day-seven return.

Frequency caps deserve special attention. Caps limit how often one user sees a full-screen ad within a period. A cap that looks wasteful on a revenue chart often pays back through retention. Unity LevelPlay lists A/B testing among its tools, so check whether your mediation platform already includes it before building your own.

When to add a second network

Add one when fill rate stays low in important countries, when a single network’s eCPM swings widely without explanation, or when you want a price check on your current network. Do not add one only because a list said so. Each extra network adds an SDK, a policy to read and a payout to track.