Why does Meta miss sales from iPhone users, and how do I get them back?
What Apple changed, and when
| When | Change | Effect on store tracking |
|---|---|---|
| 2019 | Safari caps cookies set by scripts at 7 days, 24 hours after some ad clicks | The pixel forgets returning visitors |
| Apr 2021 | App Tracking Transparency, iOS 14.5 | Facebook and Instagram apps cannot track people who say no |
| Sep 2023 | Link Tracking Protection, iOS 17 | Click IDs can be removed from links in Mail, Messages and Private Browsing |
| Sep 2025 | Fingerprinting protection for all Safari browsing, iOS 26 | Known tracking scripts lose access to some page data |
| Oct 2026 | Safari 27 blocks identity resolution services | Services that turn a typed-in email into a tracking ID are cut off |
Sources: Apple, iOS 14.5, WebKit tracking prevention, Apple, iOS 17, Apple, iOS 26, WebKit, October 2026.
Why the pixel misses iPhone purchases
The Meta pixel runs in the buyer's browser. It stores two cookies: one for the browser and one for the ad click. In Safari both are set by a script, so they fall under the 7-day limit, or 24 hours when the visit came from a tagged ad click (WebKit). Someone who clicks an ad on Monday and buys the next week can arrive as a stranger.
Add ad blockers, people who decline cookies, and app users who asked not to be tracked, and part of the purchases never reach Meta from the browser at all. Meta fills some of the gap with modeled estimates, which is one reason its numbers and your orders disagree.
How to get the missed sales back
- Send purchases server to server. On Shopify, set Meta data sharing to Enhanced or Maximum, which adds the Conversions API. See how to set up the Meta pixel on Shopify. On WooCommerce, use a plugin that sends server-side purchases with the order ID.
- Include email and phone with each purchase, so Meta can match the buyer without a cookie.
- Set the click cookie from your server. Meta recommends storing the click ID as a server cookie that lasts 90 days, which Safari's script limit does not cut (Meta for Developers).
- Avoid double counting. Browser and server purchases need the same event ID, or Meta counts the sale twice.
- Put UTM tags on every ad. Apple's link protection leaves them in place, so you can still see which ad a visitor came from.
- Count sales in your store, not only in Meta. Match each order to the ad the buyer came from.
How much browser tracking misses
We compared what GA4 recorded with the real orders in 16 stores using TrueROAS, from 5 October to 1 November 2026. The median store's GA4 saw 76% of its orders. A quarter of purchases never showed up, and every browser-based tool faces the same limits.
Meta's own count can land on either side of your orders. Across 91 stores in the same weeks, Meta reported a median 12% more sales than we could match to real orders, partly through view credit and modeled conversions. That is why the fix is two-sided: send Meta better data, and judge your ads on your own orders.
What you cannot recover
Some buyers will stay invisible to Meta: people who decline tracking and never enter an email Meta can match. No tool gets those back honestly. What you can do is know your real number of orders, so a missing slice in Meta's report does not make a good ad look bad.

