Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Facebook Marketing Partners Team response for Apple's iOS14 Privacy prompt

Hi Mark,

Yesterday (April 20, 2021), Apple confirmed it will make iOS 14.5 available to all iOS users next week, and it will start requiring apps in the App Store to obtain permission through its AppTrackingTransparency framework to “track” users across apps and websites owned by third parties for advertising and measurement purposes.

With the general availability of iOS 14.5 (week of April 26), we will begin rollout of our new advertiser experiences and measurement protocols – including Apple’s SKAdNetwork API (SKAN) and Facebook’s Aggregated Event Measurement (AEM). Once the specific date of the general availability release of 14.5 is confirmed, we will establish the rollout timing of our new experiences and communicate this timing.

You and your clients can expect to see changes in our business and advertising tools, campaign set up, targeting, delivery, measurement, and reporting, following the release of iOS 14.5 and Apple’s prompt enforcement. We are sharing a summary of these changes below, as well as key resources, to support your business and to help you support your clients.

What to expect when Apple enforces its prompt with the release of iOS 14.5

  • Expect a gradual adoption: We expect people will update their devices slowly over several weeks. As a result, we do not expect an immediate noticeable impact to iOS event reporting once Apple enforces its ATT prompt.
  • iOS 14.5 devices will be opted-out by default: When a user updates to iOS 14.5 and launches the Facebook or Instagram apps, our system detects the update and automatically opts them out on that device.

What to expect when Facebook begins rollout of our new advertiser experiences and measurement protocols (SKAN and AEM)

Expect immediate changes to app campaigns:

  • App advertisers that do not support Apple's SKAdNetwork API through their business tool integration (e.g. Facebook SDK) will be unable to create Mobile App Install campaigns targeting users on iOS 14.5+ devices, and existing campaigns will stop delivering to iOS 14.5+ devices.
  • All SKAdNetwork API campaign pauses and conversion schema configuration changes will trigger a 72 hour reset period for all active iOS 14 App Event Optimization (AEO) and Value Optimization (VO) campaigns to help minimize the risk of incorrect attribution.

Expect immediate changes to reporting (app and web): The following reporting changes will go into effect on the day Apple enforces its prompt:

  • 1-day click-through opt-out data will be modeled.
  • 7-day click-through and 1-day view-through attribution settings will no longer include iOS 14.5 opted-out events.
  • Action and demographic breakdowns will be deprecated for offsite events.
  • Attribution setting default will change to 7-day click-through for newly created ad sets and web event campaigns.
  • 28-day click-through, 7-day view-through, 28-day view-through attribution settings will be fully deprecated along with the Comparing Windows feature.
  • Attribution methodology will shift from Impression Time to Conversion Time.
  • iOS 14.5+ mobile app install campaigns will use SKAN for attribution.

Expect gradual rollout to campaigns using web events: We expect Aggregated Event Measurement (AEM) to roll out over a 2-week period, though this period may be extended based on issues we encounter. This means not all advertisers will have campaign restrictions, including limits on events that are available for optimization, starting next week.

What to expect in the following weeks

Expect performance fluctuations: As we see adoption of iOS 14.5 continue to increase, we may see greater impact to delivery and reporting, resulting in performance fluctuations and increased CPAs.

  • 100% AEM rollout to campaigns using web events: Unless we need to extend the roll out period to address implementation issues we may encounter, we expect 100% of advertisers will see the new AEM experience by Day 14 (post rollout).
  • All advertisers are subject to the 8 event per domain limit for optimization in campaign creation.
  • Ad sets will be paused if they are optimizing for an event that is not configured for AEM.
  • Ads that have not selected a domain for tracking will also be paused.
  • Modification to some web event configurations, including reprioritization, will automatically pause ad sets that are impacted by the event change (the changed event and all lower priority events) for 72 hours in order to help minimize the risk of incorrect attribution.

Audience sizes may decrease: As more people upgrade to iOS 14.5, opted-out users will automatically be excluded from certain targetable audiences, which may result in decrease of audience sizes.

Partner & client resources

In this dynamic time, we expect future changes and new product iterations, and will continue to proactively communicate our guidance and help you navigate these shifts. You and your clients can always find updated resources and recommendations here https://content.facebookinc.com/n/MjY3LVBWQi05NDEAAAF8lTZTbSZmXJmhjroQz7hm9r6xdgFnJcE7ZZc15Bj5rbKLHa4hRBln3HM_QLMGImTq3XdTSzA=.

For developer-specific guidance, we recommend that your review the following:

Facebook Changelog and Developer Docs

Developer Blog posts

To learn more about the impact of Apple’s iOS 14 prompt, as well as a high level view of how we’re thinking about the future of advertising on Facebook, visit Facebook for Business https://content.facebookinc.com/n/MjY3LVBWQi05NDEAAAF8lTZTg8Q2YTkLVgqEeAHFDsOvdb_2wZRJDW1axgRw3d8-yxpTQvUd8f-NUE-q_Pdrm6gitJc=.

Thank you for your partnership as we continue to navigate these shifts together. For any additional questions or guidance, please reach out to Direct Support https://content.facebookinc.com/n/MjY3LVBWQi05NDEAAAF8lTZTg_oYaNKrWGUfpsIXQ5clt5GuLhpA7XmLYiMLIPaJv6EYy50sBNWBbNakPszxB1396RM=. Thank you, The Facebook Marketing Partners team Copyright © Facebook. All rights reserved. Facebook Inc. 1601 Willow Rd. Menlo Park, CA 94025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment