AppLovin Sues Unity Over Alleged Mobile Ad Data Misappropriation

Full analysis

AppLovin is suing Unity, and the fight is about a piece of code that sits inside the ad auction and watches everything move through it. AppLovin says Unity's Ad Quality SDK, the little toolkit developers embed to screen out bad ads, was quietly hoovering up its creatives, users, devices, revenue per impression, and the prices auctions cleared at. Then, AppLovin claims, Unity fed all of that into models it uses to bid against AppLovin. Unity says that's nonsense, calls AppLovin a bully, and points out that AppLovin runs its own SDK, Ad Review, that it says is worse.

What's actually being decided: not who wins in a California courtroom. The real question for every mobile operator is what a third-party SDK is allowed to collect when it runs inside somebody else's auction. Hard to undo for whichever way the norm settles, easy to undo for the specific TRO, a temporary order that just freezes things while the case proceeds. The hearing was set for September 29, so the immediate procedural piece may already be decided by the time you read this. The deadline that matters is discovery, not the headline.

The Skeptic

Unity's punch back is the strong part. AppLovin runs Ad Review, the old SafeDK it acquired, and Unity says it's more intrusive. AppLovin insists Ad Review only moderates on its own MAX mediation platform. Fine, but that's a fact for discovery to settle, not a press release. If Ad Review touches non-MAX inventory, AppLovin's clean-hands story falls apart and the TRO dies. And the core claim, that Unity's models got better because of this data, is close to unprovable without cracking open Unity's model internals. Unity got resurgent after buying ironSource. Maybe the models improved because they hired better engineers. Courts are terrible at judging "your model trained on signals that correlated with our auction." This drags 18 months. In plain terms: AppLovin has to prove the burglar used its stolen tools, and the tools all look alike.

The Market Analyst

AppLovin's stock is priced for near-monopoly economics in mobile-gaming ads. You don't file for an emergency order to protect a moat you feel great about. Filing is a signal the catch-up is real. Unity's ad business was supposed to be the payoff from swallowing ironSource. A forced SDK change or an injunction sets that recovery back a full product cycle, which pressures Unity's Q4 ad-revenue estimates. The quieter winners are the neutral pipes. Any SSP or measurement vendor, think Magnite or PubMatic or DoubleVerify, that can credibly say "we watch your inventory but we don't bid against you" just got a selling point. For a general reader: the companies that only referee the auction, and never play in it, become more valuable the moment refereeing-while-playing looks dirty.

The Operator

If you're a developer or publisher with Unity's Ad Quality SDK in your stack, you audit it now, not at quarter-end. A TRO can force Unity to disable or neuter that SDK with almost no notice, and any brand-safety or ad-screening workflow hanging off it breaks the same day. DSPs and exchanges routing mobile inventory through Unity's demand should expect flaky auction participation and latency weirdness inside 30 days while Unity engineers wall off data pipes under legal supervision. And the MAX mediation managers are going to get the awkward call: "does AppLovin's Ad Review do the same thing to us?" Have the answer written before the phone rings. For a non-specialist: the plumbing everyone embedded without thinking might get shut off overnight, and nobody has a backup.

The Customer / End User

The customer here is the app developer who embedded both SDKs because everybody told them to. They never asked for a data war. They wanted more fill and higher revenue per thousand impressions, and they trusted that a screening tool screened. This case tells them the screening tool may also be a scout reporting back to a competitor in the same auction. That trust doesn't come back with a settlement. The practical result: developers start asking every SDK vendor what leaves their app and where it goes, and they start preferring vendors who can prove separation. In plain terms: the people who run the apps just learned the meter reader might also be shopping their house.

Where the council splits

Two real disagreements. First, does AppLovin have clean hands? The Skeptic says Ad Review probably guts the whole complaint in discovery. The Market Analyst doesn't care, because the filing itself already tells you the moat is under pressure regardless of who wins. Second, does any of this change the auction? The Operator and the Customer say yes, the norm around SDK data separation shifts and developers start demanding walls. The Skeptic says no, both sides pay lawyers for 18 months and the ROAS an advertiser sees on Tuesday is identical.

What it hinges on

Three things. One, whether AppLovin's Ad Review actually collects comparable data off inventory it doesn't own. That's a fact, and discovery settles it. Two, whether Unity's model gains can be traced to this specific data rather than to engineering and the ironSource advertiser base. Nearly unprovable. Three, whether developers act on the trust problem before the courts finish. The first two favor Unity or favor a long slog. The third moves without any verdict at all, and that's the one that reprices the ecosystem. Verify your own SDK data flows before you take a side, because in discovery both these companies are going to look less clean than their press statements.

The council leans toward: the lawsuit is a moat-defense move that stalls in court, but the collateral damage lands on every cross-competitive SDK in mobile, and the neutral-pipe vendors are the quiet winners.

Prediction: AppLovin and Unity will still be in active litigation or arbitration over the Ad Quality SDK data claims, with no final judgment and no settlement announced, when Unity next reports quarterly earnings in February 2027.

Confidence: High — trade-secret causation claims move slowly and both sides can fund the fight.

Why: AppLovin has to prove Unity's models improved because of its auction data, which requires opening up Unity's model internals, and courts take many quarters to work through that kind of technical trade-secret discovery. Unity has a strong counter in AppLovin's own Ad Review SDK, which gives it every reason to fight rather than fold, and neither company is cash-constrained enough to settle early to save legal fees. The opposite outcome, a fast settlement or ruling, would require one side to conclude discovery will bury them before discovery has even run, which almost never happens this early between two well-funded rivals with real strategic stakes in the answer.

Revisit by 2027-02-28: We're right if the two companies are still litigating or arbitrating the Ad Quality SDK claims with no final judgment and no announced settlement as of Unity's Q4 2026 earnings report. We're wrong if the case is dismissed, settled, or decided on the merits before then.