Mobile Ad Tech News: AppLovin v Unity Lawsuit, GMA Next-Gen SDK, and the ironSource Ads Sunset (2026)

Three things changed in mobile ad tech in the last 30 days, and every app developer should know about them

Ad tech has been quietly reshuffling all year, but October 2026 is when the changes became impossible to ignore. A San Francisco judge sent the biggest case in mobile advertising to private arbitration. Google shipped a new generation of its mobile ads SDK. Unity finished killing a legacy ad network it acquired for billions. None of these are abstract platform-policy updates. They change which SDKs are worth integrating, what your mediation stack looks like, and where the real money in your app is going to come from in 2027. If you are still deciding between platforms, our highest paying offerwall platforms comparison ranks the current options by what publishers actually earn.

Here is what actually happened, what it means for publishers, and what to do about it.

1. AppLovin sued Unity and lost its first shot at stopping the Ad Quality SDK

On September 27, 2026, AppLovin filed for arbitration against Unity Technologies at JAMS, then petitioned the Superior Court of California in San Francisco for emergency relief the next day. On October 2, the court denied AppLovin’s request for a temporary restraining order. AppLovin shares fell more than 5% in premarket trading that morning.

The substance of the dispute matters more than the stock move. AppLovin alleges that Unity’s Ad Quality SDK, a tool marketed to publishers for catching harmful or broken ads, collects data belonging to ads that AppLovin’s MAX mediation platform won. According to the filings, that includes ad creatives, device and user identifiers, impression revenue, auction clearing prices, and mediation waterfall configuration.

AppLovin’s technical claim, as reported by Digiday, is unusually specific: Unity’s SDK allegedly used AppLovin-specific connector scripts, hooked into callbacks inside AppLovin’s own code, and subscribed to an internal channel carrying impression and revenue events. The legal theories are breach of contract, misappropriation of trade secrets under California law, and unfair competition. Notably, this is not an antitrust case. AppLovin is not claiming Unity has a monopoly.

Unity’s response is that Ad Quality is a publisher-authorized tool operating with consent, and that it falls outside the two companies’ bidding agreement. A Unity spokesperson called it “a small, free product” and said AppLovin believes the data publishers share through Ad Quality is driving Unity’s improving performance.

What the denial does and does not mean is important. The court addressed interim emergency relief, not the merits. Unity keeps running Ad Quality unchanged for now, and the substantive contract and trade-secret claims proceed in confidential JAMS arbitration. Because that process is private, the dispute may never be fully public unless one side discloses the outcome.

The precedent is the real story. Two of mobile gaming’s biggest infrastructure companies are now fighting over who owns the data generated when a game shows an ad. Wedbush analyst Alicia Reese framed the ruling as a “conspicuous competitive shift,” and noted the difficulty of protecting data “particularly where it passes through publishers’ apps.”

2. Unity finished shutting down ironSource Ads direct demand

Unity announced on March 26, 2026 that it would sunset the direct demand business of the ironSource Ads network, and the cut-off landed on April 30, 2026. Onboarding of new iAds publishers stopped April 15. The iAds dashboard moved to reporting-only, with historical data retained for a year.

The part that trips up most developers: the IronSource Exchange was not shut down. Programmatic campaigns through iSX continue to serve. Unity’s own guidance is to keep the iAds SDK integrated so iSX continues delivering programmatic demand to your inventory.

LevelPlay mediation itself is unaffected. Unity describes it as still their core open mediation platform, and says retiring the ironSource Ads network simply removes one ad network from that platform while the rest continue to work the same way. If you use Ad Quality natively, no action is required, but if your Ad Quality reporting was bundled with the iAds SDK and you do remove it, you need to migrate to a native Ad Quality SDK integration to keep reporting continuity.

For publishers still running ironSource Ads alongside Unity Ads, this is now a completed migration rather than a pending one. If you were an ironSource or Tapjoy shop, our Tapjoy alternatives comparison covers what the independent options look like now. Ad Quality itself has continued shipping through the dispute: Unity reportedly released Ad Quality SDK 9.9.0 in August 2026, adding support for Google’s AdMob Next-Gen SDK, and 9.10.0 in September 2026, which Unity says reduced initialization time and memory use.

3. Google moved its Android ads SDK to Next-Gen, and version 1.6.0 landed on October 22

The Google Mobile Ads SDK for Android is now in maintenance mode. Google says to migrate to the GMA Next-Gen SDK, which reached general availability in July 2026 after a beta opened in January.

The version history since GA shows how fast the new SDK is moving:

• 1.6.0 (October 22, 2026) – fixed a bug where rewarded and rewarded interstitial ads could invoke onUserEarnedReward() after onAdDismissedFullScreenContent(). That specific bug is worth flagging for anyone whose reward logic assumes a single clean callback order, because it can fire your reward callback after the ad is already dismissed.
• 1.5.0 (September 24, 2026) – signal generation and rendering APIs for the SwipeableInterstitialAd format, in private beta.
• 1.4.0 (August 20, 2026) – PictureInPictureAd format support, in open beta.
• 1.3.0 (July 21, 2026) – NO_FILL instead of INTERNAL_ERROR when no ads are available for native or icon ad requests.

Google also markets the Next-Gen SDK as up to 17% smaller than the previous version. If you are still on the legacy SDK, you are running an SDK that is no longer receiving new features while the platform you monetize through is being rebuilt.

What the Newzoo numbers mean for where your revenue should come from

The ad tech changes above matter because of what is happening underneath them. Newzoo’s 2026 report, recapped by GameDevReports and EventFAQs, puts hard numbers on a shift that publishers have been describing in qualitative terms for years.

• Mobile now accounts for 3.10 billion players, or 83.9% of everyone who plays games on any device.
• Mobile revenue is forecast at $121.1 billion in 2026, up 6.8% year over year, and 56.6% of the entire global games market.
• Global mobile game downloads fell 25% year over year in the first half of 2026.

Revenue up 25 percent in trend terms while downloads collapse by a quarter is not a contradiction. It is the clearest signal yet that mobile gaming stopped being an acquisition story and became a monetization story. Newzoo’s own framing is that growth is shifting from player acquisition to monetization.

The regional detail is what should change your roadmap. Roughly 80% of 2026’s net mobile audience growth came from Central and Southern Asia, Southeast Asia, the Middle East, and Africa. Sub-Saharan Africa grew 9.4% and Central and Southern Asia 5.6%, against a 3.9% global average. China grew 0.9% and Japan declined 0.2%, the first net decline recorded for a major mobile market in the current reporting cycle.

iOS is also outgrowing Android on audience growth for the first time in a long while: 5.5% versus 3.4%, lifting iOS to 25.6% of the global mobile gaming audience. Android still adds far more devices, 76.3 million new owners against 41.6 million new iPhone owners, but the segment that actually spends money is growing faster.

Put those two reports together and the picture is clear. Fewer installs are arriving, most of them from price-sensitive emerging markets, and the money has to come from monetizing the users you already have. That is exactly the environment where rewarded engagement wins, because it monetizes existing engagement without requiring a purchase.

What you should actually do about this

Audit your mediation stack for anything on a deprecation path

Concretely, check whether you are running the legacy Google Mobile Ads SDK on Android, whether you still have ironSource Ads direct demand wired into your mediation, and which version of Ad Quality you are on. All three are in transition right now. Every one of them is a place where a deprecated integration quietly keeps costing you impressions or breaking your reporting.

Do not build your reward logic on assumed callback ordering

The 1.6.0 rewarded-ad callback fix is a small release note with a large blast radius for anyone granting rewards from an ad callback. Make your reward path idempotent and make sure the reward is granted exactly once regardless of how many callbacks arrive and in what order. If you are doing server-side reward validation, this is where that pays off.

Stop treating downloads as your primary metric

With downloads down 25% and the growth concentrated in markets where a 20 dollar IAP does not land, engagement monetization is no longer the secondary option. It is the primary one.

Check your revenue mix against the audience you actually have

If your audience is increasingly in Sub-Saharan Africa, Southeast Asia, and Central and Southern Asia, a single global eCPM assumption is wrong. Geo multipliers matter more every quarter, because the same offer pays very differently depending on where the user is. Our guide to optimizing offerwall revenue across markets covers how to apply them.

Keep your monetization stack modular

The AppLovin case is a reminder that SDK vendors in this market are competitors to each other, and that disputes between them can change what your SDK does without your involvement. Modular stacks, where you can add or swap a demand source without a rewrite, are what let you respond to exactly this kind of news in an afternoon instead of a quarter.