Choose networks

This guide shows the ad sources 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 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:

  1. Click the checkbox of your preferred open-sourced and versioned adapter.
  2. Click Show mediation setup.
  3. 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

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 SourceApp OpenBannerInterstitialRewardedRewarded InterstitialNativeBiddingAutomatic data collection support
Open source and versioned - third party SDKs required
AppLovinCountry-specific
ChartboostCountry-specific
DT Exchange (previously Fyber Marketplace)Country-specific
i-mobileJapan only
InMobiCountry-specific
ironSource Ads 1Country-specific
Liftoff Monetize (previously Vungle) 1Country-specific
LINE Ads NetworkCountry-specific
maioJapan only
Meta Audience Network (previously Facebook)Bidding only
MintegralCountry-specific
myTargetCountry-specific
PangleCountry-specific
Unity Ads 1Country-specific
Non-open source - third party SDKs required
AdFalconCountry-specific
FlurryCountry-specific
LeadboltCountry-specific
LG U+ADNone
Tencent GDTNone
VponNone
ZucksCountry-specific

1 Bidding integration is in beta.

Open source and versioned adapters

If an adapter is labeled "Open source and versioned" in the earlier table, it means the adapter source code is open-sourced in Google's 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 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 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 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 automatic data collection support:

Automatic data collection supportWhat it means
Country-specificeCPM values are automatically updated on your behalf on a per-country basis. This is the optimal type of optimization.
NoneYou 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 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.

Previous
Get started