Social Rocket
A court in San Francisco has rejected AppLovin's request for a preliminary injunction against Unity's Ad Quality SDK. As a result, AppLovin does not receive immediate court protection for now against the data collection the company objects to. However, the underlying data and contract dispute has not been decided and continues.
At its core, this is a question that is becoming increasingly important for mobile advertising: what data may an ad quality control tool collect, and may such data then be used for competition, auctions, or models?
Court Rejects AppLovin's Injunction Request
AppLovin had asked for a preliminary order preventing Unity from collecting, using, or passing on certain data from ads delivered through AppLovin's MAX platform. A court in San Francisco rejected this injunction request at the beginning of October.
The decision is not a ruling on the underlying allegations. AppLovin continues to accuse Unity of using Ad Quality to collect information on ad creatives, users, and devices, ad revenue, and engagement, and possibly using such data for competing models. Unity disputes this account.
According to Digiday, a parallel arbitration proceeding is also underway. There, AppLovin asserts, among other things, breach of contract, misuse of trade secrets, and unfair competition.
Unity Rejects the Allegations
Unity describes the lawsuit as an attempt by a dominant competitor to respond to growing competitive pressure. The company says AppLovin wants to restrict features of a small free product designed to protect publishers from problematic or harmful ads.
Unity's official product page describes Ad Quality as a tool that lets app publishers see which ads their users actually receive. The tool is meant to surface problematic creatives, long ads, problematic click patterns, and the possible effects of individual ad creatives on churn or revenue.
Unity provides Ad Quality independently of the mediation platform used. This cross-platform view is part of the conflict.
AppLovin Had Already Prepared the Dispute Publicly
On 16 September, AppLovin CEO Adam Foroughi published a blog post on data standards for ad quality tools. In it, AppLovin argues that such systems should use data from other ad networks only in aggregated and de-identified form.
At the same time, AppLovin stated that for its own product Ad Review, it has removed user-view access to individual impressions. The company says Ad Review does not feed other networks' data into its own Axon model or other advertising models.
That is AppLovin's position. Unity disputes the competitor's account and points out that AppLovin itself operates a comparable ad review product.
Why the dispute matters for marketers and app publishers
For advertisers, the conflict may first look like a technical dispute between two mobile adtech providers. In fact, it touches three central questions of modern media buying: data access, model training and auction advantages.
When platforms collect information about delivered ads, prices and user reactions, that data may theoretically be valuable not only for brand safety and quality control, but also for optimisation systems. That is precisely why the separation between measurement and competition is becoming more important.
Srocket already classified this development in the article "AI in Media Buying: Why Platform Automation Needs Control". Recent US requirements against Google in the adtech market also show how strongly data access and interoperability have become competition issues.
A similar transparency problem lies behind the FTC lawsuit against Amazon's advertising auctions. For media buyers, what matters less is which provider wins the current legal dispute, but rather which rules will apply in the long term to data generated within third-party advertising and mediation systems.
What remains open after the rejection
The rejection of the interim injunction initially means that Unity does not have to restrict its Ad Quality SDK on the basis of this preliminary court measure. However, it does not decide whether AppLovin's allegations are justified on the merits.
The focus therefore shifts back to the arbitration proceedings and the wider contractual and data dispute. The case becomes relevant if it leads to concrete limits on which information a cross-platform ad quality SDK may collect and how a provider may subsequently use that data.