AppLovin has filed a lawsuit and a parallel motion for a temporary restraining order against Unity Technologies, accusing the engine and platform operator of harvesting data through Unity's Ad Quality SDK to train its own ad serving models.

The complaint, made public this week, targets what AppLovin describes as misuse of an SDK publishers and developers integrated to measure ad quality. AppLovin alleges Unity leveraged the access to gather competitive intelligence and feed it into machine-learning systems for ad ranking, targeting and bid optimization.

For mobile studios, the case raises a structural question: how much visibility one ad-tech buyer has into the workings of a competing demand source when both rely on shared measurement tooling.

The Ad Quality SDK sits publisher-side in the ad stack. It gives developers transparency into ad-quality signals — fraud detection, brand safety and rendering. If a competing network received the underlying telemetry, AppLovin argues, it could adjust bidding in ways that disadvantage the data's originator.

AppLovin's request for emergency relief signals the company wants court intervention now, not just post-hoc damages. A granted TRO would force Unity to suspend the alleged data capture or its use in ad serving while the case proceeds. TRO hearings typically take place within days to weeks of filing.

What does the Ad Quality SDK actually do?

The SDK sits in publisher builds and reports on ad request responses, win rates, render quality and other demand-evaluation signals. It competes with measurement offerings from independent verification vendors and with in-house tooling maintained by major ad networks.

Unity introduced the SDK as a publisher-facing addition to its monetization stack, which includes Unity Ads and the LevelPlay mediation platform acquired through ironSource. The integration depth means changes to the SDK ripple quickly across live titles.

What's at stake for studios?

If AppLovin secures the restraining order, Unity would likely have to halt data collection through the SDK or modify how captured information is processed. Studios running the SDK in production would then face a technical migration:

• Swapping libraries in live builds
• Re-running integration tests across titles
• Reconciling reporting gaps that surface after the cutover

Publishers running mediation across Unity's LevelPlay and competing networks would be most exposed. Their reporting and optimization workflows depend on stable SDK output, and any forced change forces a release-cycle decision across multiple live titles.

The case also has procurement implications. Studios negotiating ad-tech contracts typically require vendors to disclose data-sharing arrangements with competing networks. An adverse finding could push publishers to demand contractual carve-outs and audit rights around measurement-SDK telemetry.

What changes for ad-tech competitors?

AppLovin's filing is the first publicly visible escalation between two of the largest players in mobile monetization, which have co-existed inside mediation stacks for years.

AppLovin operates the AppLovin exchange and the MAX mediation platform. Unity Ads, combined with ironSource following its 2022 acquisition, remains one of AppLovin's largest direct competitors in mobile supply.

A successful TRO or damages finding could materially reshape how SDK-level data flows between measurement vendors and competing demand sources. That practice has historically operated with limited contractual disclosure.

For Unity, the financial exposure hinges on the scope of any injunctive relief and whether the complaint is amended to add damages. The company has not yet issued a public response addressing the specific allegations in the filing.

What to watch next

The immediate signal is the TRO hearing date and the court's initial assessment of whether AppLovin's evidentiary submission meets the threshold for emergency relief. Studios running the SDK should also track whether Unity pauses the tool pending litigation or issues guidance requiring publisher action — either move would force rapid operational decisions across live titles.