App Tracking Transparency Prompt UI in SwiftUI

App Tracking Transparency is the iOS rule that you must ask permission before tracking a user across other companies’ apps and websites. The catch is that the system prompt can only be shown once, so the difference between a good opt-in rate and a terrible one is entirely in how you set it up. VP0 is the free, AI-readable iOS design library builders start from for the primer screen that earns that yes, so the moment you spend your one prompt actually lands.

Who this is for

You are building an iOS app in SwiftUI, maybe with Cursor or Claude Code, that uses an advertising SDK or otherwise tracks users across apps, and you want to handle the ATT prompt correctly, both for App Review and for real opt-in rates. This is the pattern.

What ATT actually requires

App Tracking Transparency, covered in Apple’s App Tracking Transparency documentation, gates access to the advertising identifier and any cross-app, cross-site tracking behind an explicit user choice. You add a tracking usage description string to Info.plist, then call the request to show the system prompt. Apple’s user privacy and data use guidance is clear about what counts as tracking: linking user or device data collected in your app with data from other companies for advertising or sharing with data brokers. If you only use data inside your own app to run it, you usually do not need the prompt at all.

The primer is the whole game

Because the system prompt appears once and cannot be re-shown if denied, you precede it with your own primer: a plain SwiftUI screen that explains, in one honest sentence, what the user gets if they allow tracking. The primer is not the system dialog, so you can design it, test it, and show it at the right time. Only when the user taps your continue button do you trigger Apple’s prompt. This is the same in-context consent discipline behind a guideline 5.1.1 data collection screen, and it routinely doubles opt-in rates compared with a cold ask on launch.

Time the ask, and respect the answer

Two rules decide whether you pass review and keep users’ trust.

Decision	Do	Avoid
When to prompt	After the user sees the value	On the very first launch
The primer	Honest one-line benefit	A scary or misleading pitch
On allow	Use the identifier as described	Tracking beyond what you said
On deny	Full app still works	Nags, gates, or degraded features

Apple’s App Store Review Guidelines require the app to function whether or not the user consents, so never block content behind tracking. When the answer is no, fall back to privacy-preserving measurement, the same honest posture an HIG accessibility checker brings to compliance. Apple rejected over 375,000 app submissions in 2023 for privacy violations, so getting consent right is review survival, not just good manners.

A worked example: prompting at the right moment

Picture a free game with ads. On first launch you show nothing about tracking; you let the player finish the tutorial and one real level, so they understand the app. Before the first ad break, you present your SwiftUI primer: one line saying that allowing tracking keeps the game free and shows more relevant ads, with a single Continue button. When they tap it, you call the system request and the OS prompt appears. If they allow, you read the advertising identifier and pass it to your ad SDK as described. If they deny, you do absolutely nothing different to the gameplay; the ads simply become non-personalized, and you lean on Apple’s attribution tools to measure campaigns without tracking the individual. The player never sees a nag, never loses a feature, and you spent your single prompt at the one moment it had the best chance of a yes.

Common mistakes and fixes

• Prompting on first launch. Wait until the user understands the value.
• Skipping the primer. A primer earns far more opt-ins than a cold ask.
• Gating content on consent. The app must work fully on a deny.
• A misleading primer. Apple rejects scare or bait copy; be honest.
• Forgetting the Info.plist string. Without it the request does nothing.

Once tracking is squared away, getting your build onto a device is the next hurdle, which is exactly testing APNs notifications on the simulator.

Key takeaways

• ATT gates cross-app tracking and the advertising identifier behind one prompt.
• Show an in-context primer first; it roughly doubles opt-in rates.
• The app must work fully whether the user allows or denies.
• Use privacy-preserving measurement on a deny, from a free VP0 design.

Frequently asked questions

The FAQ above covers implementing the prompt, when to show it, what happens on a deny, and whether you need ATT without ads.