IDFA

Henry Wang by Henry Wang | March 23, 2021

Let’s start with the basics.

iOS 14.5 introduces two big changes that will impact app marketing on iOS:

First is Apple’s App Tracking Transparency (ATT) policy, which will require apps to ask users for permission to track their IDFA. With most users expected to opt-out, this means that most bid requests will not contain IDFA. 

Second is Apple’s SKAdNetwork (SKAN), which will become the primary attribution framework for iOS 14.5 devices. With SKAdNetwork, postbacks will not contain any user level information (including IDFA), and are delayed. This means that there will be less data to track and optimize off of. 

While these changes are great for user privacy, it signals a general loss of data granularity for app marketing. Without user level data and real-time postbacks that were enjoyed previously, app marketing will change significantly when iOS 14.5 drops.

How Marketing Will Change on iOS

Targeting will shift from behavioral to contextual. Without IDFA, advertisers will need to rely on contextual signals like time of day, device model, publisher app, and general location to target users. At Liftoff, we’ve been able to use contextual signals to help advertisers like Playrix and Yubo drive continued performance without IDFA on Limited Ad Tracking (iOS traffic without IDFA).

Creatives will need to speak to a broad audience. Without IDFA, true personalization of ads is not feasible. Advertisers will need to focus their creatives to speak to a broad audience to drive installs. Product feed creatives will need to display the most popular products instead of the relevancy which relies on the user’s past behavioral data.

Re-Engagement will not be possible without IDFA. Most bid requests will not contain IDFA and SKAN postbacks will never contain IDFA. That’s a double whammy to Re-engagement which relies exclusively on IDFA to work. So when iOS 14.5 kicks in, advertisers will want to scale down their re-engagement campaigns and shift their budget to iOS UA campaigns as inventory transitions to SKAN. Advertisers can continue to run re-engagement campaigns on Android.

Same with incrementality testing. Incrementality testing relies on IDFA to measure conversions and lift. This won’t work without IDFA.

ROAS optimization will change. With SKAN, postbacks contain sparse data and are delayed. Additionally, SKAN will only send one postback per user per app that contains the install and the final conversion value (which SKAN won’t always send to protect user privacy). This means that advertisers will need to adjust their ROAS goals to account for postback delays and potential missing values, as well as find earlier events that are correlated with down funnel events to extrapolate ROAS.

Reporting will change. When iOS 14.5 drops, there will be a mix of traffic: Pre-ATT (MMP attributed), Post-ATT (SKAN attributed), and non-measurable (for more on this, check out our blog post here). MMP reporting will continue as is but SKAN reporting will be limited to geo and top source apps (due to SKAN postback limitations). Advertisers will need to understand that it’s not performance that’s suffering but measurement and that’s because of how SKAN works.