iOS 14.5 added App Tracking Transparency, which makes apps ask people for permission to track them across other companies' apps and websites. Many people said no, so Meta received less data on iPhone users, and advertisers saw fewer reported results and less precise reporting.
TL;DR
- Apple's App Tracking Transparency asks each person for permission to track.
- People who decline limit the data apps can share about them.
- Meta saw fewer conversions it could match to an ad, so reported results fell.
- Reporting became less precise and less immediate for affected people.
- Meta answered with new measurement and the Conversions API.
- The practical response is better first-party data, server events and a clear attribution setting.
What exactly changed?
Apple released iOS 14.5 with App Tracking Transparency. Apps, including Meta's apps, must show a prompt asking whether the person allows tracking across other apps and websites. If the person declines, the app cannot use the device's advertising identifier for that.
For advertisers, the consequence was on the measurement side. Meta relied on that identifier, along with browser data from the pixel, to match a purchase on your site to the person who saw the ad. With a decline, that match was less likely to succeed.
For the long version, see our post on Apple's iOS 14 changes.
Let Madgicx's AI do the work
Its AI marketer finds what's working and prepares the next move. You approve.
Try for Free ($0 Trial)How did it show up in advertisers' numbers?
Advertisers saw a few patterns, and they are still visible in accounts today.
| What you saw | Why |
|---|---|
| Fewer purchases in Ads Manager than before, with store sales steady | Meta could not match some purchases to ads |
| Results that arrive later or change after the fact | Reporting for affected people is delayed and modeled |
| Smaller audiences for retargeting | Fewer people were identifiable from site visits |
| A bigger gap between Meta and the store | Some conversions are hidden or credited elsewhere |
Our answer on why Ads Manager results differ from revenue shows how to measure the gap in your own account.
How did Meta respond?
Meta changed its measurement and its attribution defaults, introduced Aggregated Event Measurement for affected conversions, and promoted the Conversions API as a way to send events from your own server. Meta also leans more on modeled results where direct matching is not possible.
Details of these Meta features change over time, so check Meta's current pages before you plan around a specific limit.
What should advertisers do now?
- Send server events. The Conversions API delivers events from your server, so browser limits matter less. See server-side tracking for Meta ads for how it works.
- Send customer details. Hashed email or phone at checkout improves matching.
- Keep one attribution setting. Read results on the same window every time, so changes in the numbers mean something. See what ad attribution is.
- Compare with revenue. Use store orders as the check, and track the ratio to Meta's purchases.
- Collect first-party data. Emails, accounts and purchase history belong to you, and they hold up when browser tracking narrows.
Is the iOS 14 effect still relevant?
Yes, in two ways. The prompt is now a normal part of iPhone use, so the data limits it caused remain. And similar limits have spread to other browsers and privacy settings. Treat the change as the start of a long trend toward less browser-level data, not a one-time event. That is why server-side methods are now standard practice.
What did it not change?
It did not stop Meta ads from working. People still see ads, click and buy. It changed how much of that Meta can see and credit. Campaigns with sound creative and offers still perform. The change affects the measurement more than the market.
Where Madgicx fits
Madgicx helps with the data side of this change. Madgicx Cloud Tracking sends conversions to Meta from your server, so Meta sees and attributes more of them when a browser or device limits what it can collect. Meta's attribution rules stay in place. You decide what to run.
FAQ
What is App Tracking Transparency?
It is Apple's privacy feature that makes apps ask permission before tracking a person across other companies' apps and websites.
Did iOS 14 stop Facebook ads from working?
No, ads still run and convert. Meta can see and attribute fewer conversions, so reported results look lower.
Does iOS 14 affect Android users?
No, the rule is Apple's and applies to Apple devices. Android has its own privacy settings.
Is the Conversions API a fix for iOS 14?
It is a partial fix. It restores events that browsers hide, but it cannot override a person's choice to decline tracking.
Should I still care about iOS 14 in 2026?
Yes, because the data limits remain, and similar limits now exist elsewhere. Plan for less browser data.
Related
- Answers: Server-side tracking for Meta ads
- Answers: What is ad attribution?
- Glossary: Conversions API
Go deeper
Read the full history in our post on iOS privacy settings.
