AdMob Mediation is a feature that lets you serve ads to your apps from multiple sources, including the AdMob Network, third-party ad networks, and AdMob campaigns. AdMob Mediation helps maximize your fill rate and increase your monetization by sending ad requests to multiple networks to ensure you find the best available network to serve ads.
This guide is your one stop shop for integrating mediation into your AdMob app.
Before you can integrate mediation for an ad format, you need to integrate that ad format into your app:
Choosing your Mediation networks
Google mediation supports over 30 third-party ad networks. Integrating mediation requires changes in these places:
- Third-party ad network UI - Sign up for the third-party ad network and create a placement in their frontend.
- AdMob UI - Update your ad unit's mediation settings to include the ad network. It is also recommended that you set up ad network optimization for ad networks that support it.
- App code - Update your app to include the third-party ad network's SDK, and an adapter library that communicates between Google and the third-party ad network to request and serve ads.
To begin, select an ad network from the below, and it will guide you through these changes.
|Ad Network||Banner||Interstitial||Rewarded Video||Native Advanced||ANO support|
|Open source and versioned|
|HUNT Mobile Ads||None|
|ONE by AOL||Global|
|TapIt by Phunware||Global|
Open source and versioned adapters
If an adapter is labeled with "Open source and versioned" in the above table, it means the adapter source code is open-sourced in Google's GitHub repository, enabling you to debug issues yourself should you choose to do so.
It also means that there are versioned adapter builds in Google's bintray
against a specific version of the third-party ad network SDK. You can also
compile these adapters into your app with a single line change to your app's
build.gradle file. Click on a specific ad network's guide for more details.
The adapter versioning scheme for versioned adapters is
SDK version>.<adapter patch version>. For example, if an
ad network releases a new SDK version
1.2.3, a new adapter version
will be released to Bintray after being tested against that new SDK.
If an adapter needs updating outside the lifecycle of a third-party SDK release,
the patch version will increase. A bug fix for adapter version
be released in version
When you configure multiple ad networks in AdMob Mediation, you have to tell AdMob in what order to request these networks by setting their respective CPM. This can be difficult to manage, since ad network performance changes over time.
Ad network optimization (ANO) is a feature within AdMob Mediation that enables you to generate the highest CPM from the ad networks in your mediation chain. Ad network optimization automates the process of ordering your mediation chain and helps you maximize revenue with minimum effort.
The mediation networks table above has the following values for ANO support:
|ANO support||What it means|
||eCPM values are automatically updated on your behalf on a per-country basis. This is the optimal type of ANO support.|
||A single global eCPM value is automatically updated on your behalf|
||You must manually configure an eCPM value for that ad network|
Click on a specific ad network's guide for details on how to configure ANO for that network.
If you're looking for an ad network and don't see it on the list above, you can use custom events to write your own integration with that ad network. See Custom Events for more details on how to create a custom event.