Originally published on AppRanker.
App Tracking Transparency in the EU gets a new prompt with iOS 27.2, and in five countries your app will show it whether you change a line of code or not. If you run ads, use an attribution SDK or share data with ad networks, here is what the sheet looks like, the new API and Info.plist key, and a test plan you can run on real devices.
Who sees the new sheet
Apple announced on September 16, 2026 that, starting with iOS and iPadOS 27.2, apps can use an alternative ATT prompt for people in the European Union. The change follows commitments Apple made to competition authorities; Germany's Bundeskartellamt made them binding on August 17, 2026.
The new behaviour only kicks in when both conditions hold: the device is located in an EU country, and it is signed in to an Apple Account whose country or region is in the EU. After that, it depends on the country:
| Region | What your user gets |
|---|---|
| Germany, France, Italy, Poland, Romania | The full-page sheet, always. Even the old requestTrackingAuthorization(completionHandler:) call shows it. |
| Other EU countries | The full-page sheet only if you pass preferExpandedInterface: true; otherwise the old alert. |
| Outside the EU | The classic alert with NSUserTrackingUsageDescription. The new parameters are ignored. |
The practical risk is in that first row. Do nothing, and users in those five countries see your one-line purpose string stretched across a sheet built for a real explanation.
What the sheet adds:
- A full-page layout instead of a small alert.
- Markdown text (bold, italic, bullets, paragraph breaks; no underline) from a new optional key,
NSUserTrackingMarkdownUsageDescription. - An optional Additional Information button that closes the sheet without recording an answer and runs your own closure.
- New wording: in the EU, the Settings switch becomes "Allow Apps to Request to Link Your Activity Across Companies", and Apple's example sheet reportedly labels the buttons Allow and Reject.
The 4 code changes
1. Add the Markdown key, keep the old one. NSUserTrackingUsageDescription is still required; it is what everyone outside the EU sees. Put the Markdown version beside it. You don't need the app name in the text, since the system already shows it. The regulator's ceiling is 4,000 characters, but Apple asks for "short and specific", and that is the better target.
<key>NSUserTrackingUsageDescription</key>
<string>Lets us see which ads bring new users in and show ads that match your interests.</string>
<key>NSUserTrackingMarkdownUsageDescription</key>
<string>Ads keep this app **free**.
Allowing this lets us:
- see which campaigns brought you here
- show ads that suit you better
Pick **Reject** and nothing in the app changes.</string>
2. Call the new method behind two guards. The new API exists on iOS, iPadOS and Mac Catalyst 27.2 only, not macOS, tvOS, watchOS or visionOS. Shared code needs a platform check as well as an availability check, with the old call as the fallback.
import AppTrackingTransparency
enum TrackingConsent {
/// The single entry point for every ATT request in the app.
@MainActor
static func ask(onMoreInfo: (() -> Void)? = nil) async -> ATTrackingManager.AuthorizationStatus {
#if os(iOS)
if #available(iOS 27.2, *) {
return await ATTrackingManager.requestTrackingAuthorization(
preferExpandedInterface: true,
additionalInformationAction: onMoreInfo // nil hides the button
)
}
#endif
return await ATTrackingManager.requestTrackingAuthorization()
}
}
3. Treat .notDetermined as "not answered yet". A tap on Additional Information still fires the completion handler, with .notDetermined. Show your screen, then call ask again when the user is done. One exception from Apple: if your own consent screen already let the person opt out of everything the ATT prompt covers, don't follow up with the ATT prompt.
4. Ask from one place, once the app is active. The system skips the prompt and returns at once when tracking is restricted, the Settings switch is off, another request is pending, the call comes from an extension, or the app isn't active. The pending-request case is the sneaky one: if an ad SDK and your onboarding both ask, the second caller can get .notDetermined immediately. Route everything through one function and call it after your first screen appears, not at launch.
The yearly re-prompt is handled for you
In the EU, the system stores the date of each answer and allows a new prompt one year later, whether the person allowed or rejected, unless they turned off the Settings switch. Outside the EU the stored answer still stands forever.
You don't need to store dates or run timers. Call ask at your usual moment and the system either shows the sheet or returns the saved status. What you do control is the moment: a year in, the prompt reaches an existing user, so tie it to a meaningful action rather than app launch.
What stays exactly the same
- When you must ask: linking app data with other companies' data for ads or measurement, or sharing it with a data broker.
- No gating features behind Allow and no incentives for allowing (Guideline 5.1.2(i)).
- No tracking through another identifier, such as a hashed email, without permission.
- No fingerprinting. This one matters if you are swapping attribution or deferred deep link vendors that match installs using device signals.
Test on real devices, not the simulator
The sheet needs an EU location plus an EU Apple Account, and one developer testing the betas reported that the simulator only showed the standard alert. A short matrix covers it:
- EU account in one of the five mandatory countries: confirm the forced sheet and your Markdown.
- EU account in another member state: confirm
preferExpandedInterface: trueshows the sheet. - Non-EU account: confirm the old alert and string are unchanged.
- Additional Information path: screen appears, status stays
.notDetermined, you can ask again. - Relaunch with a prompt left unanswered: make sure requests don't stack.
Then log your EU opt-in rate before and after the update. No one has published numbers for the new sheet yet, so your own data is the only data.
Key takeaways
- The new sheet is mandatory in Germany, France, Italy, Poland and Romania, and opt-in elsewhere in the EU.
- Keep
NSUserTrackingUsageDescriptionand add a shortNSUserTrackingMarkdownUsageDescription. - Wrap the new call in
#if os(iOS)and#available(iOS 27.2, *); passnilif you have no Additional Information screen. - Funnel every request through one function, called while the app is active.
- EU users can be asked again a year after their last answer; the system tracks the timing.
The original post covers the regulatory background and how the change affects ad measurement in its full guide to the iOS 27.2 App Tracking Transparency prompt in the EU. If you are planning promotion that doesn't depend on user-level tracking, AppRanker's app leaderboard counts click-throughs to your store page with no tracking prompt involved.
Have you tried the expanded ATT sheet on an EU test device yet, and did your opt-in rate move?
Top comments (0)