Integrating Fyber Marketplace with Mediation

This guide is intended for publishers who want to use the Google Mobile Ads SDK to load and display ads from Fyber Marketplace via mediation. It covers how to add Fyber Marketplace to an ad unit's mediation configuration and how to integrate the Fyber Marketplace SDK and adapter into an iOS app.

Supported ad formats and features

The AdMob mediation adapter for Fyber Marketplace has the following capabilities:

Rewarded Video
Native Advanced


  • Xcode 10 or higher
  • iOS Deployment target of 8.0 or higher
  • Latest Google Mobile Ads SDK

Step 1: Set up Fyber Marketplace

Sign up or log in to Fyber Marketplace's Revenue Desk.

Navigate to the Inventory tab, select Manage Apps / Sites and click on the Add App or Site button.

Manage Apps

Select iOS as the Platform, fill out the rest of the form, and click Continue.

When prompted to create an Ad Spot and Ad Unit ID, enter your desired Ad Spot Name, the Format of the ad you wish to create, your desired Ad Unit Name, and fill out the rest of the form. Click Save and Continue.

Ad Spot

Next, allocate 100% of the traffic of your Ad Unit to your Ad Spot and click Continue.

Set Traffic

You will be presented with an overview of your application, as well as your created Ad Spots. Take note of the App ID, Spot ID and Ad Unit ID.

Step 2: Configure mediation settings for your AdMob ad unit

You need to add Fyber Marketplace to the mediation configuration for your ad unit.

First, sign in to your AdMob account. Next, navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add Fyber Marketplace as an ad source.

To create a new mediation group, select Create Mediation Group.

AdMob mediation tab

Enter your ad format and platform, then click Continue.

Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled, and then click Add Ad Units.

Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.

You should now see the ad units card populated with the ad units you selected.

Add Fyber Marketplace as an ad source

In the Ad Sources card, select Add Ad Network.

Select Fyber Marketplace. Then, enter an eCPM value and click Continue.

Ad source

Enter the Application ID, Ad Spot ID, and the Ad Unit ID obtained from the previous step. Finally, click 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 Apply to all networks in Mediation groups box.


If you don't apply this setting, the Fyber Marketplace adapter passes back the reward specified in the Fyber Marketplace dashboard when creating the placement.

For more information on setting reward values for AdMob ad units, see Create an ad unit.

Step 3: Import the Fyber Marketplace SDK and adapter

Add the following line to your project's Podfile:

pod 'GoogleMobileAdsMediationFyber'

From the command line run:

pod install --repo-update

Manual integration

  • Download the latest version of the Fyber Marketplace SDK, and link IASDKCore.framework, IASDKMRAID.framework and IASDKVideo.framework in your project.
  • Download the latest version of the Fyber Marketplace adapter and link FyberAdapter.framework in your project.
  • Add the following frameworks to your project:
    • libxml2.2.tbd

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.

The section below shows you how to enable or disable personalized ads for Fyber Marketplace.

Fyber Marketplace contains an API to allow publishers to forward user consent to their SDK. The following sample code shows how to pass consent information to the Fyber Marketplace SDK manually. Should you choose to pass consent information to the Fyber Marketplace SDK manually, it is recommended that this code is called prior to requesting ads via the Google Mobile Ads SDK.

#import <IASDKCore/IASDKCore.h>
// ...

[IASDKCore.sharedInstance setGDPRConsent:YES];
[IASDKCore.sharedInstance setGDPRConsentString:@"myGdprConsentString"];

Visit Fyber Marketplace's GDPR implementation guide and GDPR and You article for more information.

Fyber iOS Mediation Adapter Changelog


  • Verified compatibility with Fyber Marketplace SDK version 7.5.1.
  • Fixed a crash that occurred when initializing the Fyber SDK.

Built and tested with:

  • Google Mobile Ads SDK version 7.55.0.
  • Fyber Marketplace SDK version 7.5.1.

Version (Deprecated)

  • This version has been removed. Please use version or higher.
  • Verified compatibility with Fyber Marketplace SDK version 7.5.0.
  • Adapter will now initialize the Fyber SDK before making an ad request if the Fyber SDK has not been initialized yet.

Built and tested with:

  • Google Mobile Ads SDK version 7.53.0.
  • Fyber Marketplace SDK version 7.5.0.


  • Initial release!
  • Added support for banner, interstitial and rewarded ad formats.

Built and tested with:

  • Google Mobile Ads SDK version 7.52.0.
  • Fyber Marketplace SDK version 7.4.0.