Unity Ads

This guide is intended for publishers who want to use the MoPub SDK to load and display ads from Unity Ads 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 Unity Ads. For the latest support, visit the Unity Ads homepage.

  • Banner
  • Interstitial
  • Rewarded Video

Download and Integration

To download the Unity Ads adapters, navigate to the Mediation Integration Tool. You must also download the Unity Ads SDK:

For the latest download and integration instructions, consult Unity Ads’ tutorials before you integrate the SDK and adapters.

Android Integration Help

UnityAds adapters are released as an Android Archive (AAR) file starting from version 3.0.1.1. The AAR includes the required Manifest data for UnityAds if any. As a result, you no longer have to update your AndroidManifest manually for any generic data, such as permissions and Activities. Any other app-level placement configuration required by Unity Ads must be manually entered into the AndroidManifest..

Set Up Unity Ads on the MoPub Dashboard

  • Game ID and Placement ID are required.
  • Placement ID is backwards-compatible with Zone ID.

Network Reporting and Auto CPM

To enable Unity network reporting and Auto CPM, you must enter the API Key and Organization Core ID. unityads-reporting-1 unityads-reporting-2

This setup is required to take advantage of Auto CPM.

Migrate to Unity Ads Monetization Stats API

If you set up Unity Network Reporting before May 18, 2020 you are connected to their legacy Applifier API which is being sunset by Unity Ads on July 1, 2020. You must migrate to Unity’s new Monetization Stats API in order to maintain your connection to network reporting and Auto CPM. To migrate:

  1. Select Unity Ads within the Networks tab
  2. Under Reporting Access enter your API Key and Organization ID for Unity Ads’ new Monetization Stats API
  3. Save

Migrate Unity Ads from Custom Native Setup

  1. Transfer Game ID and Placemet ID (if applicable) from the old custom native connection to the supported Unity Ads instance. Note that if you are using Unity Ads 1.x, Unity Ads has renamed Zone IDs to Placement IDs. You can input Zone IDs in the Placement ID input field, and MoPub will handle the conversions.

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

    • iOS

      • UnityAdsInterstitialCustomEvent
      • UnityAdsRewardedVideoCustomEvent
    • Android

      • com.mopub.mobileads.UnityInterstitial
      • com.mopub.mobileads.UnityRewardedVideo

    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 Unity Ads network UI set up for backward compatibility.

Important: During migration, make sure the custom native network and the Unity Ads 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 for a consistent fill rate. To set up test mode, follow the instructions in Unity Ads’ test ad article.

Additional Support

For inquiries and support, visit Unity Ads’ support center.

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.)