Mediate via AdMob on iOS

The Flurry AdMob and DFP mediation adapter lets you integrate ads from the Flurry network, via the Flurry Advertising SDKs, into the Google Mobile Ads mediation platform.

To start the mediation integration, ensure that you have access to the following:

Note that this section describes how to mediate Flurry through AdMob. For DFP mediation of Flurry inventory, follow these Integration instructions.

Get Started Mediating Flurry via AdMob

To integrate Flurry as the mediated Network in AdMob ad serving, you perform these tasks:

  1. Integrate Flurry SDK and Flurry adapter for DFP and AdMob code into your app.

  2. Configure Flurry’s Ad space(s).

  3. Configure AdMob to mediate Flurry.

  4. Request ads in your app.

Integrate Flurry SDK and Flurry Adapter Into Your App

Follow these steps:

  1. If your app is not currently tracked by Flurry, create a new application on Flurry’s developer portal.

  2. Keep a reference to the API Key for the new application after it has been created. Flurry requires each application to have its own unique API key to identify your app in the Flurry system. The Flurry API key is also used when configuring mediation on the AdMob dashboard.

  3. Add the latest Flurry iOS SDK into your app.

  4. To integrate the Flurry adapter into your application code, add the adapter as a dependency in your project (available here).

Configure Flurry’s Ad Unit(s)

Follow these steps:

  1. For each AdMob ad unit that you want to mediate Flurry through, create a matching ad unit on the Flurry developer portal.

  2. Log into the developer portal and navigate to the Monetization tab. On the left navigation bar select, Applications & Ad Units.

  3. You may see a list of previously created ad units. To set up a new one, click the Ad Unit button in the upper-left corner. Depending on the type of Ad Unit you are creating, the Ad Unit setup screen has three to four modules. The Basic Setup section includes fields required to define the name, application, dimensions, placement and orientation of the ad unit.

  4. You only need the basic setup to start. Click Save.

For additional ad unit configuration, see Basic ad space setup instructions and Advanced ad space setup instructions.

You are required to create your ad space on the developer portal before retrieving ads through mediation.

Mediating Flurry through AdMob requires no additional Flurry-related code in your application. The Flurry Ad Unit invocation code is already incorporated in the adapter adapter code.

If you are integrating banner ads, Flurry recommends that you turn off banner refresh in Flurry and let AdMob refresh the ads. Set the refresh rate for the ad unit 0 (instead of the default 30 seconds). This setting is found in the Advanced Options section of the Ad Unit setup.

Configure AdMob to Mediate Flurry

Follow these steps:

  1. On the AdMob site, configure Flurry mediation.

  2. For each ad unit that you would like to mediate Flurry through, select the Edit mediation link.

AdMob mediates Flurry

  1. Choose Flurry from the list of available ad networks. Once Flurry is selected, provide the API key and and ad space that you configured in the earlier step.

AdMob configure Flurry

  1. Capture the Ad unit ID.

Use this ID in your code to retrieve ads from AdMob, Flurry and any other networks configured in this step.

Request Ads in Your App

Follow the same instructions used for integrating AdMob ads into your application. To integrate non-interstitial ads (banner size, leaderboard size, and so on), follow the AdMob instructions for banner ads from Google. To integrate interstitial ads (full-screen ads that take over the screen), follow the AdMob instructions for interstitial ads from Google.

To integrate native ads, follow the instructions for AdMob from Google for native ads. The Google Ads SDK allows the mediation of two system-defined native ad formats: Content and App-install ad formats. Publishers mediating Flurry can request for both formats.

Note: Ad requests for only App-install ads will not work during Flurry mediation. We recommend that publishers request for both formats if mediating Flurry.


To learn about making AdMob ad requests, follow the instructions provided by Google.

For native ads, after completing a successful native ad request, you can get Flurry-specific assets in the following way:

#pragma mark GADNativeContentAdLoaderDelegate implementation

- (void)adLoader:(GADAdLoader *)adLoader
      didReceiveNativeContentAd:(GADNativeContentAd *)nativeContentAd {

    NSLog(@"Received native content ad: %@", nativeContentAd);

    GADNativeAdImage *flurryBrandingLog = nativeContentAd.extraAssets[kFlurryExtraBrandingLogo];
    // Load the rest of the native ad
    // ..

// ..

#pragma mark GADNativeAppInstallAdLoaderDelegate implementation

- (void)adLoader:(GADAdLoader *)adLoader
      didReceiveNativeAppInstallAd:(GADNativeAppInstallAd *)nativeAppInstallAd {

    NSLog(@"Received native app install ad: %@", nativeAppInstallAd);

    GADNativeAdImage *flurryBrandingLog = nativeContentAd.extraAssets[kFlurryExtraBrandingLogo];
    NSString *appCategory = nativeContentAd.extraAssets[kFlurryExtraAppCategory];
    // Load the rest of the native ad
    // ..