Interstitials: Adding Mediated Networks

Mediation Tips

We recommend to use several ad networks to maximize your fill rate and eCPM globally. Different ad networks have different strengths when it comes to regional coverage. Fyber interstitials mediation currently supports the following ad networks.

Fyber Mediation vs Fyber Open Mediation

Fyber Open Mediation adds a new layer of openness to the basic premise of mediation. Ad networks that participate in this program have complete control over building and maintaining the mediation bundles that allow them to connect to thousands of apps currently using Fyber for monetization.

Fyber Open Mediation gives you additional ad networks to choose from to maximize your global and country fill rate and eCPM. Built upon the close relationship between Fyber and international ad networks, this new program enables our partners to build the complete mediation integration while relying on Fyber’s best practices, support, and quality verification.

Through Fyber Open Mediation, ad network-created bundles have gone through our stringent Open Mediation requirement process to become a “Partner-built” bundle. Fyber also develops and maintains mediation integrations, noted in the Developer Portal as “Fyber-built”. Both “Fyber-built” and “Partner-built” integrations are available in our Developer Portal.

For further questions, see our Frequently Asked Questions about Open Mediation.

Download and Integration guides

Warning! All bundles support minimum SDK version 8.4.0.
Ad Network Mediation Bundles Guides Auto eCPM
AdColony Download Integration guide Yes
AdMob Download Integration guide Yes
AppLovin Download Integration guide Yes
Chartboost Download Integration guide Yes
Facebook Audience Network Download Integration guide Yes
Flurry Download Integration guide Yes
InMobi Download Integration guide Yes
Innneractive Download Integration guide Yes
LoopMe Download Integration guide No
Millennial Download Integration guide Yes
NativeX Download Integration guide No
Tapjoy Download Integration guide Yes
Tremor Download Integration guide Tremor has no Reporting API
UnityAds Download Integration guide Yes
Vungle Download Integration guide Yes

Mediation Checklist for Integrating Mediated Networks

The Mediation checklist gives you first steps for your integration of mediated networks into the Fyber SDK. Every mediated network must first integrate these first few steps. With the new Fyber SDK we take advantage of the power of annotation processing, which frees the publisher from time consuming and error prone tasks such as updating the now deprecated adapters.config and adapters.info files.

Using Gradle

If you are using Android Studio, you can integrate any of the mediated networks in three simple steps:

  1. Add the following maven dependencies to your gradle.build file:

         buildscript {
             dependencies {
                 classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
             }
         }
    
         apply plugin: 'com.neenbedankt.android-apt'
    
         configurations {
             provided
         }
    
         dependencies {
             provided 'com.fyber:fyber-annotations:1.3.0'
             apt 'com.fyber:fyber-annotations-compiler:1.4.0'
         }
    
  2. Add the @FyberSDK annotation to your main Activity.

  3. Download Fyber’s bundled adapters you wish to integrate.

Using Eclipse

If you are using Eclipse there are a couple more steps to the process:

  1. Download Fyber’s bundled adapter (shown above) you wish to integrate and add them to your project’s libs folder.
  2. Download and add the Fyber annotation jar to your project’s libs folder.
  3. Download and add the Fyber annotations processor jar to your project’s libs folder.
  4. Create a new folder on your project and name it. For this example we use annotation_libs, but the name is not relevant.
  5. Add the following jars to that folder:
    • [fyber-sdk] (https://bintray.com/artifact/download/fyber/mobile-sdk/Fyber_Android_SDK_v8.22.2.zip)
    • [fyber-annotations] (https://bintray.com/artifact/download/fyber/maven/com/fyber/fyber-annotations/1.3.0/fyber-annotations-1.3.0.jar)
    • [fyber-annotations-compiler] (https://bintray.com/artifact/download/fyber/maven/com/fyber/fyber-annotations-compiler/1.4.0/fyber-annotations-compiler-1.4.0.jar)
    • all the bundled jars you have added to libs folder
    • guava
    • javapoet
    • javassist
    • reflections
  6. Enable annotations in Eclipse:

    Go to project properties > Java Compiler > Annotation Processing > and check the Enable project specific settings checkbox: Enable annotations in Eclipse

    Go to project properties > Java Compiler > Annotation Processing > Factory Path > and click on Add JARs... button and add all jars on annotation_libs folder: Add JARs to factory path

    This will trigger a new build. Code generated by the annotation processor will be on apt_generatedd folder. If the code is not there try cleaning the project or restart Eclipse.

  7. Add @FyberSDK annotation to your main Activity and set up annotations on Eclipse.

Troubleshooting Tips

Multiple dex files

You might run into the following error trying to build the project:

Unable to execute dex: Multiple dex files define Landroid/UnusedStub;

This can be solved by removing Android Dependencies from your Java build path.

Incorrect screen metrics reading

You might also run into distorted end cards. This is caused by a wrong reading of the device’s screen metrics. To address this you need to include targetSdkVersion on the manifest.

Fyber Bundles

Fyber is now distributing Ad network SDK with its correspondent adapter as a bundle. Bundled SDKs are designed to streamline the way you integrate and update your mediated ad networks.

To provide your team with more information about our new integration process, we’ve compiled a list of the most frequently-asked questions below.

How will bundled SDKs change the way I integrate and update my mediated ad networks?

Instead of downloading the Fyber adapter, the mediated ad network SDK, and other libraries separately, the bundle houses all of these components in one package. This means that you can get everything you need to integrate a mediated ad network in a single download. You no longer need to drag several files into your project and individually match their versions – we do that for you!

How many ad networks are included in a bundle?

There is one bundle for each ad network that you integrate. You can drag and drop as many bundles to your project as you need.

How do I know which ad network SDK version the bundle is using?

Our bundles now follow the mediated ad network SDK version. If you get a bundle named for example: Flurry.6.3.0_r1. This is how the versioning works:

  • Flurry is the Ad network
  • 6.3.0 is the Flurry SDK version
  • r1 is the bundle minor version

We only update the bundle minor version if we need to release an update for a bundle that was created for a specific partner SDK version.

How much easier do bundles make the integration process?

With Fyber’s new bundled SDKs, you’ll get to the market faster because bundles: Save integration time: You don’t need to spend hours locating and matching correct versions of adapters and ad network SDKs. Reduce errors: Each bundle is diligently tested and certified to limit risk of version mismatch and other integration errors.

How do you ensure the bundles work properly?

Every bundled SDK goes through a certification process. Our mediation engineering team works closely with each of our mediated ad network partners to thoroughly understand their SDKs. If a given component of the bundle is failing, we analyze and patch it as quickly as possible. We have dozens of mobile and quality assurance engineers dedicated to testing our integrations on every imaginable device and OS version.

I already work with ad network X. How do I migrate to the new bundled SDK?

If you are migrating an existing integration to use bundles, there are three easy steps you need to follow:

  • Remove the ad network adapter files from your project.
  • Remove the ad network SDK from your project.
  • Download and add the bundle to your project.

I currently use standalone adapters. Can I continue using them in the future, or can I opt out of using bundles?

Bundles are now our standard integration path. We recommend using bundles, instead of standalone adapters, because they help get your app to market faster by streamlining integration and reducing the chance of common integration mistakes. However, if you can’t work with bundles for any reason please contact your account manager.

I have additional questions. How can I get more information?

That’s what we’re here for! Please feel free to contact your account manager with any other questions.