App Monetization
Unity LevelPlay
Unity LevelPlay is Unity's app and game monetization mediation platform, built from the former ironSource product and still accessed through parts of the ironSource account infrastructure. A single SDK connects multiple ad networks and supports real-time bidding, waterfall management, automated optimization, reporting, testing, and common formats such as rewarded video, interstitials, and banners. It fits mobile developers that need active control over a multi-network monetization stack, especially game teams already using Unity services or ironSource integrations.
What it does
Unity LevelPlay is Unity's mediation platform, carrying forward the former ironSource product after the 2022 merger. One SDK connects a publisher's inventory to dozens of ad networks through real-time bidding, traditional waterfalls, or hybrid setups, with A/B testing for comparing configurations and segment-level controls. It supports rewarded video, interstitial, banner, and offerwall formats, with ironSource Ads and Unity Ads demand alongside external bidders. Reporting covers revenue, eCPM, and fill by network, geography, and segment, with impression-level revenue data available for ROAS measurement loops. For Unity-built games, integration sits close to the engine tooling. It competes head-to-head with AppLovin MAX for the core game mediation market.
Where it fits
LevelPlay is the mediation decision layer of app monetization, arbitrating demand from networks like AdMob, Liftoff, and InMobi above the publisher's inventory.
Core features
- Real-time bidding, waterfall, and hybrid mediation
- Unity Ads and ironSource demand plus external networks
- A/B testing of mediation configurations
- Segment and geography level revenue reporting
- Impression-level revenue data for ROAS workflows
Best for
- Game studios, especially those building in Unity
- Publishers running multi-network monetization operations
- Teams that want built-in experimentation on ad stack changes
Beginner notes
- Migrating mediation platforms is a significant SDK project, so trial configurations seriously before committing the portfolio.
- Start with bidding networks rather than hand-managed waterfalls, then add waterfall instances only where they prove incremental.
- Use the A/B testing on real traffic segments before rolling out stack changes, because eCPM differences between setups are rarely intuition-friendly.