ATT nutrition label and actual tracking scope are consistent

The NSUserTrackingUsageDescription wording is a legal representation of your tracking scope that users see before deciding whether to grant ATT consent. Understating the scope — claiming 'for measurement' when the SDK also performs cross-app behavioural targeting — misleads users and violates GDPR Art.5(1)(a) (lawfulness, fairness, transparency) and CCPA §1798.100. Apple cross-checks the description against the App Store nutrition labels 'Data Used to Track You' section, and mismatches trigger rejection. Declaring SKAdNetwork-only measurement while simultaneously passing IDFA to the same ad network makes the privacy-preserving claim false.

Write a tracking description that covers every purpose: ad personalisation, cross-app measurement, attribution, and any analytics use involving the IDFA. Example:

"Your device identifier is used to show you ads relevant to your interests, measure ad effectiveness, and attribute app installs to ad campaigns."

Audit each ad SDK's actual data use against the description. If you want to simplify compliance, switch to SKAdNetwork-only mode — many ad networks support privacy-preserving attribution that does not require ATT consent at all. Verify SKAdNetworkItems in Info.plist and confirm the same networks are not also receiving IDFA directly, which would make the SKAdNetwork-only claim false.