What Changed
In April 2021, Apple released iOS 14.5 with App Tracking Transparency (ATT). Since then, every app has had to ask permission before tracking a user's activity across other companies' apps and websites. If a user taps "Ask App Not to Track", the app can't use Apple's advertising identifier to follow them.
Many people decline. Reporting at the time, based on data from the analytics firm Branch, suggested only about a quarter of users who saw the prompt allowed tracking. For apps like Facebook and Instagram, that meant losing much of the visibility they had into what users did after clicking an ad.
Apple's browser has its own protections too. Safari's Intelligent Tracking Prevention limits third-party cookies and shortens the life of some tracking data, which also cuts into what traditional ad pixels can see.
How It Affects Ad Tracking
| Area | What happens | What you notice |
|---|---|---|
| Conversion reporting | Some iOS conversions can't be tied to the ad | Ads Manager shows fewer sales than your store |
| Optimization | Algorithms learn from fewer signals | Less stable delivery, slower learning |
| Retargeting audiences | Fewer users can be added | Smaller retargeting pools |
| Attribution windows | Shorter or modelled reporting | Later sales under-credited |
| Cross-device journeys | Harder to stitch together | Sales credited to "direct" or nothing |
Notice what didn't change: your sales still happen. The loss is in visibility and credit, not necessarily results. That's why some advertisers paused campaigns that were actually still working.
How the Platforms Responded
Meta leaned harder on server-side data through its Conversions API, asked advertisers to verify their domains, and introduced more modelled reporting to estimate conversions it couldn't observe directly. Google uses alternative click parameters for some iOS app traffic. Both now encourage advertisers to send first-party conversion data from their own systems.
Modelled numbers help fill gaps, but they're estimates. For budget decisions, it pays to have your own record of what actually sold.
What Still Works
- First-party tracking on your own domain. Tracking set by your own site isn't the cross-app tracking ATT restricts. See our first-party tracking guide.
- Server-side conversion sending. Events sent from your server reach the platforms even when browser pixels are blocked. See server-side tracking.
- Good customer data for matching. Hashed email and phone, sent with consent, help platforms match conversions to people.
- UTM-tagged links. They still tell your own analytics where visitors came from.
- Judging on real sales over a sensible window. Compare spend with revenue in your store or CRM, not only in Ads Manager.
How Advertisers Adapted
- Verified their domains and cleaned up eventsSo the events platforms still receive are correct.
- Added server-side deliveryThrough store integrations, gateways or tracking tools.
- Kept an independent recordA first-party tracker credits sales across every channel and device consistently.
- Fed real conversions backSo Meta and Google optimize on complete purchase data.
- Stopped judging campaigns on day oneDelayed and cross-device sales arrive later, so they evaluated over a week or more.
Where ClickMagick Fits
ClickMagick says its tracking uses first-party cookies on your own domain without redirects, so it isn't affected by iOS privacy changes or Safari's tracking prevention the way third-party pixels are. Its cross-device tracking connects phone clicks to later desktop purchases, and its Audience Optimization sends conversions back to Meta and Google. For Google Ads, ClickMagick says it sends iOS conversions using the WBRAID parameter.
The result is a consistent view of what your ads really sold, plus better data flowing back to the platforms that still have gaps.
See the sales your iOS-affected pixel has been missing.
Try ClickMagick FreeFrequently Asked Questions
What did iOS 14.5 change for advertisers?
iOS 14.5 introduced App Tracking Transparency, which requires apps to ask permission before tracking users across other companies' apps and websites. Many users decline, which limits what apps like Facebook and Instagram can track about what users do after clicking an ad.
Does App Tracking Transparency affect Google Ads too?
Yes, for iOS app traffic. Google uses alternative click parameters for some iOS traffic, and tools like ClickMagick say they send iOS conversions back to Google using the WBRAID parameter.
Can I still track iPhone users?
You can still record visits and sales on your own website with first-party tracking, and send conversions to ad platforms from your server. What's limited is cross-app tracking by apps and third-party identifiers. Respect users' choices and your consent obligations.
Is Safari's tracking prevention the same as ATT?
No. ATT applies to apps on iPhone and iPad. Safari's Intelligent Tracking Prevention limits cookies and tracking in the browser itself. Both reduce what traditional pixels can see.
What's the best response to iOS tracking limits?
Combine first-party tracking on your own domain, server-side conversion sending such as Meta's Conversions API, good customer data for matching, and judging campaigns on real sales over a sensible time window.