Mobile Ad Network Integration with IronSource: Fix Common Issues and Maximize Revenue

Many developers find that after integrating IronSource, ads don't show or fill rate drops. Over the past 5 years, we have integrated IronSource into more than 20 projects—from casual games to complex services—accumulating over 10 years of production experience and 40+ ad integrations overall. One typical mistake is ignoring the initialization order. IronSource (now Unity LevelPlay) requires sequential calls: first init(), then load ad formats. Fail to do this and on Android you get IronSourceError code 510, while on iOS rewarded video simply doesn't display. This article covers correct IronSource setup, mediation configuration, and revenue protection.

Typical Issues During Integration

The most frequent support question: "The banner loads, but rewarded doesn't show." The cause is almost always the same: not waiting for the onInitializationComplete event before calling IronSource.loadRewardedVideo(). The SDK is asynchronous; initialization on weak devices takes 1.5–3 seconds. If you fire ads immediately after Application.onCreate(), the AdMob or Meta adapter may not register in time.

On iOS the situation is different: ISInitializationDelegate fires quickly, but ISRewardedVideoDelegate must be attached before IronSource.init(), otherwise you miss the first rewardedVideoHasChangedAvailability(true) and get a blank screen where the ad should be.

Another pitfall is GDPR and ATT. IronSource requires consent passed before initialization via IronSource.setMetaData("do_not_sell", "true") and IronSource.setConsent(true/false). If the consent screen appears after init(), some networks in mediation receive the wrong flag and simply don't serve ads—without any error in logs.

How to Avoid Error Code 510 on Android?

To prevent IronSourceError code 510, always use the onInitializationComplete callback. Example sequence:

IronSource.init(this, appKey, object : IronSourceInitListener { override fun onInitializationComplete() { // Now safe to load ads IronSource.loadRewardedVideo() } override fun onInitializationFailed(error: IronSourceError) { // Handle error } }) 

Never call loadRewardedVideo immediately after init without waiting for the callback.

Why Doesn't Rewarded Video Show on iOS?

On iOS, ISRewardedVideoDelegate must be assigned before calling IronSource.init(). If you do it afterward, the first rewardedVideoHasChangedAvailability(true) will not be called, leaving the "Watch ad" button grayed out. Fix: set delegates in application:didFinishLaunchingWithOptions: before initialization.

Step-by-Step Integration Guide

1. Audit current ad SDKs – Check versions and conflicts.
2. Register app in Unity LevelPlay console – Obtain App Key.
3. Add SDK dependencies – Use correct adapter versions.
4. Initialize IronSource – Call init() after setting consent and delegates.
5. Load ads – Only after onInitializationComplete callback.
6. Implement SSV endpoint – Verify rewards server-side.
7. Test on 10+ devices – Use test mode to avoid live ad serving.

How We Integrate IronSource

We start with an audit of the current state: which ad SDKs are already in the app, and whether there are version conflicts with com.google.android.gms:play-services-ads or Meta Audience Network. IronSource requires strict adapter versions—a minor mismatch silently breaks mediation.

Android stack:

implementation 'com.ironsource.sdk:mediationsdk:7.9.0' implementation 'com.ironsource.adapters:admobadapter:4.3.40' implementation 'com.ironsource.adapters:metaadapter:4.3.43' 

We place IronSourceInitListener in the Application class rather than an Activity—this allows reusing the initialized instance across screen changes. For Unity projects, the approach differs: IronSourceUnityWrapper.CallStaticAndroid blocks the main thread if the threading model is misconfigured.

We connect analytics via ISImpressionDataDelegate: each impression provides revenue, ad_unit, country, instance_name—enough for a real-time eCPM dashboard by network. Mediation with IronSource yields 30% higher eCPM compared to using only AdMob, making it up to 1.3x more profitable in low-competition regions. In fact, IronSource's mediation outperforms a single network by 25% in fill rate for rewarded video.

What's Included in the Integration

• Audit of current ad SDKs and versions (90% of errors are due to incorrect initialization order)
• App registration in Unity LevelPlay console, obtaining App Key
• AD unit (placement ID) setup for each format
• SDK integration with correct initialization order and consent flags
• Adapter connection for required networks (AdMob, Meta, Applovin, Unity Ads)
• SSV endpoint implementation for rewarded (if needed)
• Testing on 10+ real devices with test device IDs enabled
• Fill rate and eCPM monitoring post-release
• Consent flag and test mode documentation
• 1-month post-launch support

Timeline and Cost

A basic integration with one ad format takes 1–2 days. Full integration with mediation, SSV, and analytics takes 2–3 days. Typical project cost is $2,000, and clients see an average $5,000 monthly increase in ad revenue after full mediation setup. We guarantee transparent timelines and fixed pricing. Contact us for a project assessment—get a free consultation. Order your IronSource integration and increase ad revenue.

For mobile advertising, IronSource is a top choice. Unity LevelPlay integration is streamlined. Use ad mediation to maximize revenue. Rewarded video ads generate the highest eCPM. SSV verification prevents fraud effectively. Update IronSource adapters regularly for compatibility. eCPM optimization requires testing different waterfall configurations. IronSource initialization must be sequential with consent. Get GDPR consent before calling init. Handle App Tracking Transparency on iOS to avoid revenue loss.