AdColony

This guide is intended for publishers who want to use the MoPub SDK to load and display ads from AdColony via mediation. Below, you will find information about the ad network, integration/setup instructions, and more. For more information about how MoPub mediation works, visit this guide.

Supported Ad Formats

The following ad formats are currently supported by AdColony. For the latest support, visit the AdColony homepage.

  • Banner (Advanced Bidding not supported)
  • Medium Rectangle
  • Interstitial
  • Rewarded Video

Download and Integration

To download the AdColony adapters, navigate to the Mediation Integration Tool. You will also need to download the AdColony SDK, which can be found below.

For the latest download and integration instructions, ensure that you have consulted AdColony’s tutorials before you integrate the SDK and adapters.

iOS Download
Android Download
  • Android Integration Help: AdColony adapters are released as an Android Archive (AAR) file starting from version 3.3.8.1. The AAR includes the required Manifest data for AdColony. As a result, publishers no longer have to update their AndroidManifest manually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by AdColony must be manually entered into the AndroidManifest.

Set Up AdColony on the MoPub Dashboard

  • App ID and Zone ID are required. Each Zone ID must be unique per MoPub ad unit.
  • No field is provided for allZoneIds but allZoneIds will be passed to the AdColony adapters. They will contain all of the Zone ID entries for that app.
  • clientOptions is optional and only applicable on Android.

Network Reporting and Auto CPM

To enable AdColony network reporting and Auto CPM, enter the API Key.

Ad Colony Reporting

To find the API Key, navigate to Settings and look for Read-Only API Key.

This setup is required to take advantage of Auto CPM.

Migrate AdColony from Custom Native Setup

  1. Transfer the App IDs and Zone IDs (if applicable) from the old custom native connection to the supported AdColony instance.

  2. MoPub will initiate the following AdColony mediation adapter class names to render the ads:

    • iOS

      • AdColonyBannerCustomEvent
      • AdColonyInterstitialCustomEvent
      • AdColonyRewardedVideoCustomEvent
    • Android

      • com.mopub.mobileads.AdColonyBanner
      • com.mopub.mobileads.AdColonyInterstitial
      • com.mopub.mobileads.AdColonyRewardedVideo

    If you are manually entering these class names, migrate to the new network setup and pause the “Custom Native Network.” If you are using your own mediation adapter class names, have both the old custom native network and the new AdColony network UI set up for backward compatibility.

Important: During migration, make sure the custom native network and the AdColony network are not both live at the same time, because this may impact your revenue.

Test Ad

While testing your SDK integrations and network setups, we recommend that you leverage test ad placements. To set up test mode, follow the instructions in AdColony’s dashboard setup tutorial, “Step 3: Toggle Test Ads.”

Advanced Bidding - Android Build Requirements

On Android, AdColony SDK depends on Google Play Services dependencies to gather the Advertising ID of the Android device. Without this identifier, AdColony ad server would not bid on Advanced Bidding requests. Related AdColony documentation can be found here.

  • Android: Please make sure the following dependencies are installed

    • com.google.android.gms.play-services-ads
    • com.google.android.gms.play-services-ads-base
    • com.google.android.gms.play-services-ads-identifier
    • com.google.android.gms.play-services-ads-lite
    • com.google.android.gms.play-services-basement
    • com.google.android.gms.play-services-measurement-base
    • com.google.android.gms.play-services-measurement-sdk-api
  • Unity: These dependencies are included with MoPub AdColony Unitypackage starting version 1.1.8.

The Advertising ID value can’t be obtained if user opts out of ads personalization and limits ads tracking. In this case, AdColony ad server won’t bid on Advanced Bidding requests.

Important: On Unity to Android cases, there’s an additional step necessary to ensure AdColony SDK initializes early on to serve Advanced Bidding requests. You need to pass your AdColony app id and zone ids information to MoPub’s initialization sequence:

  • If you’re initializing MoPub automatically by using MoPub Manager Prefab, please see the section called Network Configuration here.

  • If you’re initializing MoPub manually, please follow the example here.

Additional Support

For inquiries and support, please email AdColony at support@adcolony.com.

Last updated June 09, 2020

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2020 MoPub (a division of Twitter, Inc.)