Skip to content

Mediation

AdMob Mediation is a feature lets you serve ads to your apps from multiple sources, including the AdMob Network and third-party ad sources, in one place. AdMob Mediation helps maximize your fill rate and increase your monetization by sending ad requests to multiple networks to verify you find the best available network to serve ads. Case study.

Prerequisites

Warning

Verify that you have the necessary account permissions to complete the mediation configuration. These permissions include access to inventory management, app access, and privacy and messaging features. See Manage user access to your account for details.

Before you can integrate mediation for an ad format, you need to integrate that ad format into your app:

New to mediation? Read Overview of AdMob Mediation.

Initialize Google Mobile Ads SDK

You can either rely on Automatic SDK initialization or implement it manually. During that initialization call, mediation adapters also get initialized. It is important to wait for initialization to complete before you load ads in order to verify full participation from every ad network on the first ad request.

Check which ad network adapter class loaded the ad

Here is an example that logs the ad network class name for an ad:

#include "GoogleAdMobResponseInfo.h"
// ...
void UYourClass::OnLoaded(const UGoogleAdMobResponseInfo& ResponseInfo)
{  
    UE_LOG(LogTemp, Display, TEXT("Adapter class name: %s"), *ResponseInfo.MediationAdapterClassName);
}

Refer to the Response info documentation on MediationAdapterClassName for details about this property.

US states privacy laws and GDPR

If you need to comply with the U.S. states privacy laws or General Data Protection Regulation (GDPR), follow the steps in US state regulations settings or GDPR settings to add your mediation partners in AdMob Privacy & messaging's US states or GDPR ad partners list. Failure to do so can lead to partners failing to serve ads on your app.

Learn more about enabling restricted data processing (RDP) and obtaining GDPR consent with the Google User Messaging Platform (UMP) SDK.

Choose networks

AdMob Mediation supports several ad sources, with a mix of bidding and waterfall mediation integrations. To add one of the networks, you need to choose an appropriate guide from Google from the table below and complete first 2 steps from it, and then enable this mediation network in Project Settings. Select an ad source for integration instructions specific to that ad source:

Ad Source App Open Banner Interstitial Rewarded Rewarded Interstitial Bidding Ad source optimization support Plugin Version
AppLovin (Android | iOS) Country-specific 1.0.0+
InMobi (Android | iOS) Country-specific 1.0.0+
ironSource (Android | iOS) Country-specific 1.0.0+
Liftoff Monetize (Android | iOS) Country-specific 1.0.0+
LINE Ads Network (Android | iOS) Country-specific 1.0.0+
Meta Audience Network (Android | iOS) Bidding only 1.0.0+
Mintegral (Android | iOS) Country-specific 1.0.0+
Moloco (Android | iOS) Country-specific 1.1.0+
Pangle (Android | iOS) Country-specific 1.0.0+
Unity Ads (Android | iOS) Country-specific 1.0.0+

Note

The project won't package for Android if both LINE Ads Network and Generate universal APK from bundle are set to True.

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 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 ad source optimization support:

Ad source optimization support What it means
Bidding only The ad network only participates in bidding. Ad source optimization is not applicable.
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 ad source optimization for that network.

Note

There is also a number of "No third-party SDKs required" ad networks that only require signing a partnership through the AdMob UI.

Troubleshoot AdMob bidding

When integrating a bidding partner that requires their SDK, the following symptoms indicate an improper integration:

  • The Ads Activity report shows significantly fewer ad requests to that partner than you expect.

  • The a3p parameter in any request after the first ad request is missing.

    Note

    The first ad request may contain the a3p parameter even if you did not configure bidding.

Follow this checklist to make sure your setup is correct:

  • In the AdMob UI:

    • Confirm that you have followed the specific partner's integration guide to configure third-party bidding demand.
    • Confirm that you have an ad unit mapping for each creative format.

  • In your project:

    • Ensure that the app ID in Project Settings is the same app ID that your ad unit mapping targets.
    • Make sure your ad unit IDs match those in the AdMob UI as they must match exactly.