MPP fires your tracking pixel whether or not anyone reads the message. How the proxy works, how badly it skews your metrics, and what to measure instead.
Since iOS 15 in 2021, Apple Mail Privacy Protection has been quietly rewriting the meaning of the open rate. MPP routes remote content through Apple proxies and pre-fetches it for delivered messages, which fires tracking pixels without any human involvement. Years later, plenty of teams still run engagement scoring, sunset policies, and A/B tests on a metric that Apple partially fictionalized. This article covers what MPP actually does and how to build measurement that survives it.
What MPP actually does
When a user with MPP enabled receives mail, Apple's infrastructure downloads the message's remote content, including tracking pixels, through its proxy network. The download happens on Apple's schedule, typically shortly after delivery when the device is on power and network, regardless of whether the user ever opens the message. When the user does open it, content is served from the cache, so the sender sees no second distinguishable event.
Two separate losses follow. Opens become unreliable as a positive signal, because a pre-fetch and a real read look identical. And the metadata that pixel-based analytics used to harvest, recipient IP, geolocation, device, and open time, is replaced by an Apple proxy address and Apple's fetch timing. Adoption among Apple Mail users is effectively universal, since the feature is presented as a default-on choice during setup.
How much your numbers are skewed
The distortion scales with your audience's Apple Mail share. Consumer lists commonly see a third to half of opens coming from Apple proxies; B2B lists skew lower because Outlook and Gmail web clients dominate desk work. The direction of the error is consistent: raw open rates read higher than true engagement, and the gap is largest in exactly the segments where engagement is weakest, because MPP fires for subscribers who never glance at your mail.
That last property is what breaks sunset logic. An engagement policy that counts opens keeps disengaged Apple users in the active pool indefinitely, because their mailbox dutifully fires your pixel every send. Teams migrating off open-based sunsetting routinely discover a tranche of subscribers who have not clicked in years while registering perfect open streaks.
Identifying Apple opens in your data
MPP fetches arrive from Apple's published proxy IP ranges with a distinctive user agent. Most ESPs now flag these opens as machine or privacy opens in their event streams, and if you process raw events yourself, both signals are easy to match. Once flagged, you can compute two open metrics: raw opens for continuity with historical dashboards, and filtered opens excluding known proxy fetches.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
AppleWebKit/605.1.15 (KHTML, like Gecko)
Source IP: 17.x.x.x and Apple relay ranges (proxy, not recipient)
Timing: clustered shortly after delivery, before typical read timesFiltered opens are better, not perfect. Gmail image caching, corporate link scanners, and other prefetchers add their own noise, and a filtered open still only proves an image loaded somewhere. Treat filtered opens as an upper bound on readership and clicks as the floor.
Rebuilding your metrics around actions
Measurement that survives MPP
- 1
Split opens by source
Separate Apple-proxy opens from the rest in every report. Trends in the non-Apple segment remain a usable readership proxy.
- 2
Redefine engagement on clicks and conversions
Sunset windows, reactivation triggers, and segment health move to clicked-or-converted definitions, with window lengths extended to compensate for lower click frequency.
- 3
Judge subject lines by downstream effect
A/B tests keyed on opens are contaminated at the rate of your Apple share. Test to clicks or conversions, accepting larger required sample sizes.
- 4
Watch per-provider engagement for deliverability
Placement diagnosis relies on engagement trends by mailbox provider. Use clicks there too, and remember Gmail's own models never needed your pixel.
- 5
Keep raw opens for one job only
Raw opens still detect catastrophic placement failure: if even machine opens collapse, your mail stopped arriving. As a smoke alarm, the corrupted metric retains value.
The deliverability angle
MPP changes your measurement, not Apple's filtering. iCloud's own spam decisions rest on authentication, reputation, and signals Apple observes directly, none of which involve your pixel. The deliverability risk from MPP is indirect: senders who keep mailing pixel-validated ghosts degrade their real engagement rates at every provider, and senders who cannot see a placement problem behind inflated opens respond to incidents late. Both are measurement failures with reputation consequences.
Frequently Asked Questions
Can I detect a real open from an MPP user at all?
Do other providers do this too?
Should I stop using open tracking entirely?
How should I set sunset windows without opens?
MPP removed a convenient fiction more than it removed a metric: opens always overstated attention, and Apple merely made the overstatement impossible to ignore. Move your decisions to actions recipients take deliberately, and your measurement gets more honest than it was before 2021.
Key Takeaways
- MPP pre-fetches images through Apple proxies, registering opens for messages nobody read
- The proxy also strips IP-based location and device data from all Apple Mail opens
- Apple Mail's share of opens makes raw open rates structurally inflated for consumer lists
- Apple opens are identifiable by proxy IP ranges and user agent, and should be segmented in analytics
- Clicks, conversions, and per-provider engagement replace opens as decision metrics; sunset logic on raw opens mails dead weight for years
Related articles
2025 in Email: The Year Authentication Became Mandatory Everywhere
Microsoft joined the mandate, Gmail moved to hard rejection, and DMARCbis reached the finish line. What 2025 changed for senders and what it sets up for 2026.
Q4 Peak Sending: Ramping Volume Without Triggering Filters
Between Black Friday and year end, send volumes triple while filters tighten. How to ramp into peak season so November's volume looks like growth, not an incident.
Email Validation Services: What They Can and Cannot Do
Validation APIs verify syntax, domains, and mailbox existence. Where each check works, where catch-alls and traps defeat them, and where validation belongs in your stack.