Integrate Zucks with AdMob Mediation

  • This guide helps publishers integrate Zucks ad network with their existing apps using Google Mobile Ads Mediation.

  • It outlines the process of setting up a mediation adapter and configuring request parameters for Zucks.

  • Publishers need an app with Google Mobile Ads SDK, an AdMob account, and ad units configured with mediation line items as prerequisites.

  • Integration involves downloading the Zucks SDK and adapter, including them in the Unity project, and potentially configuring AndroidManifest.xml or Xcode settings.

This guide is intended for publishers who are interested in using AdMob Mediation with Zucks. It walks you through getting a mediation adapter set up with your current app and setting up additional request parameters.

Zucks Resources
Documentation
SDK
Adapter
Customer support

Prerequisites

Helpful primers

The following Help Center articles provide background information on mediation:

Include network adapter and SDK

Download the SDK and adapter for Zucks from links provided. Some SDKs already include a Google Mobile Ads SDK adapter, while others offer it as a separate file. See the integration instructions or README that's included with each adapter.

Include the mediated networks' SDKs and adapter files within the appropriate directory of your Unity project:

  • Android: Assets/Plugins/Android
  • iOS: Assets/Plugins/iOS

Include network configurations

Android
Some ad networks require extra configurations to be added to your AndroidManifest.xml file. You can make these modifications to the AndroidManifest.xml inside the Assets/Plugins/Android/GoogleMobileAds directory.
iOS
After generating an Xcode from Unity, include any frameworks, compiler flags, or linker flags that your chosen networks require.

Your app need not call any third-party ad network code directly; Google Mobile Ads SDK interacts with the mediated network's adapter to fetch third-party ads on your behalf.