Integrating MoPub with Mediation

This guide is for publishers who want to use the Google Mobile Ads SDK to load and display ads from MoPub via mediation. It covers how to add MoPub to an ad unit's mediation configuration, how to set up Automatic data collection, and how to integrate the MoPub SDK and adapter into an iOS app.

Supported ad formats and features

The Ad Manager mediation adapter for MoPub has the following capabilities:

Rewarded Video
Rewarded Video (new APIs)
Native Ad - Custom Rendering
Smart banners
Automatic data collection
Native Video


  • Xcode 9.0 or higher
  • iOS Deployment target of 8.0 or higher
  • Google Mobile Ads SDK 7.42.2 or higher

Step 1: Set up MoPub

First, sign up and log in to your MoPub UI. Navigate to the Apps page and click the Add a New App button.

MoPub new app

Select iOS as the Platform for your app, enter the App name and iTunes URL of your app. Then select a primary and secondary category of your app from the provided list.

MoPub app

MoPub requires you to create your first ad unit before you can finish adding your app.

For additional instructions on creating an ad unit, select the tab corresponding to your preferred ad format.


Choose Tablet as the Device type. Choose a banner format that matches the ad size you're requesting in your app. Enter a Name for your ad unit.

The refresh rate is handled by the Google Mobile Ads SDK according to your refresh rate setting in the Ad Manager UI. So, we recommend using a high value for the Refresh Interval here (e.g. 1000 seconds).



Choose Tablet as the Device type. Choose Tablet Full Screen as the Format. Enter a Name for your ad unit. Choose the type of Layout to present the ad in.



Choose Tablet as the Device type. Choose Native (Custom layout) as the Format. Enter a Name for your ad unit.


Click Save and View Code Integration to get your Ad Unit ID.

MoPub ad unit id

In addition to the Ad Unit ID, you'll also need to obtain your MoPub API Key and Inventory Report ID to set up your Ad Manager ad unit ID. To find your API Key and Inventory Report ID, navigate to the Reports page and click View API Access Details.

MoPub reporting keys

MoPub Marketplace

To get ads from MoPub, your account must be approved for MoPub Marketplace. During your initial account setup, you will be prompted to go through the process for Marketplace approval. Part of this process includes entering your payment information.

MoPub marketplace

See the Marketplace setup guide for more details.

Step 2: Configure mediation settings for your Ad Manager ad unit

Sign in to your Ad Manager account. Navigate to Delivery > Yield groups and click the New yield group button.

Enter a unique Name for your yield group, set the Status to Active, select your Ad Format, and set the Inventory type to Mobile App. Under the Targeting > Inventory section, select the Ad Unit ID to which you want to add mediation.

Next, click the Add yield partner button.

If you already have a Yield partner for MoPub, you can simply select it. Otherwise, select Create a new yield partner.

Select MoPub as the Ad network and enter a unique Name. Enable Mediation and turn on Automatic data collection, and enter the API Key and Inventory Report ID obtained in the previous section. You don't need to enter a Username and Password. Click Save when finished.

Once the Yield partner is selected, choose Mobile SDK mediation as the Integration type, iOS as the Platform, and Active as the Status. Enter the Ad Unit ID obtained in the previous section and a Default CPM value.

Click Save at the bottom of the page when done.

Using rewarded video ads

In the settings for your rewarded video ad unit, provide values for the reward amount and reward type. Then, to ensure you provide the same reward to the user no matter which ad network is served, check the Override reward settings from third-party ad networks when using mediation box.

Override reward

If you don't apply this setting, the MoPub adapter passes back the reward specified in the MoPub dashboard.

Step 3: Import the MoPub SDK and adapter

  • Add the following line to your project's Podfile:

    pod 'GoogleMobileAdsMediationMoPub'
  • From the command line run:

    pod install --repo-update

Manual integration

  • Download the latest version of the MoPub SDK and link the MoPubSDK source code in your project.
  • Download the latest version of the MoPub adapter and link MoPubAdapter.framework in your project.

Step 4: Additional code required

Initialize the MoPub SDK

Before loading ads, have your app initialize the MoPub SDK by calling initializeSdkWithConfiguration: with a valid MoPub Ad Unit ID you created in Step 1. This needs to be done only once, ideally at app launch.

#import "MoPub.h";

@implementation AppDelegate

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

  MPMoPubConfiguration *sdkConfig =
  [[MPMoPubConfiguration alloc] initWithAdUnitIdForAppInitialization:@"YOUR_MOPUB_AD_UNIT_ID"];

  [[MoPub sharedInstance] initializeSdkWithConfiguration:sdkConfig completion:nil];
  return YES;


Step 5: Test your implementation

To get test ads from MoPub, you need a guaranteed or backfill line item. MoPub recommends adding the Demo line item to your ad unit to get test ads. The Demo line item is added to your MoPub account by default.

MoPub demo item

The Demo Line Item contains test creatives for native and banner ad units by default, but does not have a test creative for interstitial ad units. To add your own test creative for interstitial ads, you need to upload a simple image to the MoPub UI by navigating to the Demo Line Item and clicking the Add a New Creative button. Choose Tablet Full Screen format. Fill the form with the necessary details and click Save to add your test creative to the Demo Line Item.

MoPub demo item

That's it! You now have a working mediation integration with MoPub.

Optional steps

Under the Google EU User Consent Policy, you must ensure that certain disclosures are given to, and consents obtained from, users in the European Economic Area (EEA) regarding the use of device identifiers and personal data. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information about each network's use. Google currently is unable to pass the user's consent choice to such networks automatically.

To collect consent for MoPub, MoPub asks that you use its consent mechanism. See the MoPub GDPR Publisher Integration Guide for more information.

Using native ads

Network-specific parameters

The MoPub adapter supports an additional request parameter which can be passed to the adapter using the GADMoPubNetworkExtras class. This class includes the following property:

  • privacyIconSize - Set the size for the MoPub privacy icon in points. Values can range from 10 to 30 inclusive. The default size for the privacy icon is 20.

Here's a code example of how to set this parameter at ad request time:


let adRequest = DFPRequest()
let extras = GADMoPubNetworkExtras()
extras.privacyIconSize = 15


DFPRequest *request = [DFPRequest request];
GADMoPubNetworkExtras *extras = [[GADMoPubNetworkExtras alloc] init];
extras.privacyIconSize = 15;
[adRequest registerAdNetworkExtras:extras];

Ad Rendering

The MoPub adapter returns its native ads as NativeAppInstallAd objects. It populates the following Native App install ad display fields for a GADNativeAppInstallAd:

Field Populated by MoPub adapter
App icon
Call to action
Star rating

Impression and Click Tracking

MoPub and Google Mobile Ads SDKs track impressions in their own way, so there may be discrepancies.

Clicks are detected by the Google Mobile Ads SDK and are forwarded to MoPub SDK, so click reporting will be in sync.

Additional Resources

For more details on how to set up test ad units, consult MoPub's Testing Ads.

Send feedback about...

Mobile Ads SDK for iOS
Mobile Ads SDK for iOS
Need help? Visit our support page.