iOS 14 Advanced Privacy & Tracking

Image Description
Written by Luisa Woodfine Updated over a week ago

ATT Consent Prompt:

  • Apple has introduced ATT (App Tracking Transparency) in iOS 14 and has begun enforcing ATT which requires advertisers/publishers to request user permission to access user data for tracking a user or device.
  • As for iOS advanced privacy, we have planned to take dual consent from end-users at both sides (advertiser's app and publisher's app) so that we could get {click_id}/{idfa} in postbacks which is necessary to accurately measure the conversion and reward the right publisher.
  • Dual consent basically means end-users at both sides (advertiser's app and publisher's app) should give consent to collect {click_id}/{idfa} for the tracking purpose. 
  • Advertisers will have to show ATT Prompt to the user so as to take ATT consent from the end-user
  • It's a kind of permission, for user to allow the tracking SDK to track install with user identifiers which is essential for tracking to work.
  • Make sure conversion (install/event) from SDK is fired after user have successfully given ATT (App Tracking Transparency) consent. 
  • Important: Keep Aggregated Advanced Privacy disabled in your respective tracking software otherwise your tracking provider will not send us user-level attribution data, without which tracking will not work properly.

Note: Starting with the general availability of iOS 14.5+ and ATT enforcement by Apple, advertisers use the AppsFlyer Advanced Privacy (AAP) framework to control the availability of user-level attribution data from the platform.

Disable Advanced Privacy (w.r.t appsflyer):

  1. Advanced Privacy mode is likely to be on by default, but you can turn off this by the app in the "App Settings".

    Screenshot_2021-04-26_at_17.39.06.png
  2. Look for "Aggregated Advanced Privacy" and disable it.
    Screenshot_2021-04-26_at_17.39.38.png
    Note: If the AAP toggle is switched on in the app settings, then the AAP toggle will be locked in the "On" position for the partner (CPIDroid). This is the reason that you may be unable to disable the same. In this case, you would have to disable it, you can head over to your App Settings and toggle the functionality, post which you can toggle it on an individual partner level (CPIDroid). 

Regarding SKAdNetwork:

SKAdNetwork does not make sense for CPI / CPA campaigns because just tracking conversion is not enough for CPI / CPA campaigns to work properly, the eco-system can't just work without tracking {click_id}, if we don't get {click_id} in postback, we never know which publisher (or user) have delivered (or completed) the conversion (or offer) and hence we can't payout (or reward) the right publisher (or user).

Was this article helpful?

0 out of 0 found this helpful

Related articles