Docs

iOS 27.2's Annual ATT Re-Prompt: What Changes in the EU

iOS 27.2 lets EU apps re-prompt App Tracking Transparency yearly — the opt-in and cohort tracking that assumption now breaks.

Acquisition

iOS 27.2 and iPadOS 27.2 introduce an alternative App Tracking Transparency prompt that’s mandatory, not optional, for apps distributed in Germany, France, Italy, Poland and Romania, following agreements between Apple and European competition authorities. The new prompt drops the warning-hand icon and reworks the wording, and adds an “Additional Information” text button surfacing more detail about what tracking is being requested. That’s a smaller change than it sounds — but the change sitting next to it isn’t: developers in those five markets can now re-prompt a user for ATT consent one year after their previous choice, whether they originally accepted or declined.

Every attribution pipeline built since 2021 has quietly assumed a user’s ATT choice is fixed at install and stays fixed for the life of the app. That assumption has just stopped being true for a meaningful chunk of the EU market. A user who declined tracking a year ago can now be re-prompted and accept — and a user who accepted can, on re-prompt, decline. Any cohort analysis, LTV model, or attribution join keyed on a single install-time opt-in flag will silently misclassify users the moment their consent state changes underneath it, unless the pipeline is built to treat ATT status as something that can change, not a one-time fact.

Data Points to Track

  • ATT authorization status per user, timestamped on every check, not just once at install, so a status change is visible rather than overwritten
  • Re-prompt eligibility date (one year from the last prompt) per user in the five affected markets, so re-prompt timing can be planned rather than left to whenever the app happens to check
  • Opt-in and opt-out transitions specifically, separate from the raw authorized/denied totals, since the transition rate is the new signal this change creates
  • Market segmentation (Germany, France, Italy, Poland, Romania vs. rest of EU vs. rest of world), since the annual re-prompt only applies in these five countries for now
  • Attribution and LTV model drift for users whose ATT status flips, compared against users whose status stays constant
  • App Store review or support signals referencing the new “Additional Information” text, as an early read on user sentiment toward the reworked prompt

Setup Steps

  1. Stop treating ATT status as install-time metadata — store it as a timestamped, mutable attribute on the user record, with history, not a single field.
  2. Add a scheduled re-check of ATT authorization status for users in the five affected markets, rather than only reading it opportunistically when the app happens to call the API.
  3. Tag every attribution and LTV calculation with the ATT status in effect at that moment, so a later status change doesn’t retroactively corrupt historical numbers.
  4. Build a re-prompt scheduler keyed on the one-year eligibility window, so re-prompting is a deliberate product decision rather than an accidental side effect of unrelated app updates.
  5. Segment all EU acquisition and retention reporting by these five markets versus the rest of the EU before the first re-prompt-driven status changes start appearing in the data, so the shift is visible against a clean baseline.

Actionable Insights

The number worth adding to a dashboard now, before the first re-prompts actually happen, is the opt-in-to-opt-out and opt-out-to-opt-in transition rate once it starts appearing. A meaningfully high reversal rate in either direction means the reworked prompt’s wording and “Additional Information” button are actually moving user decisions, which has direct downstream consequences for how much of your EU attribution data is measured versus modelled. Get the timestamped, mutable tracking in place before the first eligible re-prompts land in December 2026 and beyond — retrofitting historical accuracy onto a field that was only ever recorded once at install isn’t possible.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert