App Tracking Transparency Just Changed in the EU: What To Do
The short answer
What changed in App Tracking Transparency in the EU with iOS 27.2?
When you have to ask users for tracking permission hasn't changed; the prompt has. On iOS 27.2, users in France, Germany, Italy, Poland and Romania always get Apple's new full-page sheet, the rest of the EU gets it only if you ask for it, and anywhere in the EU you can ask again one year after the user's answer, yes or no.
Key facts
- 5 countriesIn France, Germany, Italy, Poland and Romania, Apple's alternative prompt is the only option.Apple Developer News, Updates to App Tracking Transparency in the European Union, 16 September 2026
- iOS 27.2The new request call, with its full-page sheet and Additional Information options, works on iOS and iPadOS 27.2 and later.Apple Developer Documentation, requestTrackingAuthorization with preferExpandedInterface and additionalInformationAction
- 1 yearIn the EU you can ask again one year after the user's last answer, yes or no, unless they switched off the setting that lets apps ask.Apple, User Privacy and Data Use
- 38%Adjust's global industry average opt-in rate for early 2026, measured before this change; no opt-in data for the new prompt was published as of 28 October 2026.Adjust, Mobile App Trends 2026 (global opt-in, Q1 2026), 18 February 2026
Chapters
- 0:00App Tracking Transparency changed: the short answer
- 0:35Do you even need the ATT prompt?
- 1:13Which users get the alternative prompt?
- 2:00What do you change in your code? (Info.plist and the new request call)
- 2:40Should you add the Additional Information button?
- 3:26Can you ask again? The yearly re-ask
- 3:58What happens to your ads? (IDFA, AdAttributionKit, SKAdNetwork)
- 5:05Tallyleaf's list, in order
Transcript
Edited for readingTallyleaf is a made-up habit tracker with ads in Germany and Spain, and its story is an illustrative example, not a real account. Every rule on this page comes from Apple's developer pages and the other sources listed under Sources.
App Tracking Transparency changed: the short answerWatch from 0:00
App Tracking Transparency just changed in the EU. Here's the short answer: when you have to ask users hasn't changed. The prompt has.
In France, Germany, Italy, Poland and Romania, there's now only one option. On iOS 27.2, users always get Apple's new full-page sheet. And anywhere in the EU, you can ask again a year after they answer. Yes or no.
If you run ads to European users, this matters now. Take Tallyleaf, a made-up habit tracker with ads in Germany and Spain. Here's what it has to change, in order.
Do you even need the ATT prompt?Watch from 0:35
Step one. Do you even need the prompt?
Apple calls it tracking when you link your app's data with other companies' data, for ads or ad measurement. Sharing data with a data broker counts too.
Here's the one people miss. An ad SDK that combines your users' data with other apps' data counts. Even if you never use it for that.
Linking data only on the phone, without sending it off in a way that identifies anyone, isn't tracking.
Tallyleaf runs an ad network SDK. So yes, it needs the prompt. If you're sure your app doesn't track, you don't need it. Just check your SDK list against that rule first.
Which users get the alternative prompt?Watch from 1:13
Step two. Which of your users get the new prompt?
In those five countries, it's the only option. Users always get the full-page sheet, whatever your code asks for. Everywhere else in the EU, it's your choice: you get the sheet only if you ask for it. Outside the EU, nothing changes. People see the same small alert as before.
One catch. Apple decides by where the phone is, and which country the Apple Account is set to. Not just your App Store storefront.
Why these five? Apple points to agreements with European competition authorities. Germany made Apple's commitments binding in August. France and Italy had already fined Apple over ATT.
So for Tallyleaf, German users always get the sheet. Spanish users get it only if Tallyleaf turns it on.
What do you change in your code? (Info.plist and the new request call)Watch from 2:00
Step three. What do you change in your code?
On iOS 27.2 and later, there's a new version of the request call. It has two new options. The first one asks for the full-page sheet instead of the small alert.
The sheet also reads a new usage text from your Info.plist. It's written in Markdown, so you can use bold, italics and bullet points. Keep your old usage text too. It's still required, and the system falls back to it.
Apple's tip: keep the new text short and specific. The sheet already shows your app's name.
Our take: write it for a person, not a lawyer. And translate it for every EU language you sell in.
Should you add the Additional Information button?Watch from 2:40
Step four. Should you add the Additional Information button? That's the second new option. It puts a text button on the sheet, labelled Additional Information.
Take a guess. If someone taps it, did they say yes, or no? Neither. The sheet closes without recording an answer. Your app shows its own explanation screen. Then you ask again.
In code, that tap comes back as not determined. So don't treat it as a no.
On that screen, don't lock features or offer a reward for saying yes. Apple's guideline 5.1.2 bans both.
Tallyleaf added the button, with one plain screen and a single continue button.
Can you ask again? The yearly re-askWatch from 3:26
Step five. Can you ask again after someone says no? In the EU, yes. You can ask again one year after their last answer. That counts for a yes as well as a no.
Except when they've switched off the setting that lets apps ask at all. In the EU, Apple renamed it: Allow Apps to Request to Link Your Activity Across Companies.
Our take: Apple doesn't say the status resets after a year. So store the date of each answer yourself, and only ask once a year has passed.
Outside the EU, there's no yearly re-ask.
What happens to your ads? (IDFA, AdAttributionKit, SKAdNetwork)Watch from 3:58
Step six. What happens to your ads? Honest answer: nobody knows yet. As of 28 October, there's no published opt-in data for the new prompt.
For a baseline, Adjust put the global industry average opt-in rate at 38%, early this year. That's before this change.
What doesn't depend on the answer? Apple says AdAttributionKit and SKAdNetwork work whatever the user chooses. Apple Ads attribution runs through AdServices, Apple's own attribution framework. And Meta says its aggregated measurement covers people who opted out.
One surprise, though. Google switches off its on-device event measurement for users in the European Economic Area, the UK and Switzerland. So don't count on it there.
Our take: split your opt-in report into three groups. The five countries, the rest of the EU, and everyone else. Then you'll see the change instead of guessing.
How opt-in feeds your ad platforms is its own fix. It's in our video, Why Your Mobile App Tracking Is Wrong (And How To Fix It).
Tallyleaf's list, in orderWatch from 5:05
So here's Tallyleaf's list, in order.
Confirm it tracks. Ship the new request call, with Markdown text in every EU language. Decide on the Additional Information button. Store the date of each answer, for the yearly re-ask. Split opt-in by country. And keep the privacy-safe measurement running.
The rules on when to ask didn't change. The screen did. Rewrite yours before your first new numbers come in.
Sources
- Apple Developer News, Updates to App Tracking Transparency in the European Union (16 September 2026)
- Apple, User Privacy and Data Use
- Apple Developer Documentation, requestTrackingAuthorization with preferExpandedInterface and additionalInformationAction
- Apple Developer Documentation, NSUserTrackingMarkdownUsageDescription
- iOS & iPadOS 27.2 Release Notes
- App Review Guidelines, 5.1.2
- Apple Developer Documentation, AdAttributionKit
- Apple Developer Documentation, SKAdNetwork
- Meta for Developers, Aggregated Event Measurement
- Google Ads Help, on-device conversion measurement
- Adjust, Mobile App Trends 2026 (global opt-in, Q1 2026) (18 February 2026)
- Bundeskartellamt, Apple ATTF decision (13 August 2026)
- Autorite de la concurrence, targeted advertising fine (31 March 2025)
- AGCM, case A561 (22 December 2025)
