> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/consent-management/setup-guides/mobile-apps/ios/att-app-tracking-transparency-ios-14.5+.md).
# ATT - App Tracking Transparency (iOS 14.5+)
Since April 2021, Apple requires that your app provide a transparency popup to ask user permission for tracking, beginning with iOS 14.5 () and the [ATT framework](https://developer.apple.com/app-store/user-privacy-and-data-use/).
### When and how should you request permission from the ATT?
Before attempting to use the IDFA from an iOS device, you must first display the ATT tracking permission alert, according to Apple's guidelines. If permission is not requested or if the user declines, the IDFA will be unavailable to your app and any embedded third-party SDKs. Third-party SDKs may not function properly in this case.To really complies with both Apple and GDPR requirements, you must open the ATT popup to get user permission **as well** as open CMP popup to get user consent for GDPR purpose. ATT isn't currently compliant with the IAB TCF or with GDPR prerequisites, so it can't be utilized as the lone consent collection system and should be utilized with the Commanders Act CMP.
### Our recommended solutions
#### 1. Most accepted solution : ATT first
From customer's experiences, the **most accepted solution** by Apple is to :
1. Open the ATT popin
2. Depending of user's choice on ATT :
1. if the user choose to allow the tracking, then open the TrustCommander popin to collect the consent
2. If the user refuse the tracking in the ATT popin, the user has to be considered as optout **without** opening the TrustCommander popin
#### 2. ATT after Commanders Act Consent banner
For some customer's this solution worked also :
1. Open the Commanders Act Consent popin
2. **Whatever the consent**, open the ATT popin just after
{% hint style="info" %}
This setup offers the advantage of allowing the user to consent certain purposes whatever his choice regarding the popin ATT tracking. Neverthe less this implementation is some time refused by some Apple reviewers
{% endhint %}
To go further, here a for France customers the position of the competition authority on this subject:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.commandersact.com/features/consent-management/setup-guides/mobile-apps/ios/att-app-tracking-transparency-ios-14.5+.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.