Use the mediation picker to quickly integrate any open-sourced and versioned adapter into your app.
- Click the desired checkboxes.
- Click Show mediation setup.
- Copy and paste the integration statements into your app.
See the individual partner pages for necessary further integration instructions.
AdMob 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||Rewarded Interstitial||Native||Bidding||Ad source optimization support|
|No third-party SDKs required|
|Ad Generation||Bidding only|
|Chocolate Platform||Bidding only|
|ENGINE Media Exchange (EMX)||Bidding only|
|Equativ (formerly Smart Adserver)||Bidding only|
|Improve Digital||Bidding only|
|Index Exchange||Bidding only|
|InMobi Exchange||Bidding only|
|OneTag Exchange||Bidding only|
|Verve Group||Bidding only|
|Open source and versioned - 3rd party SDKs required|
|DT Exchange (previously Fyber Marketplace)||Country-specific|
|Liftoff Monetize (previously Vungle)||Country-specific|
|Meta Audience Network (previously Facebook)||Bidding only|
|Non-open source - 3rd party SDKs required|
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.
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
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 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 ad source optimization support:
|Ad source optimization support||What it means|
||The ad network only participates in bidding. Ad source optimization is not applicable.|
||eCPM values are automatically updated on your behalf on a per-country basis. This is the optimal type of optimization.|
||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 ad source optimization 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 the custom events guide for more details on how to create a custom event.