Choose networks

Mediation in Ad Manager 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 Automatic data collection support
Open source and versioned - 3rd party SDKs required
AppLovin Country-specific
Chartboost Country-specific
DT Exchange (previously Fyber Marketplace) Country-specific
i-mobile Japan only
InMobi 1 Country-specific
ironSource Ads Country-specific
Liftoff Monetize (previously Vungle) 1 Country-specific
maio Japan only
Meta Audience Network (previously Facebook) Bidding only
Mintegral 1 Country-specific
myTarget Country-specific
Pangle 1 Country-specific
Unity Ads Country-specific
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 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 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 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 will be released in version

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 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.