Freigeben über

iOS 14.0 FAQ(s)

  • Artikel

This document provides an FAQ in regards to the release of Apple's iOS 14.0 in relation to the Xandr iOS SDK. Specific questions on iOS 14.0 should be researched on the Apple release site.

Warning

This document is written from the perspective of Xandr Mobile SDK, other parts of our Platform were not considered when creating this FAQ. If you have a specific question about Xandr's support for SKAdNetwork/iOS14, reach out to our support team.

What is Xandr mobile SDK doing to support AppTrackingTransparency?

Xandr's support for AppTrackingTransparency comes from two distinct point-of-views, what we expect the Publisher App to do and what we are changing in the Xandr Mobile SDK.

  • As per the requirements by Apple in iOS14 and above, our expectations are that the Publisher App will
  • If publishers decide not to show the app-tracking authorization request to users, then the authorization status will either be ATTrackingManagerAuthorizationStatusNotDetermined or ATTrackingManagerAuthorizationStatusRestricted. These cases will be treated the same way as ATTrackingManagerAuthorizationStatusDenied.
  • The below table describes how the SDK will treat ATTrackingManagerAuthorizationStatus value.
ATTrackingManagerAuthorizationStatus Xandr SDK's treatment of limit_ad_tracking field in AdRequest
ATTrackingManagerAuthorizationStatusAuthorized - IDFA is supported.
- Publisher 1st party data is supported and optional iOS user ID doc publisher first party ID.
- Industry IDs are supported (Liveramp IDL, NetID, etc) and optional iOS user id doc external user ID.
ATTrackingManagerAuthorizationStatusDenied - IDFA is not supported.
- Publisher 1st party data is supported iOS user ID doc publisher ID.
- Industry IDs are not supported (Liveramp IDL, NetID, etc) iOS user ID doc external user ID.
ATTrackingManagerAuthorizationStatusNotDetermined - IDFA is not supported.
- Publisher 1st party data is supported iOS user ID doc publisher ID.
- Industry IDs are not supported (Liveramp IDL, NetID, etc) iOS user ID doc external user ID.
ATTrackingManagerAuthorizationStatusRestricted - IDFA is not supported.
- Publisher 1st party data is supported iOS user ID doc publisher ID.
- Industry IDs are not supported (Liveramp IDL, NetID, etc) iOS user ID doc external user ID.

Note

It is the responsibility of the publisher to present the authorization requests. Xandr SDKs will not perform this task.

What is happening to IDFA in iOS14?

Xandr SDK will fetch and send valid IDFA in ad request only if the authorization status is ATTrackingManagerAuthorizationStatusAuthorized.

Note

If you are concerned with a high volume of users opting out of tracking in iOS14 and above and what options Xandr will use to replace IDFA, reach out to the mobile SDK team. We will pass your concerns on to the correct team responsible for IDFA.

What happens if App's do not update to v7.6 of SDK release?

If the user is in iOS14 and the app has not updated to v7.6.2+ of the SDK, AdRequest will be sent with limit_ad_tracking:true (This is because Xandr SDK will still be using deprecated iOS13 API in this case).

What is Xandr Mobile SDK doing to support SKAdNetwork?

SKAdNetwork and related changes in iOS14 are specific for attributing app installations. Xandr Mobile SDK has traditionally relied on third parties such as Appflyer and Kochava for attributing app installs and they continue to support app install attribution in iOS14 and above. In addition to Appflyer and Kochava, we are associated with the following app install tracking vendors.

Go here (log in required) for instructions to integrate these vendors with your app and have them report back to your Xandr account.