FAQ
What is MDN11?
MDN11 is an SDK for iOS, Android and Unity that optimizes the mediation platform you already use, such as AppLovin MAX, LevelPlay, AdMob or Google Ad Manager (GAM). It sits between your app and your mediation platform and finds the highest-value ad for every impression through smarter pre-caching and adaptive user-level floor prices across multiple ad units.
Does MDN11 replace my existing mediation platform?
No. MDN11 works on top of your existing mediation platform. The MDN11 SDK wraps the mediation SDK you already use, and you connect it by adding the matching MDN11 adapter.
For example, an app that already uses the AppLovin MAX SDK keeps it. The MAX SDK still serves and renders the ads, and you keep using the MAX dashboard. Only your integration code changes:
| Your app calls | Which then calls | |
|---|---|---|
| Before | MAX SDK: initialize, load and show ads | n/a |
| With MDN11 | MDN11 SDK: initialize, load and show ads | MAX SDK: initialize, load and show ads |
Which ad network adapters do I need?
Declare an adapter for each mediation platform on your MDN11 account. Aurion11 confirms which ones those are during integration.
Which SDK and adapter versions should I use?
Use the versions listed in Supported ad networks and in your platform's changelog. On Android, use the BOM and omit the versions on all MDN11 artifacts, so the SDK and all adapters stay on a matching set of versions.
Android changelog · iOS changelog · Unity changelog
Can I initialize a mediated network's SDK myself?
You can, but we advise against it. Most SDKs can only be initialized once and use the config of whichever caller is first, so MDN11 may not be able to apply its own config.
If your question isn't answered here, contact your Aurion11 representative.