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

  • Interstitial
  • Rewarded Video

Download and Integration

To download the Ad Network Name adapters, navigate to the Mediation Integration Tool. You must also download the ironSource SDK:

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

Android Integration Help

IronSource adapters are released as an Android Archive (AAR) file starting from version The AAR includes the required Manifest data for IronSource. 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 ironSource must be manually entered into the AndroidManifest.

For users leveraging ProGuard, be sure to add the following code to your ProGuard profile:

-keepclassmembers class com.ironsource.sdk.controller.IronSourceWebView$JSInterface {
    public *;
-keepclassmembers class * implements android.os.Parcelable {
    public static final android.os.Parcelable$Creator *;
-keep public class** {
   public *;
-keep class com.ironsource.adapters.** { *;
-dontwarn com.ironsource.mediationsdk.**
-dontwarn com.ironsource.adapters.**
-dontwarn com.moat.**
-keep class com.moat.** { public protected private *; }

Set Up Ad Network Name on the MoPub Dashboard

App Key and Instance ID are required fields.

Network Reporting and Auto CPM

To enable ironSource network reporting and Auto CPM, you must enter the Username and Secret Key.

ironSource reporting 1

To find the Username and Secret Key, from My Account, navigate to the API tab.

This setup is required to take advantage of Auto CPM.

Migrate Ad Network Name from Custom Native Setup

  1. Transfer App Key and Instance ID from the old custom native connection to the supported ironSource instance.

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

    • iOS

      • IronSourceInterstitialCustomEvent
      • IronSourceRewardedVideoCustomEvent
    • Android

      • com.mopub.mobileads.IronSourceInterstitial
      • com.mopub.mobileads.IronSourceRewardedVideo

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

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

Set Up Reporting

The username is the login/e-mail that is used to login to the ironSource UI. The Secret Key parameter is unique for your ironSource account. To retrieve it, click on your user profile on the top right corner of the screen, and select My Account. You will find the Secret Key in the Reporting API section.

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 ironSource’s test ad articles for Android and iOS.

For details about available error codes as well as potential resolutions, reference ironSource’s documentation.

Additional Support

For inquiries and support, contact ironSource.

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