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 Android app.

Supported ad formats and features

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

Formats
Banners
Interstitials
Rewarded Video
Native Ads
Features
Smart banners
Ad Network Optimization (ANO)
Native Video

Requirements

• Android API level 16 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.

Select Android 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.

Key Point: Within a Fyber Marketplace ad spot, we strongly recommend creating only a single Fyber Marketplace ad unit. An AdMob ad unit ID should have a 1:1 relationship to a Fyber Marketplace ad spot. If you have multiple AdMob ad unit IDs that you want to integrate with Fyber Marketplace, we strongly recommend creating a unique ad spot corresponding to each AdMob ad unit ID.

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

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.

On Username > User Profile. Take note of the Publisher ID, Consumer Key and Consumer Secret as this will be needed in the next step.

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.

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 Waterfall card, select Add Ad Source.

Select Fyber Marketplace and it should take you to Add ad source: Fyber Marketplace

Enable the Optimize switch. Enter the Publisher Id, Consumer Key and Consumer Secret obtained in the previous section. Review and check the Authorization checkbox to set up Ad Network Optimization (ANO) for Fyber Marketplace. Then enter an eCPM value for Fyber Marketplace and click Continue.

Enter the Application ID, Ad Spot ID, Ad Unit ID obtained in the previous section. Then click Done.

Note: Ad network optimization takes a few days to gather data to accurately calculate eCPM for a mediation network. In the meantime, the ANO status will be PENDING, so you must manually set an eCPM value for the network. Once the eCPM can be calculated, ANO will automatically start updating the eCPM on your behalf. If the AdMob Dashboard is showing a PENDING or ERROR status for more than 72 hours, verify that you have added the System User to each of your Properties.

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

Android Studio integration (recommended)

Add the following implementation dependency with the latest version of the Fyber SDK and adapter in the app-level build.gradle file:

repositories {
    jcenter()

    maven {
      url "https://fyber.bintray.com/marketplace"
    }
}

...
dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'com.google.android.gms:play-services-ads:19.5.0'
    implementation 'com.google.ads.mediation:fyber:7.7.0.0'
}
...

Manual integration

• Download the latest version of the Fyber Marketplace SDK for Android and add the following files to your project:
  • ia-mraid-kit-release-x.y.z.aar
  • ia-sdk-core-release-x.y.z.aar
  • ia-video-kit-release-x.y.z.aar
• Download the latest .aar file of the adapter from Bintray, located under the Files tab, and add it to your project.

Optional Steps

EU Consent and GDPR

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 com.fyber.inneractive.sdk.external.InneractiveAdManager;
// ...

InneractiveAdManager.setGdprConsent(true);
InneractiveAdManager.setGdprConsentString("myGdprConsentString");

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

Network-specific parameters

The Fyber Marketplace adapter supports additional supports an additional parameter to pass the user's age:

Here's a code example of how to set this parameter:

Java

Bundle extras = new Bundle();
extras.putInt(InneractiveMediationDefs.KEY_AGE, 10);

AdRequest request = new AdRequest.Builder()
       .addNetworkExtrasBundle(FyberMediationAdapter.class, extras)
       .build();

Kotlin

var extras = Bundle()
extras.putInt(InneractiveMediationDefs.KEY_AGE, 10)

var adrequest = AdRequest.Builder()
       .addNetworkExtrasBundle(FyberMediationAdapter::class.java, extras)
       .build()

Fyber Android Mediation Adapter Changelog

Version 7.7.0.0

• Verified compatibility with Fyber SDK 7.7.0.

Built and tested with:

• Google Mobile Ads SDK version 19.3.0.
• Fyber SDK version 7.7.0.

Version 7.6.1.0

• Verified compatibility with Fyber SDK 7.6.1.

Built and tested with:

• Google Mobile Ads SDK version 19.3.0.
• Fyber SDK version 7.6.1.

Version 7.6.0.0

• Verified compatibility with Fyber SDK 7.6.0.
• Updated the adapter to support inline adaptive banner requests.
• Updated the minimum required Google Mobile Ads SDK version to 19.3.0.
• Fixed a bug where onAdOpened()/onAdClosed() methods were not being called for banner ads.

Built and tested with:

• Google Mobile Ads SDK version 19.3.0.
• Fyber SDK version 7.6.0.

Version 7.5.4.0

• Verified compatibility with Fyber SDK 7.5.4.
• Updated the minimum required Google Mobile Ads SDK version to 19.1.0.

Built and tested with:

• Google Mobile Ads SDK version 19.1.0.
• Fyber SDK version 7.5.4.

Version 7.5.3.0

• Verified compatibility with Fyber SDK 7.5.3.

Built and tested with:

• Google Mobile Ads SDK version 19.0.1.
• Fyber SDK version 7.5.3.

Version 7.5.2.0

• Verified compatibility with Fyber SDK 7.5.2.
• Updated the minimum required Google Mobile Ads SDK version to 19.0.1.

Built and tested with:

• Google Mobile Ads SDK version 19.0.1.
• Fyber SDK version 7.5.2.

Version 7.5.0.0

• Verified compatibility with Fyber SDK 7.5.0.
• Fixed NullPointerException crash during Fyber ad loading.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Fyber SDK version 7.5.0.

Version 7.4.1.0

• Verified compatibility with Fyber SDK 7.4.1.
• Updated the minimum required Google Mobile Ads SDK version to 18.3.0.

Built and tested with:

• Google Mobile Ads SDK version 18.3.0.
• Fyber SDK version 7.4.1.

Version 7.3.4.0

• Initial release!
• Supports Banner, Interstitial and Rewarded ads.

Built and tested with:

• Google Mobile Ads SDK version 18.2.0.
• Fyber SDK version 7.3.4.