France Fines Apple Over ATT: What App Publishers Should Take From It

The decision

On March 31, 2025, France's competition authority, the Autorité de la concurrence, fined Apple €150 million for abusing a dominant position in the distribution of mobile apps on iOS and iPadOS through the way it implemented App Tracking Transparency (ATT) between April 2021 and July 2023. It is the first antitrust fine by any regulator over ATT.

The authority was careful about what it objected to. It said the objective of ATT, giving users control over tracking, is not in itself problematic. The problem was implementation, which it found neither necessary for nor proportionate to Apple's stated goal of protecting personal data. According to the authority's press release, key findings included:

• ATT's prompt did not satisfy legal consent requirements on its own, so apps also had to show their own consent screens, producing multiple pop-ups and making third-party apps excessively complex to use.
• There was an asymmetry: users had to confirm consent to tracking twice but refuse it only once, which undermined the informed consent ATT was supposed to support.
• Smaller publishers were hit hardest, because unlike vertically integrated platforms with their own first-party data, they depend heavily on third-party data collection to fund their apps.

Apple was also required to publish a summary of the decision on its website. ATT itself stays in place; nothing in the decision bans it.

Why it matters for app publishers

ATT, which arrived with iOS 14.5 in April 2021, sharply reduced access to the device advertising identifier (IDFA) on iOS, and it reshaped in-app advertising. Targeting and attribution moved toward contextual signals, aggregated measurement through Apple's SKAdNetwork and, more recently, AdAttributionKit, and first-party data. The French decision does not reverse any of that. But it does validate a point app publishers have made for years: consent flows can cost real revenue, and the design of those flows matters.

It is also a reminder that platform rules can be challenged and can change. App publishers who have built their monetization on today's rules should keep enough flexibility to adapt.

Practical steps for in-app monetization

1. Review your consent sequence

If you show both a consent management platform prompt and Apple's ATT prompt, look closely at order, wording and timing. Showing prompts at launch, before users have seen any value from the app, tends to produce lower acceptance than showing them after a natural first interaction. Explain plainly what users get in return. Make sure choices in one prompt are reflected in the other, and that your CMP's signals reach every ad partner.

2. Make contextual and app signals work harder

With or without IDFA, buyers value accurate app information: store URL, bundle ID, content category, content rating and, for gaming, genre and in-app context. Check what your SDKs and mediation platform actually pass in bid requests. Missing or generic signals depress bids on every impression.

3. Keep app-ads.txt clean

The app-ads.txt file on your developer website tells buyers which sellers are authorized to sell your app's inventory. Buyers increasingly avoid unverified supply. Audit it against your active partners, remove stale lines, and make sure the developer URL in your store listing points to the domain where the file lives.

4. Use in-app bidding, and measure it

Most mobile mediation platforms now run real-time bidding alongside or instead of legacy waterfalls, and open-source options such as Prebid Mobile support header bidding in apps. Compare partners on revenue per daily active user, not just eCPM, and check fill and latency by ad format. Latency affects user experience in apps as much as on the web.

5. Respect the player in gaming apps

Gaming is where in-app monetization is most mature and where user tolerance is most tested. Rewarded video, offered at natural break points, remains one of the formats users accept most readily. Interstitials need frequency caps and should never interrupt gameplay. Banner refresh intervals should follow platform guidance; Google Ad Manager, for example, recommends 60 seconds for time-based and event-driven refreshes in apps.

6. Build first-party value

Logged-in users, loyalty programs and in-app preferences create data you control, with consent, that does not depend on device identifiers. Where you can, use it for contextual and cohort-based packaging in direct deals rather than trying to replicate individual tracking.

A one-hour audit

1. Open your app on a fresh iOS device and record every prompt a new user sees, in order, with screenshots.
2. Pull your current app-ads.txt file and compare each line with your active demand partners.
3. Capture a sample bid request from each major partner and check that bundle ID, store URL, category and consent strings are present and correct.
4. Compare revenue per daily active user for opted-in and opted-out iOS users, and for Android, to see where the gaps are.

Most teams find at least one missing signal or stale seller line the first time they do this.

What to watch

Apple faces scrutiny of ATT in other European markets as well, and the decision adds weight to arguments that consent frameworks should not favor the platform that runs them. Any change to how ATT prompts work, especially on consent duplication, would matter directly to app revenue. Meanwhile, measurement continues to evolve, and aggregated, privacy-preserving attribution is where Apple is investing.

ATT isn't going away. The publishers who do best will be the ones whose consent flows are clear, whose signals are complete, and whose demand isn't dependent on a single identifier.

If your app monetization is managed across several SDKs and partners, a single audit of consent flow, app-ads.txt and bid request signals is usually the fastest way to find lost revenue.