Rewarded Video: 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 supports minimum SDK 8.4.0
Ad Network Mediation Bundles Guides Auto eCPM
AdColony Download Integration guide Yes
AppLovin Download Integration guide Yes
Chartboost Download Integration guide Yes
Flurry Download Integration guide Yes
HyprMX Download Integration guide Yes
InMobi Download Integration guide Yes
LoopMe Download Integration guide No
Mediabrix Download Integration guide No
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 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 file:

         buildscript {
             dependencies {
                 classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
         apply plugin: ''
         configurations {
         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 compiler 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] (
    • [fyber-annotations] (
    • [fyber-annotations-compiler] (
    • 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: Alt Text

    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.