An ironSource Exchange alternative must use the current product distinction. The catalog records that ironSource Ads direct demand ended on April 30, 2026, while iSX programmatic exchange demand continues separately. LevelPlay is a mediation platform. Older articles that treat these as one active network can send developers toward an obsolete onboarding path.
APP PLATFORMS / EDITORIAL SHORTLIST
The shortlist at a glance
These are options for different needs, rather than a highest-paying ranking. Read the product roles and the reasons below before replacing your current setup.
| Platform & role | Consider it for | Setup / minimum payout | Explore |
|---|---|---|---|
| Mobile ad exchange | App publishers considering Digital Turbine’s programmatic exchange demand.Confirm the provider’s own eligibility and demand requirements. | Medium setup effortEditorial estimate, not an approval probability. Per partner contract | Compare with ironSource Exchange (iSX) →Official reference ↗ |
| Mobile ad exchange | App publishers evaluating Verve Brand+ demand via Smaato NextGen SDK or supported mediation.Confirm the provider’s own eligibility and demand requirements. | High setup effortEditorial estimate, not an approval probability. Per publisher contract; confirm the applicable minimum | Compare with ironSource Exchange (iSX) →Official reference ↗ |
| In-app bidding service | App publishers evaluating Amazon and other demand through APS in-app bidding.Confirm the provider’s own eligibility and demand requirements. | High setup effortEditorial estimate, not an approval probability. Per product and partner agreement | Compare with ironSource Exchange (iSX) →Official reference ↗ |
| Ad network / Mediation | App developers evaluating Google demand together with optional mediation.Google demand is involved; relevant publisher policies still apply. | Medium setup effortEditorial estimate, not an approval probability. USD $100 · other currencies vary | Compare with ironSource Exchange (iSX) →Official reference ↗ |
| Mobile ad network | Game and app developers adding Unity advertising demand directly or through a supported mediator.Confirm the provider’s own eligibility and demand requirements. | Medium setup effortEditorial estimate, not an approval probability. See Unity payment settings | Compare with ironSource Exchange (iSX) →Official reference ↗ |
| Mobile ad network | App developers adding Moloco publisher demand to a supported mediation stack.Confirm the provider’s own eligibility and demand requirements. | Medium setup effortEditorial estimate, not an approval probability. Per publisher contract; no universal minimum verified | Compare with ironSource Exchange (iSX) →Official reference ↗ |
Requirements and payments reuse the catalog compiled 2026-11-03; confirm current account and country terms with each provider. See the ironSource Exchange (iSX) profile for the baseline, and our commercial disclosure for referral relationships.
What to replace in your ironSource Exchange (iSX) setup
First confirm with Unity which iSX access and integration is available to your account. If you are replacing legacy direct demand, do not assume the same credentials or product rules apply to the exchange. Choose another source based on the actual supply role, supported mediator and app inventory you need.
ironSource Exchange (iSX) alternatives by use case
1. DT Exchange: Another in-app exchange relationship
DT Exchange is a relevant option for reviewed programmatic app inventory through supported SDK or partner integrations. It is distinct from DT FairBid mediation. Confirm the exchange account, placement configuration and settlement terms directly before treating it as a replacement for an iSX supply relationship.
Compare ironSource Exchange (iSX) vs DT Exchange · Platform requirements and payments
2. Smaato / Verve Brand+: An exchange option through current Verve products
Smaato / Verve Brand+ is worth assessing for app supply through the current NextGen SDK or supported mediator route. Verify inventory review, store listing and consent requirements. Historical SDK adoption does not demonstrate present demand or automatic eligibility for your app.
Compare ironSource Exchange (iSX) vs Smaato / Verve Brand+ · Platform requirements and payments
3. Amazon Publisher Services: A separate in-app bidding path
APS is relevant if an available mobile product and supported integration fit your inventory. Confirm account access, contracts and demand-source payment arrangements. Do not import TAM or UAM web assumptions into the app decision, and do not assume the product replaces every existing supply contract.
Compare ironSource Exchange (iSX) vs Amazon Publisher Services · Platform requirements and payments
4. Google AdMob: Google network demand with optional mediation
AdMob is a candidate where the app can meet Google review and verification requirements. Decide whether the change is demand only or a full mediation migration. Account access and policy compliance remain independent of the fact that an ironSource-related integration previously worked in the app.
Compare ironSource Exchange (iSX) vs Google AdMob · Platform requirements and payments
5. Unity Ads: A distinct Unity demand product
Unity Ads is a separate network that can be relevant for supported app placements. It is not the same as iSX and not another name for LevelPlay. Confirm the currently supported SDK or mediator route and account setup, rather than reuse obsolete ironSource direct-demand instructions.
Compare ironSource Exchange (iSX) vs Unity Ads · Platform requirements and payments
6. Moloco SDK: Another publisher bidding source
Moloco SDK is worth considering where publisher portal access and supported adapters are available. Obtain the current account and bidding credentials before integration. It supplies a demand relationship, not a complete exchange or mediation operation, so compare the scope explicitly.
Compare ironSource Exchange (iSX) vs Moloco SDK · Platform requirements and payments
Before switching from ironSource Exchange (iSX)
Inventory legacy ironSource instances and distinguish direct demand, iSX and LevelPlay configuration. Use current Unity documentation to establish what remains supported. Confirm new source access before code changes, test auction and consent behavior in staged releases, and preserve records for final payments under each applicable demand agreement.
Every network can require its own app approval, privacy configuration and payment verification. A mediation account does not automatically approve the sources connected to it.
How to judge the result
Compare net ad ARPDAU, request coverage, fill, rendered-impression eCPM and impressions per user by OS, country and format. Include load latency, crashes and retention. A higher eCPM on fewer filled requests is not by itself a better monetization result.
We have not verified a controlled revenue benchmark or a comparable approval-rate dataset for this shortlist. The setup labels are editorial estimates, and all account-specific terms should be checked with the provider. The table links to official references and full profiles so you can confirm the details that apply to your business.
Which option should you shortlist?
DT Exchange, Verve and APS are the more direct exchange or bidding conversations. AdMob, Unity Ads and Moloco are network alternatives with distinct roles. Verify current iSX availability first so the migration solves today’s product issue rather than follows a retired guide.
Use the app platform directory to check the wider catalog, or open the ironSource Exchange (iSX) profile to revisit the baseline requirements. This guide uses the existing directory research compiled November 3, 2026; it does not claim a fresh independent review of every provider policy.
Eligibility and payment policies may change. Before applying, check the platform’s current terms and your account settings.
← Back to all articles