This guide shows the ad sources AdMob Mediation supports, in addition to details, such as required open-source and versioned adapters, and supported ad source optimization.
If you want to integrate an ad source that AdMob Mediation doesn't support, see Custom events.
Integrate open-source and versioned adapters
This section includes a picker to select your preferred open-source and versioned adapter, and view the integration statements.
To integrate an open-sourced and versioned adapter into your app, do the following:
- Click the checkbox of your preferred open-sourced and versioned adapter.
- Click Show mediation setup.
- In your app, copy and paste the resulting integration statements.
For further integration instructions, see the page for each individual ad source in the following section.
Network details
AdMob Mediation supports several ad sources, with a mix of bidding and waterfall mediation integrations. Select an ad source for integration instructions specific to that ad source:| Ad Source | App Open | Banner | Interstitial | Rewarded | Rewarded Interstitial | Native | Bidding | Ad source optimization support |
|---|---|---|---|---|---|---|---|---|
| Open source and versioned - third party SDKs required | ||||||||
| AppLovin | Country-specific | |||||||
| Chartboost | Country-specific | |||||||
| DT Exchange (previously Fyber Marketplace) | Country-specific | |||||||
| i-mobile | Japan only | |||||||
| InMobi | Country-specific | |||||||
| ironSource Ads | 1 | Country-specific | ||||||
| Liftoff Monetize (previously Vungle) | Country-specific | |||||||
| LINE Ads Network | 1 | Country-specific | ||||||
| maio | Japan only | |||||||
| Meta Audience Network (previously Facebook) | Bidding only | |||||||
| Mintegral | Country-specific | |||||||
| myTarget | Country-specific | |||||||
| Pangle | Country-specific | |||||||
| Unity Ads | 1 | Country-specific | ||||||
| Non-open source - third party SDKs required | ||||||||
| AdFalcon | Country-specific | |||||||
| Flurry | Country-specific | |||||||
| Leadbolt | Country-specific | |||||||
| LG U+AD | None | |||||||
| Tencent GDT | None | |||||||
| Vpon | None | |||||||
| Zucks | Country-specific | |||||||
| No third-party SDKs required | ||||||||
| Ad Generation | Bidding only | |||||||
| Chocolate Platform | Bidding only | |||||||
| Equativ (formerly Smart Adserver) | Bidding only | |||||||
| Fluct | Bidding only | |||||||
| Improve Digital | Bidding only | |||||||
| Index Exchange | Bidding only | |||||||
| InMobi Exchange | Bidding only | |||||||
| Magnite DV+ | Bidding only | |||||||
| Media.net | Bidding only | |||||||
| MobFox | Bidding only | |||||||
| Nexxen (previously UnrulyX) | Bidding only | |||||||
| OneTag Exchange | Bidding only | |||||||
| OpenX | Bidding only | |||||||
| PubMatic | Bidding only | |||||||
| Sharethrough | Bidding only | |||||||
| Smaato | Bidding only | |||||||
| Sonobi | Bidding only | |||||||
| TripleLift | Bidding only | |||||||
| Verve Group | Bidding only | |||||||
| Yieldmo | Bidding only | |||||||
| YieldOne | Bidding only | |||||||
1 Bidding integration is in beta.
Open source and versioned adapters
If an adapter is labeled with "Open source and versioned" in the earlier 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 repository, built against a specific version of the third-party ad network SDK. You can also integrate these adapters into your app with a single line change to your app's Podfile.
Adapter versioning
The adapter versioning scheme for versioned adapters is <third-party
SDK version>.<adapter patch version>. For example, if an
ad network releases a new SDK version 1.2.3, a new adapter version 1.2.3.0
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 1.2.3.0 will
be released in version 1.2.3.1.
Ad source optimization
When you configure multiple ad networks for mediation, you have to specify 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 source optimization is a feature that lets you to generate the highest CPM from the ad networks in your mediation chain by automating the process of ordering the mediation chain to maximize revenue.The mediation networks table earlier uses the following values for ad source optimization support:
| Ad source optimization support | What it means |
|---|---|
Bidding only |
The ad network only participates in bidding. Ad source optimization is not applicable. |
Country-specific |
eCPM values are automatically updated on your behalf on a per-country basis. This is the optimal type of optimization. |
None |
You must manually configure an eCPM value for that ad network. |
Click a specific ad network's guide for details on how to configure ad source optimization for that network.
Custom events
If you're looking for an ad network and don't see it on the list earlier, you can use custom events to write your own integration with that ad network. See the custom events guide for more details on how to create a custom event.