Choose networks

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

Integration through pub.dev

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 instructions.
  3. In your project, follow the resulting integration statements:

Manual Integration

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 instructions.
  3. In your project, follow the resulting integration statements:

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 App Open Banner Interstitial Rewarded Rewarded Interstitial Native Bidding Automatic data collection support
Open source and versioned - third party SDKs 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 Bidding only
Mintegral 1 Country-specific
myTarget Country-specific
Pangle 1 Country-specific
Unity Ads 1 Country-specific
Non-open source - third 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 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

Flutter 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 Flutter adapter also gets a corresponding version bump. All other releases get a patch version bump.

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.

Previous
Get started