ironSource

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 will also need to download the ironSource SDK, which can be found below.

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

iOS Download
Android Download

Android Integration Help

Note: IronSource adapters are released as an Android Archive (AAR) file starting from version 6.8.2.1. 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 com.google.android.gms.ads.** {
   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.

Migrate Ad Network Name from Custom Native Setup

  • Transfer App Key and Instance ID from the old custom native connection to the supported ironSource instance.
  • MoPub will initiate the following ironSource custom event class names to render the ads:
    • iOS
      • IronSourceInterstitialCustomEvent
      • IronSourceRewardedVideoCustomEvent
    • Android
      • com.mopub.mobileads.IronSourceInterstitial
      • com.mopub.mobileads.IronSourceRewardedVideo

Note: If you are manually entering the above-mentioned class names, migrate to the new network setup and pause the “custom native network”. If you are using your own custom event class names, you should have both the old custom native network setup & the new ironSource network UI setup for backward compatibility.

Note: During migration, please make sure the custom native network and the ironSource network are not live at the same time as this may cause revenue-impacting issues.

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, it is recommended that you leverage test ad placements for a consistent fill rate. To set up test mode, please reference ironSource’s test ad article for Android and iOS for instructions.

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

Additional Support

For inquiries and support, please reach out to ironSource.

Last updated August 26, 2019

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.

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