Retargeting After iOS 14: What Still Works and How to Rebuild Your Audiences
iOS 14 didn't kill retargeting — it killed lazy retargeting that depended entirely on a browser pixel. The pixel still works on Android and desktop. What changed is that iOS users who opted out (most of them) are invisible to client-side tracking. The fix: server-side CAPI events, CRM-based custom audiences, and in-platform engagement audiences that Apple has no access to. Use all three and your retargeting reach is often better than pre-iOS 14.
- ✓CAPI server-side events are matched via hashed email and phone — they survive iOS consent blocks entirely.
- ✓CRM custom audience uploads bypass the pixel completely — your best retargeting audience and most people aren't using it.
- ✓In-platform engagement (video views, profile visits, form opens) is data Meta owns — iOS can't touch it.
- ✓Event Match Quality score in Meta Events Manager tells you how well your CAPI events are matching — below 6 means you're leaving audiences on the table.
What actually broke — and what didn't
When iOS 14.5 dropped in 2021, Meta pixel audiences shrank for most advertisers by 30–60% on iOS traffic. I saw one e-commerce client's retargeting audience drop from 180,000 to 70,000 people virtually overnight. That's real. But here's what didn't break: server-side events sent directly to Meta's API, CRM audiences uploaded from email lists, and engagement audiences built from in-app behaviour. The businesses that got hurt were the ones whose entire retargeting infrastructure was pixel-only.
The three-layer retargeting stack that works now
- Layer 1 — CAPI server-side events: fire purchase, lead, and add-to-cart events from your server with hashed email, phone, name, and postal code. Meta matches these against its user database. EMQ score above 7 means strong matching. This layer recovers the iOS-invisible conversions.
- Layer 2 — CRM custom audiences: upload your full contact list, customer list, and high-value segments directly to Meta and Google. No pixel involved. No iOS dependency. This is your highest-intent audience and most advertisers underuse it.
- Layer 3 — In-platform engagement: video viewers (25%, 50%, 95%), Instagram profile visitors, Facebook page engagers, lead form openers. Meta owns this data entirely — Apple's ATT doesn't affect it at all.
Layer by funnel stage — different offer for each
- 01Cold → Video viewers 25%+: they've shown interest but don't know you. Offer: case study or social proof.
- 02Warm → Website visitors + page engagers: they know you. Offer: primary product or service CTA.
- 03Hot → CRM leads + CAPI-matched purchasers: they've given you data. Offer: direct meeting ask, upsell, or win-back.
- 04Lapsed → Past customers 90–365 days: they bought before. Offer: new reason to return, updated product, or seasonal hook.
Every advertiser I've worked with who 'tried retargeting and it didn't work' had one problem: they built one audience, ran one ad, and called the whole strategy broken. Retargeting is a stack, not a single campaign.
Event Match Quality: the number to fix before anything else
Meta's Event Match Quality (EMQ) score measures how well your CAPI events are matching to real Meta users. Score of 8–10: excellent matching, strong retargeting audiences. Score of 4–6: partial matching, smaller audiences, weaker performance. Below 4: most events aren't matching — your retargeting is running on a fraction of actual reach. To improve: send hashed email, phone, first name, last name, city, and postal code with every CAPI event. The more identifiers, the higher the match rate.
Is browser pixel retargeting still worth running after iOS 14?
Yes — it still captures Android users (majority of global mobile), desktop users, and the small percentage of iOS users who consented. Treat it as one layer of a broader stack, not your primary infrastructure. Audiences will be smaller than 2020, but the intent signal from someone who visited your pricing page is still valuable.
How large does a retargeting audience need to be on Meta?
Meta needs at least 1,000 matched users to run ads from a custom audience. For meaningful delivery and learning, 5,000+ is better. If your pixel audience is small post-iOS 14, combine it with your CRM upload and engagement audiences to reach a workable size.
Does the iOS 14 problem affect Google Ads retargeting the same way?
Less severely. Google has more first-party signal from logged-in Chrome and Google app users, so its audience matching is more resilient to iOS opt-outs. Google's Enhanced Conversions (server-side, similar to Meta CAPI) improve match rates further. The same principle applies: use first-party data and server-side signals to reduce pixel dependency.
Want this kind of system built for your business? Let's talk — the first call is free, no pressure.