For the past decade, mobile apps have been able to rely on Apple’s Identifier for Advertiser (IDFA) to track users across other companies' apps and websites for targeting and advertising purposes.
Apple is changing the information required to submit new apps and app updates to the app store effective December 8, 2020. The new submission process will give users transparency about app data usage via a new privacy details section of an app’s product page in the app store. This “nutrition label” will also include data used by third-party partners integrated into an app.
We are excited to announce a set of solutions to help publishers manage and understand the Conversion Value they set in order to measure post-install campaign performance. A new Flurry Analytics SDK will be available later this month to support this developer need ahead of Apple’s iOS 14 release.
Last week we explained why the release of iOS 14 will reduce publisher ad revenue and how Flurry can help reverse some of that impact. This week we focus on how iOS 14 will also impair mobile ad campaign attribution.
When Apple announced iOS 14, it outlined a new policy which requires app publishers to seek end user permission to access a user’s IDFA. While estimates on forecasted opt-in rates vary, the result is clear: the IDFA will become scarce. Among the implications for app developers, the most pressing is an expected large drop in advertising revenue. In this post, we’ll discuss how disabling the IDFA leads to a sizable drop in ad revenue.
At this year’s WWDC, Apple announced that iOS 14 will change how developers can collect and share end user data. We’re summarizing the most important changes here, and how we’re helping you prepare for iOS 14.
Using Flurry Analytics
Please note that Flurry Analytics is unaffected by these changes, and you can continue to use the service without any issues before and after iOS 14 is released.
Managing Privacy with Your End Users