AppLovin asks court to block Unity's data collection in SDK dispute

AppLovin has asked the Superior Court of California in San Francisco to temporarily restrict rival Unity from collecting and using certain data generated through its mobile advertising business, escalating a legal fight between two of the sector's largest platforms.

The request, filed this week as an application for a temporary restraining order, marks a sharp turn in a dispute that is also heading to arbitration. Court filings show the two mobile ad giants have further entrenched their rivalry on legal rather than commercial ground.

At the center of the filing is Unity's Ad Quality SDK. AppLovin alleges the SDK has improperly collected data relating to advertisements served by AppLovin — including information about creatives, users and devices, impression revenue and engagement.

That data matters. Impression revenue and engagement figures are the raw material of bidding and optimization systems. If one ad platform can observe the performance of another's inventory at scale, it gains visibility into a competitor's pricing, creative strategy and user behavior signals. The allegations, if proven, would touch the core economics of mobile user acquisition.

For now, these are allegations, not findings. Unity has not publicly responded to the specific claims, and the case file (Case No. CPF26520212) contains AppLovin's application rather than a court ruling. The restraining order request — not a final judgment — is what AppLovin seeks at this stage, alongside arbitration proceedings running in parallel.

What is confirmed: AppLovin filed the application this week in San Francisco Superior Court. What remains unconfirmed: whether Unity's SDK actually collected the data in the manner described, and how Unity will defend the practice. Practitioners should treat any claim about the scope or scale of the alleged collection as unverified until the court or the parties disclose evidence.

For mobile marketers and developers, the dispute has practical implications. Many studios run both AppLovin's and Unity's monetization and mediation tools in the same apps, often alongside multiple ad networks. A restraining order against Unity's Ad Quality SDK — which developers typically embed to monitor ad quality across networks — could force studios to reassess their SDK stacks if the court grants it and the ruling survives appeal. Nothing changes yet; the SDK remains in place pending the court's decision.

The case also signals a broader shift. Data generated inside one platform's ad stack is becoming contested property, and the entities that control measurement SDKs sit close to sensitive competitive information. Ad tech vendors that operate both monetization and analytics products face growing scrutiny over where collected data travels and which internal teams can use it.

Budget implications are indirect but real. If courts restrict cross-platform data collection, ad networks lose signal that feeds bidding models, which can compress match rates and raise effective acquisition costs. Conversely, a ruling in Unity's favor would leave the current measurement architecture untouched and shift the fight back to arbitration.

The next concrete milestone is the court's decision on the temporary restraining order. Until then, both platforms continue operating as usual, and the substance of the dispute moves between a San Francisco courtroom and confidential arbitration.