Integrate Zucks with mediation

  • The Mediation Test Suite allows you to test whether your mediation setup is configured correctly before going live to ensure ad requests and revenue are flowing as expected.

  • By integrating the Mediation Test Suite into your app, you gain access to detailed, real-time insights into the ad mediation waterfall to troubleshoot setup problems quickly.

  • The suite offers comprehensive functionalities such as manual ad requests for testing specific scenarios, a visual ad request waterfall, and adapter status reports to monitor adapter configuration.

  • It enables you to manage and organize multiple ad units and ad sources within the test suite, including line item details and other properties for each ad source.

  • This ensures a seamless and optimized ad mediation experience, leading to higher fill rates, increased ad revenue, and improved app performance.

This guide is intended for publishers who are interested in using Google Mobile Ads mediation with Zucks. It walks through the setup of a mediation adapter to work with your current Android app and the configuration of additional settings.

Zucks Resources
Documentation
SDK
Adapter
Customer support

Prerequisites

Helpful primers

The following Help Center articles provide background information on mediation:

Add Zucks to your project

Include network adapter and SDK

Download the Zucks SDK and adapter from the previous links.

In Android Studio, include the adapter and SDK files in your project's libs folder. Make sure that your app-level Gradle file includes the following:

Kotlin

dependencies {
    implementation(fileTree(mapOf("dir" to "libs", "include" to listOf("*.aar", "*.jar"))))
    // ...
}

Groovy

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.aar', '*.jar'])
    // ...
}

Configure the AndroidManifest.xml file

Modify your AndroidManifest.xml file as instructed in the Zucks documentation.

Your app doesn't need to call Zucks directly—Google Mobile Ads SDK calls the Zucks adapter to fetch ads on your behalf. If necessary, you can specify any additional request parameters. The rest of this page details how to provide more information to Zucks.

Initialize your ad object with an Activity instance

In the constructor for a new ad object (for example, AdView), you must pass in an object of type Context. This Context is passed on to other ad networks when using mediation. Some ad networks require a more restrictive Context that is of type Activity and may not be able to serve ads without an Activity instance. Therefore, we recommend passing in an Activity instance when initializing ad objects to ensure a consistent experience with your mediated ad networks.