DFP Android SDK Mediation (v2.0)


Our SDK has embedded all needed classes to be called from DFP. To use our SDK from DFP, you need to attach our SDK to your project.

Integrate the SDK with Maven

Add this line in your "build.gradle":

repositories {

dependencies {
    implementation 'com.tappx.sdk.android:tappx-sdk:3.+'


If you are using proguard in your app, you must add the following lines to your setup file:

-keepattributes *Annotation*
-keepclassmembers class com.google.**.R$* {
    public static ;
-keep public class com.google.ads.** {*;}
-keep public class com.google.android.gms.** {*;}
-keep public class com.tappx.** { *; }

Installation tracking

(cross promotion only)

In this document we will explain the most difficult variant of configuration to use install tracking. Why I do this? Because a lot of our developers already have other tracking services/networks (Analytics, Flurry, etc.), and if you don’t have any other tracking service, If you create this class/method you will prepare your app for the future.
We will have to edit our AndroidManifest.xml to call our class when one user installs our app from market. (This class is always called that one user installs our app, but Tappx's tracking only counts installations that proceeds from a click of our network banners).


Important: The declared broadcast must have the android:exported="true" property in order to work properly.

SDK Mediation

Now you can use our SDK with Tappx, and with ADX/AdMob, or with any other exchange/network as you wish, our SDK gives you the possibility to do multi-call and mediate between these networks.

Follow these steps:

  1. In the "Delivery" option, you click in "Yield Groups":

Very Important: If you don't have this option, you contact with the Google Support to active this option.

  1. Create a "New Yield Group" if you don't have:

  2. When you have your "Yield Group", you create a new "Yield Partner":

  3. Now you select Tappx as "Yield Partner". If you don't have Tappx as an option, you create a "New Yield Partner":

  4. For you create a new "Ad Network", you select "Other Networks" and enable the option "Mediation":

Custom Event Configuration

In the form add the next fields:
1. Yield Partner: Tappx
2. Integration Type: Custom Event
3. Plataform: Android
4. Status: Active

You add in "Additional yield partner details":

  • Class Name:
    • For Banner: com.tappx.sdk.adapters.DfpBannerAdapter
    • For Interstitial: com.tappx.sdk.adapters.DfpInterstitialAdapter
  • Label: Only required to provide you a description…
  • Parameter: Network KEY (for example, for your tappx key (format: Pub-xxxx-Android-xxxx)

Example of a possible full configurationWith this configuration you can first call up your direct campaigns, then if nothing is found, DFP will call to Google AdExchange and, finally, if nothing has been found, DFP will call to Tappx SSP. (you can decide the correct order in your Mediation Waterfall).NOTE: You only can use our SDK Mediation to call to your DFP, AdExchange, TappxSSP and TappxCrosspromotion, then to call them you only need to use your DFP/AdExchange/Tappx KEYS (each one has its own format).

Tappx © 2020