· Added · Updated

Apple’s ATT prompt is changing in 2026 (Germany’s FCO case): what to watch

Didomi summarises the Bundeskartellamt decision and Apple’s commitments to make ATT consent experiences more neutral and closer to Apple’s own. Practical takeaway: expect prompt copy/layout changes, and plan measurement baselines + consent UX work like a product update.


Original post (source): Didomi, “Apple ATT 2026 update: What does it mean for your business” (August 27, 2026)


The core idea

Didomi’s framing is straightforward: ATT is not going away, but the prompt UX is being reshaped after Germany’s Bundeskartellamt (FCO) decision.

The practical changes they highlight:

  • Apple is committing to more neutral text and formatting (less “nudge-y” design).
  • The gap between Apple’s own consent flows and third-party app prompts is expected to narrow.
  • There may be more room to combine ATT-style requests with GDPR consent collection, reducing “ask twice” friction (implementation will vary by CMP and app setup).

Why this matters for app teams

Even if you do not change anything, prompt and consent UX changes can cause:

  • opt-in rate shifts (up or down),
  • measurement baseline breaks (your attribution/ROAS trend lines jump),
  • and a bunch of internal “what changed?” churn.

Treat it like a platform change that affects growth, not like a legal footnote.

Tiny wins

  1. Write down your current ATT opt-in baseline Capture opt-in rate by country, iOS version, acquisition channel, and cohort age.

  2. Tag the day the prompt changes in your dashboards Add a permanent annotation, so future you does not spend a week “debugging” seasonality.

  3. Audit your pre-prompt and value exchange If the system prompt gets more neutral, your in-app explainer needs to do more of the work (without being manipulative).

Editor: App Store Marketing Editorial Team

Insights informed by practitioner experience and data from ConsultMyApp and APPlyzer.

Want help with ASO?

If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.