Using the ATT consent status dimension

The ATT consent status dimension can be used in your Ads activity report to understand IDFA user permission status and its impact on monetization. 

When you add this dimension to your reports, you can see the IDFA user permission statuses and how they’re affecting your app:

• Authorized: The user authorized access to app-related data for tracking the user or the device under the AppTrackingTransparency (ATT) framework. 
• Denied: The user did not authorize access under the ATT framework, either in the app or in their device settings. 
• Restricted: The user or device has a restricted status. This means that ATT is disabled on the device and the user cannot enable it.
• Not determined: The app can’t determine the user’s authorization status for access to app-related data for tracking the user or the device. 
• (Not applicable): This could be due to the following:
  • You have not yet implemented the ATT framework for this app. 
  • This may be an Android user or the user is using an iOS less than 14+, or the GMA SDK is less than 7.64.

How is this dimension different from the serving restriction dimension?

It’s important to highlight that the serving restriction dimension and the ATT consent status dimension are independent of one another. The serving restriction dimension provides granular details on the restrictions on the ads served and if those restrictions lead to personalized or non-personalized ads. The ATT consent status dimension provides data on if the ATT framework was implemented, and the user’s response to ATT consent (if it was requested).

Even when ATT is declined, app consent is not requested, or app consent is not implemented (IDFA is not shared), you may still see No restrictions when using the serving restriction dimension due to other methods for personalizing ads.