This guide is intended for publishers that are interested in using Google Mobile Ads mediation. It walks you through getting a mediation adapter set up with your current Android app and setting up additional request parameters.
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.
- DFP UI - Modify your DFP yield group to add the ad network as a yield partner. We also recommended that you set up automatic data collection 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||Native||Automatic data
|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
Automatic data collection support
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 has the following values for Automatic data collection support:
|Automatic data collection support||What it means|
||eCPM values are automatically updated on your behalf on a per-country basis. This is the optimal type of optimization.|
||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 Automatic data collection for that network.
Deprecated ad networks
Remove deprecated ad networks from your mediation placements. See Delete an ad network from mediation for instructions.
|Deprecated ad networks|
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.
Initialize your ad object with an Activity instance
In the constructor for a new ad object (for example,
you must pass in an object of type
Context is passed on to other ad networks when using mediation. Some
ad networks require a more restrictive
Context that is of type
and may not be able to serve ads without an
Activity instance. Therefore,
we recommend passing in an
Activity instance when initializing ad objects
to ensure a consistent experience with your mediated ad networks.
Banner ads mediation
Make sure to disable refresh in all third-party ad networks UI for banner ad units used in AdMob mediation. This will prevent a double refresh since AdMob also triggers a refresh based on your banner ad unit's refresh rate.
Native ads mediation
The following are some best practices to consider when implementing native mediation.
Request both system-defined formats
The Mobile Ads SDK allows you to specify a preference for app install ads, content ads, or both for each request. However, not every mediated network offers both of these formats, and some are unable to filter by format. In order to make sure that ad requests have the best chance of being filled, it's highly recommended that apps request both formats when loading native ads and include rendering code that can display either one.
Native ad presentation policy
Each ad network has its own policies. When using mediation, it's important to remember that your app still needs to abide by the policies of the mediated network that provided the ad.
The Mobile Ads SDK automatically places the AdChoices logo for you. Mediation adapters are also responsible for placing the AdChoices logo if applicable, so you don't need to take any action to display an AdChoices asset in your app.