iOS 14.5+ Privacy Changes · Impact on Meta Advertising

Apple's App Tracking Transparency (ATT) framework, implemented with iOS 14.5 in April 2021, requires apps to explicitly request permission before tracking users across other apps and websites using Apple's IDFA (Identifier for Advertisers). When a user opens Facebook or Instagram on an iPhone after the update, they see a prompt asking whether to allow the app to track their activity across other companies' apps and websites.

The majority of iOS users — Meta estimated approximately 62% in the months following rollout — chose to deny this permission. This had several cascading effects on Meta advertising:

• Pixel tracking reduced. The Meta Pixel fires on websites after a user clicks a Facebook ad, but if that user is on iOS and opted out, Meta cannot record the click-to-conversion journey. Conversion events from opted-out iOS users are not attributed back to the ad that drove them.
• Remarketing audiences shrank. Website Custom Audiences built from pixel data lost a significant proportion of iOS users. A product page audience that previously contained 100,000 users might contain 60,000–70,000 post-ATT.
• Attribution windows shortened. Meta reduced default attribution windows from 28-day click / 1-day view to 7-day click / 1-day view for iOS users, further reducing reported conversions.
• Lookalike accuracy reduced. Lookalikes built from audiences with significant iOS populations became less accurate as the pixel data representing those users became incomplete.

Signal loss refers to the reduction in conversion data that Meta receives for optimisation and attribution. Practical manifestations advertisers observed post-ATT:

• Reported conversions dropped. Campaigns that previously showed 100 purchases per day now showed 60–70 — not because fewer purchases occurred, but because Meta could no longer attribute them all. Platform-reported ROAS fell even when actual business performance remained stable.
• CPM and CPA increased. With less conversion data, Meta's bidding algorithms had less signal to optimise delivery — resulting in less efficient auction wins and higher costs per result.
• Learning phase extended. Ad sets that previously exited the learning phase in 7 days now took longer, as the 50 optimisation events threshold was harder to reach with incomplete attribution.
• Audience targeting degraded. Retargeting audiences based on pixel activity became less complete and less fresh, reducing retargeting campaign performance.

Meta introduced Aggregated Event Measurement (AEM) as its privacy-compliant measurement framework for iOS 14+ users. AEM restricts each website domain to a maximum of 8 conversion events that can be used for campaign optimisation and measurement. These 8 events must be prioritised in Events Manager — the priority order determines which events are attributed when a user completes multiple events in one session.

Setting up AEM — domain verification and event prioritisation

1. Verify your domain in Meta Business Manager. Under Business Settings → Brand Safety → Domains → Add. Verification confirms Meta that you own the domain and can configure its AEM settings. Required before events can be prioritised.
2. Prioritise your 8 events. In Events Manager → Aggregated Event Measurement → Configure Web Events. Rank your conversion events by business importance — Purchase first, then Add to Cart, then Initiate Checkout, etc. Higher-priority events are attributed to ads when multiple events fire in one session.

Why event prioritisation matters

A user who views a product, adds to cart, initiates checkout, and completes a purchase in one session has triggered 4 events. Under AEM, only the highest-priority event fires back to Meta. If Purchase is priority 1, only the Purchase is attributed — lower-priority events from that session are not reported for optimisation purposes.

The Conversions API (CAPI) is Meta's server-side event tracking solution — an alternative to the browser-based pixel that bypasses the tracking restrictions imposed by ATT, ad blockers, and browser cookie limitations. Rather than firing events from the user's browser (where they can be blocked), CAPI sends event data directly from your server to Meta's API.

When a user completes a purchase, your server sends the purchase event and relevant parameters (order value, product IDs, customer email hash) directly to Meta — not through the user's device. Meta can then attribute this event to the ad click even if the user's iOS settings block browser tracking.

Deduplication — critical with CAPI + Pixel

Most advertisers run CAPI alongside the browser pixel (not as a replacement) for maximum redundancy. This means Meta may receive the same event from both the pixel (browser) and CAPI (server). To prevent double-counting, both the pixel and CAPI must send a matching event_id parameter — Meta uses this to deduplicate and count the event only once.

Event Match Quality

Meta provides an Event Match Quality score in Events Manager — a 0–10 rating of how well Meta can match your CAPI events to Meta user accounts. Higher quality means better attribution and targeting. Improve Event Match Quality by including more identifiers: hashed email, hashed phone, first name, last name, city, state, zip, country, client IP address, client user agent, click ID (fbclid).

Meta uses statistical modelling to estimate conversions that cannot be directly attributed due to ATT opt-outs. When a user who opted out of tracking clicks an ad and converts, Meta's models use patterns from similar users and campaigns to estimate whether that click likely resulted in a conversion — adding this estimated conversion to reported totals.

Modelled data allows Meta to provide more complete conversion reporting than raw pixel data alone, but it introduces estimation uncertainty. Meta indicates when reported conversions include modelled data — typically a note in Ads Manager or specific column labelling. Advertisers should compare Meta-reported conversions against their own server-side records (Shopify orders, CRM leads) to calibrate the accuracy of Meta's modelled attribution for their specific account.

1. Verify your domain in Meta Business Manager. Without verification, you cannot configure AEM event priorities and Meta's attribution is compromised.
2. Implement the Conversions API. CAPI is now essential — not optional — for accurate Meta advertising measurement. Implement via direct API integration, a partner integration (Shopify, WooCommerce, Zapier), or Meta's Gateway CAPI option. Target Event Match Quality score of 7+ in Events Manager.
3. Prioritise your 8 AEM events correctly. Purchase at priority 1; work back through the funnel. Misaligned priorities cause important conversion events to be underreported.
4. Enable Advanced Matching on the pixel. Advanced Matching sends hashed customer identifiers (email, phone) from your website to Meta — improving match rates for browser-tracked events.
5. Use GA4 and first-party data for cross-verification. Do not rely solely on Meta-reported conversions. Cross-reference with GA4, Shopify analytics, or your CRM to understand the actual business impact of Meta campaigns and calibrate against the modelled data.
6. Accept longer attribution windows to capture delayed conversions. With fragmented attribution, some conversions appear later. Review 7-day and 28-day attribution comparisons in Ads Manager to understand the full conversion delay pattern for your business.

Authentic Sources