Mediation

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

This guide is your one-stop shop for integrating mediation into your AdMob app. It covers both Open Bidding (Beta) integrations and waterfall integrations.

Prerequisites

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

  • Banner
  • Interstitial
  • Rewarded
  • Native

• New to mediation? Read Overview of AdMob mediation.

• For Open Bidding: Google Mobile Ads SDK 7.53.1 or higher.

Initialize the Mobile Ads SDK

The quick start guide shows you how to initialize the Mobile Ads SDK. During that initialization call, mediation and open bidding adapters also get initialized. It is important to wait for initialization to complete before you load ads in order to ensure full participation from every ad network on the first ad request.

The sample code below shows how you can check each adapter's initialization status prior to making an ad request.

Swift

import GoogleMobileAds

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

  func application(_ application: UIApplication,
      didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {

    let ads = GADMobileAds.sharedInstance()
    ads.start { status in
      // Optional: Log each adapter's initialization latency.
      let adapterStatuses = status.adapterStatusesByClassName
      for adapter in adapterStatuses {
        let adapterStatus = adapter.value
        NSLog("Adapter Name: %@, Description: %@, Latency: %f", adapter.key,
        adapterStatus.description, adapterStatus.latency)
      }

      // Start loading ads here...
    }

    return true
  }

}

Objective-C

@import GoogleMobileAds;

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

  GADMobileAds *ads = [GADMobileAds sharedInstance];
  [ads startWithCompletionHandler:^(GADInitializationStatus *status) {
    // Optional: Log each adapter's initialization latency.
    NSDictionary *adapterStatuses = [status adapterStatusesByClassName];
    for (NSString *adapter in adapterStatuses) {
      GADAdapterStatus *adapterStatus = adapterStatuses[adapter];
      NSLog(@"Adapter Name: %@, Description: %@, Latency: %f", adapter,
            adapterStatus.description, adapterStatus.latency);
    }

    // Start loading ads here...
  }];
  return YES;
}

@end

Choosing your mediation networks

AdMob mediation supports several ad sources, with a mix of waterfall and Open Bidding integrations. Select an ad source below for integration instructions specific to that ad source.

Ad Source	Banner	Interstitial	Rewarded	Native	Open Bidding (Beta)	ANO support
No third-party SDKs required
Ad Generation						Bidding only
Chocolate Platform						Bidding only
Fluct						Bidding only
Improve Digital						Bidding only
Index Exchange						Bidding only
Media.net						Bidding only
MobFox						Bidding only
OpenX						Bidding only
PubMatic						Bidding only
Rubicon						Bidding only
Sharethrough						Bidding only
Smaato						Bidding only
Sonobi						Bidding only
TripleLift						Bidding only
UnrulyX						Bidding only
Yieldmo						Bidding only
YieldOne						Bidding only
Open source and versioned - 3rd party SDKs required
AdColony						Country-specific
AppLovin						Country-specific
Chartboost						Country-specific
Facebook						Country-specific
Fyber Marketplace						Country-specific
i-mobile						Country-specific
InMobi						Country-specific
ironSource						Country-specific
maio						Global
MoPub						Country-specific
myTarget						Country-specific
nend						Global
Tapjoy						Country-specific
Unity Ads						Country-specific
Verizon Media						Country-specific
Vungle						Country-specific
Non-open source - 3rd party SDKs required
AdFalcon						Country-specific
Flurry						Country-specific
Leadbolt						Country-specific
LG U+AD						None
Tencent GDT						None
Vpon						None
Zucks						Country-specific

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 repository, built against a specific version of the third-party ad network SDK. You can also integrate these adapters into your app with a single line change to your app's Podfile. Click on a specific ad network's guide for more details.

Adapter versioning

The adapter versioning scheme for versioned adapters is <third-party SDK version>.<adapter patch 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 patch version will increase. A bug fix for adapter version 1.2.3.0 will be released in version 1.2.3.1.

ANO 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.

Ad network optimization (ANO) 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 uses the following values for ANO support:

ANO support	What it means
Bidding only	The ad network only participates in Open Bidding. ANO support 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.
Global	A single global eCPM value is automatically updated on your behalf.
None	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 ANO for that network.

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

Custom events

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.

Note: Custom events do not have ANO support.

Check the value of adNetworkClassName

Each ad format class has an adNetworkClassName property on the GADResponseInfo object that returns the class name of the ad network that fetched the current ad. This property only has a value once an ad successfully loads.

Here is some sample code that logs the ad network class name for each ad format.

Banner

Swift

func adViewDidReceiveAd(_ bannerView: GADBannerView) {
  print("Banner adapter class name: \(bannerView.responseInfo.adNetworkClassName)")
}

Objective-C

- (void)adViewDidReceiveAd:(GADBannerView *)bannerView {
  NSLog(@"Banner adapter class name: %@", bannerView.responseInfo.adNetworkClassName);
}

Interstitial

Swift

func interstitialDidReceiveAd(_ interstitial: GADInterstitial) {
  print("Interstitial adapter class name: \(interstitial.responseInfo.adNetworkClassName)")
}

Objective-C

- (void)interstitialDidReceiveAd:(GADInterstitial *)interstitial {
  NSLog(@"Interstitial adapter class name: %@", interstitial.responseInfo.adNetworkClassName);
}

Rewarded Video

Swift

func rewardBasedVideoAdDidReceive(_ rewardBasedVideoAd: GADRewardBasedVideoAd) {
  print("Rewarded video adapter class name: \(rewardBasedVideoAd.adNetworkClassName)")
}

Objective-C

- (void)rewardBasedVideoAdDidReceiveAd:(GADRewardBasedVideoAd *)rewardBasedVideoAd {
  NSLog(@"Rewarded video adapter class name: %@", rewardBasedVideoAd.adNetworkClassName);
}

Native

Swift

func adLoader(_ adLoader: GADAdLoader,
              didReceive nativeAd: GADUnifiedNativeAd) {
  print("Native adapter class name: \(nativeAd.responseInfo.adNetworkClassName)")
}

Objective-C

- (void)adLoader:(GADAdLoader *)adLoader
    didReceiveUnifiedNativeAd:(GADUnifiedNativeAd *)nativeAd {
  NSLog(@"Native adapter class name: %@", nativeAd.responseInfo.adNetworkClassName);
}

Refer to Retrieving Information about the Ad Response for details.

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.

Rewarded ads mediation

We recommend that you override all default reward values by setting reward values in the AdMob UI. To do this, select the Apply to all networks in Mediation groups box so that the reward is consistent across all networks. Some ad networks don't provide a reward value or type at all. By overriding the reward value, the reward is consistent no matter which ad network served the ad.

For more information on setting reward values in the AdMob UI, refer to create a rewarded ad unit.

Native ads mediation

The following are some best practices to consider when implementing native mediation.

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.

Avoid using the GADMultipleAdsAdLoaderOptions class when making requests

Requests for multiple native ads only serve Google ads. The multiple native ads feature does not support mediation.

Open Bidding troubleshooting

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

• The Open Bidding 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.

Key Point: The first ad request may contain the a3p parameter even if you did not configure Open Bidding.

Follow this checklist to make sure your setup is correct:

• In the AdMob UI, your AdMob ad unit targets a mediation group that has an Open Bidding entry configured for that third-party ad network.
• In the AdMob UI, your AdMob ad unit belongs to the same AdMob app ID that you passed to the Google Mobile Ads SDK.
• In your app code, you initialized the mobile ads SDK and verified the adapter status is READY prior to loading an ad.
• In your app code, you've included the latest version of the adapter and SDK binaries for the ad source you're trying to integrate with.