Apple announced changes in iOS 14 that affect the way Facebook receives and processes conversion events. For this reason, all companies that publish mobile app ads and that perform optimization, segmentation and reporting processes related to conversion events on the website will be seen from any of their business tools. Basically, most Facebook Ads campaigns will start to underperform.

Apple will require that all apps in the App Store that require some type of tracking display a notice to iOS 14 users. This transparency policy will prohibit certain data collection and sharing processes, unless people agree to the notice in the notice. Tracking on iOS 14 devices. As users disable tracking, ad personalization and performance reporting will be limited on Facebook Ads app and web conversion events.

To respond to these changes, Facebook will begin to process pixel conversion events coming from iOS 14 devices using grouped event metering. In this way, you will protect the privacy of users and ensure the performance and circulation of the campaigns.

Facebook's Grouped Events Measurement lets you measure website events from iOS 14 devices.

Here are some steps you can take to keep delivering your campaigns and measuring their performance:

Update the Facebook SDK for iOS 14 to version 8.1 so that you can customize the ads you deliver to iOS 14 users and continue to receive reports on conversion events in the app. You can do it from the event manager, as long as you are an administrator of the app. Currently, version 8.1 of the Facebook SDK for iOS 14 supports Apple's SKAdNetwork API and allows you to measure app install announcements. If you did not install the latest version of the SDK, we recommend that you do so. Learn more about how to use the Facebook SDK, App Events API, and mobile device measurement partners to reach iOS 14 devices and measure performance.

If you plan to deliver ads for optimized conversion events that take place on your business website:

It is recommended that you verify the domain of your website to avoid future interruptions of your campaigns related to the site. Domain verification must be done on the effective top-level domain, plus one (eTLD + 1). For example, in the case of www.books.jasper.co.uk, books.jasper.co.uk and jasper.co.uk, the domain eTLD + 1 would be jasper.co.uk.

In addition, those domains that are already registered in the list of public suffixes will be admitted. In this way, companies will be able to verify their eTLD + 1 domains if the hosting domain (eTLD) is registered in the public suffix list. For example, if "kreatr.xyz" is a domain registered in the public suffix list, then an advertiser named "news" with the subdomain "news.kreatr.xyz" could verify "news.kreatr.xyz'.