Ad Manager mediation supports several ad sources, with a mix of bidding and waterfall mediation integrations. Select an ad source below for integration instructions specific to that ad source.
| Ad Source | Banner | Interstitial | Rewarded | Native | Bidding | Automatic data collection support |
|---|---|---|---|---|---|---|
| Open source and versioned - 3rd party SDKs required | ||||||
| AdColony | Country-specific | |||||
| AppLovin | Country-specific | |||||
| Chartboost | Country-specific | |||||
| DT Exchange (previously Fyber Marketplace) | Country-specific | |||||
| i-mobile | Japan only | |||||
| InMobi | Country-specific | |||||
| ironSource | Country-specific | |||||
| Liftoff Monetize (previously Vungle) | Country-specific | |||||
| maio | Japan only | |||||
| Meta Audience Network (previously Facebook) | Bidding only | |||||
| myTarget | Country-specific | |||||
| nend | Japan only | |||||
| Pangle | 1 | Bidding only | ||||
| Tapjoy | Country-specific | |||||
| Unity Ads | Country-specific | |||||
| Yahoo | None | |||||
| Non-open source - 3rd party SDKs required | ||||||
| AdFalcon | Country-specific | |||||
| Flurry | Country-specific | |||||
| Leadbolt | Country-specific | |||||
| LG U+AD | None | |||||
| Tencent GDT | None | |||||
| Vpon | None | |||||
| Zucks | Country-specific | |||||
1 Bidding integration is in beta.
Open source and versioned adapters
If an adapter is labeled "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.
You can also find adapter
builds that can be
integrated into your app with just a single line change to your app's
build.gradle file.
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.
Automatic data collection
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.
Automatic data collection is a feature that enables 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 above uses the following values for automatic data collection support:
| Automatic data collection support | What it means |
|---|---|
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 on a specific ad network's guide for details on how to configure automatic data collection for that network.
Custom events
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 the custom events guide for more details on how to create a custom event.