The following use cases are not consider conversion tracking, and do not require user permission through the AppTrackingTransparency framework:
When user or device data from your app is link to third-party data solely on the user’s device and is not sent off the device in a way that can identify the user or device.
When the data broker with whom you share data uses the data solely for fraud detection, fraud prevention, or security purposes, and solely on your behalf. For example, using a data broker solely to prevent crit card fraud.
We believe users should
have the choice over the data that is being collect about them and how it’s us. Facebook can continue to track users across apps and websites as before, App Tracking Transparency in iOS 14 will just require that they ask for your permission first. pic.twitter.com/UnnAONZ61I
— Tim Cook (@tim_cook) December 17, 2020
How Will iOS 14’s New Policy Affect Facebook Ad Campaigns & Ad Sets?
In late Apr., iOS Apps that collect data for “personaliz advertising” began displaying Apple’s ATT prompt. This is an additional layer of privacy atop the current settings:
Apple’s App Tracking Transparency Prompt
was introduc by iOS 13 regarding geographic information, opt-in rates to allow sharing “with apps when they’re not in use” plummet botswana email list 167419 contact leads from 100% to below 50%.
Facebook’s statements reflect
similar projections: “In testing we’ve seen more than a 50% drop in Audience Network publisher revenue”; and, “Our studies show, without personaliz ads power by their own data, small businesses could see a cut of over 60% of website sales from ads.”
In context, it’s crucial to point out that Facebook’s figures are preliminary estimates that may mix ecommerce with SDK implications be numbers (i.e., app revenue).
Equally unknown, is how hyperbolic Facebook is being to drum up fear in a PR war to make Apple the enemy.
