![\"Facebook](\"https:\/\/adscook.com\/blog\/wp-content\/uploads\/2021\/09\/Facebook-iOS-14-Prompt-760x460.jpg\")
<\/figure>\n\n\n\nUsers can’t bypass or avoid the opt-in\/opt-out prompt. So now, Facebook or other apps can track the iOS users\u2019 behavior only if they opt in and express consent. This impacts apps like:
<\/p>\n\n\n\n
- Facebook<\/li>
- Pinterest<\/li>
- Amazon<\/li>
- TikTok<\/li>
- And more<\/li><\/ul>\n\n\n\n
\u201cOnly 12% of users let applications track their activity\u201d. This is the result of the first two weeks of the App Tracking Transparency reported by Flurry Analytics.<\/a>This means marketers lose access to the most users\u2019 Identifier for Advertisers (IDFA). Instead, data groups together to hide individual identities. This has a direct impact on three main things:
<\/p>\n\n\n\n- Reporting conversions:<\/strong> Some conversions are no longer counted.<\/li>
- Optimization:<\/strong> It’s more difficult to identify people likely to complete the desired action.<\/li>
- Targeting:<\/strong> Marketers can’t target or exclude iOS 14 users who opted out.<\/li><\/ol>\n\n\n\n
And this is huge for Facebook advertisers because:<\/p>\n\n\n\n
- 98%<\/a> of active Facebook users across the globe are mobile users. And 81.8%<\/a> of active Facebook users only<\/em> use their mobile devices to access FB. They use the app, not the website<\/li>
- 26%<\/a> of mobile users are Apple iOS users. They use iPhones or iPads<\/li>
- 83%<\/a> of iOS users opt-out of tracking<\/li>
- This means marketers lose close to 21% of conversion data<\/li><\/ul>\n\n\n\n
So let\u2019s get into the details about how the iOS 14 update affected Facebook advertising. Plus, explore quick fixes advertisers should make to mitigate the impact.
<\/p>\n\n\n\n1. iOS 14 and Facebook Ads: Reporting<\/strong><\/p>\n\n\n\n
- Tracking Pixel Events<\/a><\/li>
- Breakdowns<\/a><\/li>
- Reporting Delays<\/a><\/li>
- Attribution windows<\/a><\/li><\/ul>\n\n\n\n
2. iOS 14 and Facebook Ads: Optimization <\/strong><\/p>\n\n\n\n
- Optimization events<\/a><\/li><\/ul>\n\n\n\n
3. iOS 14 and Facebook Ads: Targeting <\/strong><\/p>\n\n\n\n
- Custom audiences<\/a><\/li><\/ul>\n\n\n\n
iOS 14 and Facebook Ads: Reporting<\/strong><\/h2>\n\n\n\n
Tracking Pixel events<\/strong><\/h3>\n\n\n\n
What changed: iOS 14 Users<\/strong><\/p>\n\n\n\n
You are now allowed to track up to 8 conversion events per domain as opposed to unlimited events in the past. This limitation is due to Aggregated Event Measurement, a new protocol that Facebook released as a response to Apple privacy update. The protocol aims to help advertisers still run effective campaigns while also complying to user privacy forced by Apple.
<\/p>\n\n\n\nThis means that if someone opts out of iOS 14 tracking, you can still collect some conversion data. But it\u2019s aggregated and none of the data links to an individual user\u2019s action. Instead, all the data groups together for privacy.
<\/p>\n\n\n\nFacebook initially assigns these 8 events it believes matter most to your business based on the conversion data. But advertisers also have the option to:<\/p>\n\n\n\n
- Select pixel events on their own<\/li>
- Prioritize conversion events <\/li>
- Re-prioritize once every 72 hours<\/li><\/ul>\n\n\n\n
To do this, visit the Facebook Ads Manager >> Aggregated Event Management. <\/em><\/p>\n\n\n\n
Why is this prioritization so important? If an opted-out user takes multiple actions in one conversion window, Facebook only reports the \u201ctop\u201d event. So when a user triggers more than one conversion event, you\u2019ll see the one that\u2019s highest on your priority list.
<\/p>\n\n\n\nHere\u2019s an example:
<\/p>\n\n\n\n- Susan clicks on your Facebook ad for winter boots<\/li>
- She then Adds to Cart<\/li>
- And she purchases the boots as a result<\/li><\/ul>\n\n\n\n
Because Purchase trumps Add to Cart, you will only see the top event. In this case, it\u2019d be Purchase.
<\/p>\n\n\n\nIn a different scenario, if the user doesn\u2019t purchase, Facebook will report on the next most important conversion event in the ranking list.
<\/p>\n\n\n\nKeep in mind that in this regard, all of your other events may report numbers that are lower than anticipated. This is true even if they are within your top eight. So for this reason, expect to see inaccurate or incomplete data in Events Manager reporting.
<\/p>\n\n\n\nThis of course creates a huge gap in the buyer’s journey and may disrupt your advertising strategy overall.
<\/p>\n\n\n\nPro Tip:<\/em><\/strong> If there\u2019s big timing difference between conversion events,<\/em> you might still see each event.<\/em>
<\/p>\n\n\n\nWhen it comes to opt-in iOS 14 users, all 8 events will be returned regardless of the prioritization. <\/p>\n\n\n\n
Whether or not an iOS 14 user is opted in or opted out, you can deliver optimized ads for one of your eight prioritized events.
<\/p>\n\n\n\nBut if you want to optimize your ads for a non-prioritized event, you\u2019ll have limited delivery and limited reporting. These types of ads only deliver to users who opted-in to tracking.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Facebook also estimates \u201cmissing\u201d iOS 14 web conversion events with statistical modeling. This means all the stats you would have had for iOS 14 users are now replaced with data projections.
<\/p>\n\n\n\nIf you run an iOS 14 app install campaign, you\u2019re limited to whatever data Apple\u2019s SKAdNetwork API provides. In other words, SKAdNetwork API reports aggregated campaign results to Facebook.
<\/p>\n\n\n\nThis means all data on the campaign level isn\u2019t linked to an individual. And there are limits on possible insights. But, Facebook may use statistical modeling for app installs. It’s designed to fill in these missing iOS 14 data points.
<\/p>\n\n\n\nEither way, now that fewer people opt-in to tracking, there\u2019s not as much data to report. This impacts your ability to retarget, optimize, and customize \u2014 more on this in a minute.
<\/p>\n\n\n\nWhat changed: Desktop Users \/ Non-iOS 14 Users<\/strong><\/p>\n\n\n\n
Nothing for app conversions. The iOS 14 update only impacts Apple devices with iOS 14 or later. So marketers can still access complete conversion data. But only for non-iOS 14 and traditional desktop devices. And there\u2019s an unlimited number of trackable Pixel events.
<\/p>\n\n\n\nBut the way Facebook web conversion reporting works is different. Web conversion events now report based on the time each conversion takes place. This isn’t how it worked before \u2014 which was through associated ad impressions.
<\/p>\n\n\n\nWhen it comes to app install campaigns, you can only choose the 1-day click and 1-day view option for Value or App Events. And some non-iOS 14 app install campaigns are only eligible for the 1-day click and 1-day view option, too.
<\/p>\n\n\n\nQuick reference table<\/strong><\/h4>\n\n\n\n
Type of user<\/strong><\/td> Changes in conversion reporting<\/strong><\/td><\/tr> Apple iOS 14 or later, opt-out<\/td> – Limited data is collected and aggregated
– Statistical modeling replaces real data for web conversions
– iOS 14 app installs are limited to aggregated data that Apple\u2019s SKAdNetwork API provides<\/td><\/tr>Apple iOS 14 or later, opt-in<\/td> – Limited to the top events
– Statistical modeling replaces real data for web conversions
– iOS 14 app installs are limited to aggregated data that Apple\u2019s SKAdNetwork API provides<\/td><\/tr>Desktop Users \/ Non- iOS 14<\/td> – No changes except timestamps mark when a web conversion takes place
– Only 1-day click and 1-day view is available for app installs<\/td><\/tr>App Event<\/td> – Only 1-day click and 1-day view is available for app installs<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n What you can do about it<\/strong><\/h4>\n\n\n\n
- Use Facebook\u2019s Conversion API (cAPI) to help fill some gaps in reporting. It\u2019s not the end-all-be-all solution. It doesn\u2019t restore tracking for iOS 14 opted-out users. But it helps marketers collect information through their website without using cookies<\/li>
- Explore web and ad tracking strategies that don\u2019t rely on the Facebook Pixel. Consider using UTM parameters on your site\u2019s URLs. Or invest in third-party software like Wicket Reports, Hyros, and so on<\/li>
- Clear out unused events and group similar conversion events together<\/li>
- Keep an eye out for statistical modeling. Facebook may project data based on the \u201cmissing\u201d iOS 14 users<\/li>
- Explore first-party cookie options to track web conversion events<\/li>
- Research App Tracking Transparency (ATT) rules and regulations about app install tracking. Explore compliant options that use first-party tracking solutions for new or existing apps<\/li><\/ul>\n\n\n\n
Breakdowns<\/strong><\/h3>\n\n\n\n
What changed: iOS 14 users<\/strong><\/p>\n\n\n\n
Facebook no longer provides any reporting on delivery or action breakdowns. This means marketers are in the dark when it comes to data like:
<\/p>\n\n\n\n- Age<\/li>
- Gender<\/li>
- Region<\/li>
- Ad placement<\/li>
- Device<\/li>
- And more<\/li><\/ul>\n\n\n\n
Instead, you\u2019ll only see data for eligible users (i.e. desktop non-iOS 14 users). And there’s a disclaimer stating the data excludes iOS 14 users.<\/p>\n\n\n\n
Regardless of whether an iOS 14 user opted-in or opted-out of tracking, there\u2019s no demographic data.<\/p>\n\n\n\n
Pro Tip:<\/em><\/strong> Now\u2019s the time to invest in cookies on your website that track Facebook data without leaning on the Pixel.<\/em>
<\/p>\n\n\n\nIn other words, you can\u2019t access any reporting on the delivery or action breakdowns.<\/p>\n\n\n\n
What changed: Desktop Users \/ Non-iOS 14 Users<\/strong>
<\/p>\n\n\n\nIt\u2019s business as usual since the iOS 14 update only applies to people who use an Apple mobile device. Other desktop and non-iOS 14 users are in the clear. This means you\u2019ll be able to see things like age, gender, and ad placement.
<\/p>\n\n\n\nBut there\u2019s a catch. If you want to access breakdowns, your ad sets should only target non-iOS 14 users. So if your ad set includes both iOS 14 and desktop users (or anyone who\u2019s not on iOS 14), you can\u2019t access breakdowns. But if your ad set only includes non-iOS 14 users, you\u2019re good to go.
<\/p>\n\n\n\nQuick reference table<\/strong><\/h4>\n\n\n\n
Type of user<\/strong><\/td> Changes in breakdown reporting<\/strong><\/td><\/tr> Apple iOS 14 or later, opt-in
<\/td>No delivery or action breakdowns<\/td><\/tr> Apple iOS 14 or later, opt-out<\/td> No delivery or action breakdowns<\/td><\/tr> Desktop Users \/ Non-iOS 14 <\/td> No changes as long as your ad set only targets non-iOS 14 users <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n What you can do about it<\/strong><\/h4>\n\n\n\n
- Integrate with Google Analytics or other quality analytics platforms<\/li>
- If you already use Google Analytics, make sure to keep it updated<\/li>
- If you already have server-side tracking, report with this data on demographics instead<\/li>
- Consider Facebook\u2019s Conversion API (cAPI) for server-side or back-end tracking<\/li>
- Invest in first-party data collection that\u2019s independent of the Facebook Pixel<\/li><\/ul>\n\n\n\n
Reporting delays<\/strong><\/h3>\n\n\n\n
What changed: iOS 14 users<\/strong><\/p>\n\n\n\n
Like desktop and non-iOS 14 reporting, iOS 14 data delays can last up to 3 days. And all data centers on the time of conversion, not the ad impression.
<\/p>\n\n\n\nBut, regardless of whether a user opted in or out, all the data comes from Apple’s SKAdNetwork API. This means the time conversions you see come from Apple, not Facebook.<\/p>\n\n\n\n
What changed: Desktop Users \/ Non-iOS 14<\/strong><\/p>\n\n\n\n
Facebook no longer supports real-time reporting. Instead, data report delays can last up to 3 days. Also, conversion timestamps aren\u2019t based on ad impressions. Now, reports show the time the conversion took place.
<\/p>\n\n\n\nQuick reference table<\/strong><\/h4>\n\n\n\n
Type of user<\/strong><\/td> Reporting delays<\/strong><\/td><\/tr> Apple iOS 14 or later, opt-out<\/td> – Up to 3 days
– Timestamps show the data SKAdNetwork API reports to Facebook<\/td><\/tr>Apple iOS 14 or later, opt-in<\/td> – Up to 3 days
– Timestamps show the data SKAdNetwork API reports to Facebook<\/td><\/tr>Desktop Users \/ Non- iOS 14<\/td> – Up to 3 days
– Timestamps aren\u2019t based on ad impressions
– Now timestamps mark when the conversion took place<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nWhat you can do about it<\/strong><\/h4>\n\n\n\n
- Explore integrations with Apple\u2019s SKAdNetwork API for better or faster reporting options<\/li>
- Investigate Facebook\u2019s Conversion API (cAPI) for server-side or back-end tracking solutions<\/li>
- Identify first-party players who collect information without using the Facebook Pixel<\/li><\/ul>\n\n\n\n
Attribution windows<\/strong><\/h3>\n\n\n\n
What changed: Desktop Users \/ Non-iOS 14, and iOS 14<\/strong><\/h4>\n\n\n\n
Facebook\u2019s attribution reporting changed across the board. FB merged windows on the account level and ad set level. Together they form a new ad set level attribution setting. You can find this under Optimization & Delivery.
<\/p>\n\n\n\nAll attribution windows are the same except Facebook scrapped:
<\/p>\n\n\n\n- 28-day click<\/li>
- 28-day view<\/li>
- 7-day view<\/li><\/ul>\n\n\n\n
Pro Tip:<\/em><\/strong> If you have inactive ad sets, you should still be able to see all historical data. This applies even if you used the discontinued attribution window options above.<\/em>
<\/p>\n\n\n\nHere are the windows you can still choose from:
<\/p>\n\n\n\n- 1-day click<\/li>
- 7-day click<\/li>
- 1-day click and 1-day view<\/li>
- 7-day click and 1-day view<\/li><\/ul>\n\n\n\n
Note that the 7-day click and 1-day view was the original default setting. Now, the 7-day click option is the default.
<\/p>\n\n\n\nThere are some attribution window option exceptions. But they\u2019re for app install campaigns. We\u2019ll cover this in a minute.
<\/p>\n\n\n\nQuick reference table<\/strong><\/h4>\n\n\n\n
Facebook settings<\/strong><\/td> Attribution windows<\/strong><\/td><\/tr>
What\u2019s still there<\/td>– 1-day click
– 7-day click
– 1-day click and 1-day view
– 7-day click and 1-day view <\/td><\/tr>
What\u2019s gone<\/td>– 28-day click
– 28-day view
– 7-day view <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nWhat you can do about it<\/strong><\/h4>\n\n\n\n
- Keep a close eye on data before it\u2019s cleared each week<\/li>
- Explore first-party programs to pull data points that are independent of Facebook<\/li>
- Use the Google Analytics multi-channel reporting tools for attribution<\/li>
- Explore third-party tools that pull and compare data from several data sources<\/li>
- Investigate eROAS and eCPA for better reporting<\/li><\/ul>\n\n\n\n
iOS 14 and Facebook Ads: Optimization<\/strong><\/h2>\n\n\n\n
Optimization events<\/strong>
<\/h3>\n\n\n\nWhat changed: Desktop Users \/ Non-iOS 14, and iOS 14<\/strong><\/h4>\n\n\n\n
As we already know, Facebook limits trackable events to 8 per domain. This is across the board, regardless of device ori OS. Facebook chooses these events for you. But you have the power to reprioritize each event as you see fit in the Ads Manager.
<\/p>\n\n\n\nThis means marketers have less ability to target users. And thus less ability to optimize per ad level. Here\u2019s an example:
<\/p>\n\n\n\n- You have an ad set with two separate events<\/li>
- One event is Purchase for Product A<\/li>
- The second event is Purchase for Product B<\/li><\/ul>\n\n\n\n
With the iOS 14 update, you can\u2019t optimize each event above on its own because of the new limitations. Now, you have to pick and choose because there are fewer options.
<\/p>\n\n\n\nPlus, the new attribution windows impact optimization, too. Marketers lost iOS 14 users, the 28-day click, and the 28-day view. So now there’s less information to make decisions about future ads.
<\/p>\n\n\n\nQuick reference table<\/strong><\/h4>\n\n\n\n
Type of device<\/strong><\/td> Optimization event limits<\/strong><\/td><\/tr> iOS 14 with opt-out <\/td> 8<\/td><\/tr> iOS 14 with opt-in<\/td> 8<\/td><\/tr> Desktop \/ Non-iOS 14<\/td> 8<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n What you can do about it<\/strong><\/h4>\n\n\n\n
- Track data in the Facebook Ads Manager for events you can\u2019t optimize<\/li>
- Use any data you can find in the Ads Manager to inform which events you put at the top of the list<\/li><\/ul>\n\n\n\n
iOS 14 and Facebook Ads:<\/strong> Targeting<\/strong><\/h2>\n\n\n\n
Custom audiences<\/strong><\/h3>\n\n\n\n
What changed: iOS 14 users<\/strong><\/h4>\n\n\n\n
If iOS 14 users opted-in, marketers can still retarget them through Custom Audience. This is good news for FB marketers. But the bad news is that iOS 14 users who opted-out are off-limits. The same applies to lookalike audiences that are created from custom audiences.
<\/p>\n\n\n\nThis means Custom Audience sizes drop across the board as there are fewer people to retarget. In short, all iOS users on Facebook could have been a part of your Custom Audience before. But now, all iOS 14 users who don\u2019t permit tracking aren\u2019t included. Again, there\u2019s less information to work off of. And fewer people to retarget.<\/p>\n\n\n\n
What changed: Desktop Users \/ Non-iOS 14<\/strong>
<\/p>\n\n\n\nThe Facebook Ads Manager lets marketers create Custom Audience. These are highly defined groups of people on FB who already know your business. Think past customers, app users, or website visitors. And the Custom Audience tool in FB lets you:
<\/p>\n\n\n\nRetarget audiences:<\/strong><\/p>\n\n\n\n
Connect with people who\u2019ve converted in the past.
<\/p>\n\n\n\nCreate lookalike audiences:<\/strong><\/p>\n\n\n\n
Custom audiences serve as one of the sources to create a lookalike audience, a new audience that mimics the audience you already care about.
<\/p>\n\n\n\nCustom Audience is a powerful tool. And luckily it\u2019s business as usual for marketers targeting desktop and non-iOS 14 users. There aren\u2019t any limitations on Custom Audience – nothing\u2019s new here.<\/p>\n\n\n\n
Quick reference table<\/strong><\/h4>\n\n\n\n
Type of device<\/strong><\/td> Changes in Custom Audience<\/strong><\/td><\/tr> iOS 14 with opt-in<\/td> No limits (same as usual)<\/td><\/tr> iOS 14 with opt-out<\/td> Excluded by default<\/td><\/tr> Desktop Users \/ Not iOS 14<\/td> No limits (same as usual)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n What you can do about it<\/strong><\/h4>\n\n\n\n
- Offset Custom Audience shrinkage by making your retargeting audiences bigger<\/li>
- If you collect email addresses, make use of Customer List custom audience option. Upload your email list to create a new Custom Audience<\/li>
- Target cold audiences with ads based on interest<\/li><\/ul>\n\n\n\n
Facebook Retargeting After iOS 14: How To Adjust Your Strategies<\/strong><\/a><\/pre>\n\n\n\n
Final thoughts on the Facebook and iOS 14 update<\/strong><\/h2>\n\n\n\n
There\u2019s no doubt the iOS 14 update impacts marketers and businesses. It conceals data, makes retargeting much more difficult, and limits optimization strategies. Here\u2019s what you\u2019ve learned:
<\/p>\n\n\n\n
- Custom audiences<\/a><\/li><\/ul>\n\n\n\n
- Breakdowns<\/a><\/li>
- 26%<\/a> of mobile users are Apple iOS users. They use iPhones or iPads<\/li>
- Optimization:<\/strong> It’s more difficult to identify people likely to complete the desired action.<\/li>
- Reporting conversions:<\/strong> Some conversions are no longer counted.<\/li>