Analytics and Tracking
App Tracking Transparency
Prepare iOS tracking-consent copy and URL rules for a future signed iOS implementation.
Before you start
- A clear determination that the app performs tracking under Apple policy
- Specific user-facing purpose text
- A future macOS/Xcode worker
Configure and verify
Decide whether ATT applies
Inventory cross-app or cross-company tracking behavior and SDK data use. Do not show ATT merely because an analytics SDK is present.
Write a specific purpose string
Explain why permission is requested and how data will be used. Avoid generic text.
Choose prompt timing
Use URL rules to request consent near a relevant feature, before any tracking begins.
Implement in the iOS worker
The future native iOS shell must add the usage description, call Apple ATT APIs, and ensure tracking SDKs wait for the result.
Current limitation
Consent behavior
A denial must leave core app features usable. Do not repeatedly prompt after the operating system records a choice.
Test before release
- Tracking purpose is documented
- Prompt copy is specific
- SDK startup waits for consent where required
- Denied users retain core functionality