Choose networks

This section includes a picker to select your preferred open-source and versioned adapter, and view the integration statements.

OpenUPM-CLI

Important: If you are migrating from using a .unitypackage to using OpenUPM-CLI, you must manually uninstall the assets from the old location by deleting all files from the respective Assets/GoogleMobileAds/Mediation folder.

If you have OpenUPM-CLI installed, you can install the Google Mobile Ads Mediation Plugins for Unity to your project using the following instructions:

1. Click the checkbox of your preferred open-sourced and versioned adapter.
2. Click Show OpenUPM-CLI instructions.
3. Run the resulting commands from your project's root directory.

OpenUPM

Important: If you are migrating from using a .unitypackage to using OpenUPM, you must manually uninstall the assets from the old location by deleting all files from the respective Assets/GoogleMobileAds/Mediation folder.

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 OpenUPM instructions.
3. In your project, install the resulting packages.

Unity Package

Download the zip files for the mediation adapters you're interested in:

AppLovin
Chartboost
DT Exchange
i-mobile
InMobi
IronSource Ads
Liftoff Monetize
LINE Ads Network
maio
Meta
Mintegral
myTarget
Pangle
Unity Ads

To integrate the mediation adapters you are interested in, follow the instructions in each respective ad source's integration guide in the following section.

For integration instructions, visit the individual partner pages, under the Integrate partner networks header in the left navigation bar.

Network details

Mediation in Ad Manager supports several ad sources, which accommodate integrations for both bidding and waterfall methods. Click an ad source for integration instructions specific to that ad source.

Ad source	Banner	Interstitial	Rewarded	Rewarded Interstitial	Bidding	Ad source optimization support
Open source and versioned — third-party SDK required
AppLovin						Country-specific
Chartboost						Country-specific
DT Exchange						Country-specific
i-mobile						Japan only
InMobi					^1	Country-specific
ironSource Ads					^1	Country-specific
Liftoff Monetize					^1	Country-specific
LINE Ads Network						Country-specific
maio						Japan only
Meta Audience Network						Country-specific
Mintegral						Country-specific
myTarget						Country-specific
Pangle						Country-specific
Unity Ads					^1	Country-specific
Non-open source — third-party SDK required
AdFalcon						Country-specific
Flurry						Country-specific
Leadbolt						Country-specific
LG U+AD						None
Tencent GDT						None
Vpon						None
Zucks						Country-specific

¹ Bidding integration is in beta.

Note: Ad sources are ordered alphabetically.

Open source and versioned adapters

If an adapter is labeled with "Open source and versioned" in the previous table, it means the adapter source code is open-sourced in Google's GitHub repository (Android or iOS), enabling you to debug issues yourself should you choose to do so.

Each adapter is built against a specific version of the third-party ad network SDK. Follow the specific partner's integration guide for more details.

Adapter versioning

Unity adapters follow a <major>.<minor>.<patch> versioning scheme that models the underlying Android and iOS SDK dependencies for that ad network. If either the Android or iOS dependency gets a major or minor version bump, the Unity adapter also gets a corresponding version bump. All other releases get a patch version bump.

Important: Make sure to disable refresh in all third-party ad networks UI for banner ad units used in mediation . This prevents a double refresh since Ad Manager also triggers a refresh based on your banner ad unit's refresh rate.

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 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 previous mediation networks table 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.

Note: Only ad networks that are Open source and versioned have specific instructions for setting up automatic data collection on that network.