Mail Privacy Protection doesn't block a tracking pixel, it pre-fetches it. Apple Mail downloads every remote image in a message, tracking pixels included, through its own relay infrastructure before a recipient necessarily looks at the email. With Apple Mail now at 75.84% of tracked opens (Litmus, October 2026), "opened" has become the least trustworthy number in most senders' dashboards. This report walks through what MPP does and doesn't touch, and which numbers in MailInApp to read instead.
How Mail Privacy Protection works
Per Apple's own documentation, once a recipient enables Mail Privacy Protection (an option offered at setup since iOS 15 and macOS Monterey), all remote content in a message is routed through two separate relays operated by different parties:
- The first relay knows the recipient's real IP address, but never sees the remote content.
- The second relay fetches the remote content, but never learns the recipient's IP address.
No single party holds both pieces. For a sender, every image request, tracking pixel included, now comes from Apple's infrastructure rather than the recipient's device or network.
Why open rates go up under MPP
Masking an IP address doesn't fabricate an open. The distortion comes from when the fetch happens: Apple pre-fetches a message's images on its own schedule, whether or not the recipient ever opens the message. The pixel fires, gets logged as an open, and that open may be nothing more than a message sitting unread in a folder.
The bias runs one way: MPP can only inflate open counts, never deflate them, and by an amount unrelated to real engagement. Litmus's October 2026 data (more than 1.7 billion opens) puts Apple at 75.84% of them, so the inflation reaches most consumer lists.
Gmail's proxy is a milder version of the same idea
Gmail has run its own image caching proxy since December 2013: every remote image URL is rewritten to a googleusercontent.com address, which masks the recipient's IP address the way Apple's relays do. Gmail fetches through its proxy when the email is opened, but in MailInApp's own tests (October 2026) Gmail on the web also scanned the message seconds after it arrived, before anyone opened it. A first Gmail fetch isn't proof of an open either.
What still works: answers and clicks
MPP pre-fetches passive content, the images a message loads automatically. It has no equivalent for something a recipient chose to do: tap a link, vote in a poll, submit a form, finish a quiz, book a time or buy. Those are requests a person's own action triggered, so they carry the same weight under MPP as they did before it existed.
That is the case for interactive email as a way to measure, not just to engage. A poll vote or a quiz completion is a signal MPP cannot inflate, where an open count already can be.
What MailInApp does about it
MailInApp is built around the signals MPP leaves alone:
- One tap records an answer. Polls, ratings, RSVPs and booking times are links in every email app, so each answer is a real tap by a real person.
- Insights shows who did what. Insights lists each block's answers and clickers per person, next to opens, so you can judge a send by responses.
- Experiments decide on answers and sales. An experiment's primary metric can be response rate, unique click rate, purchase conversion or revenue per email, none of which a pre-fetch can inflate.
- Lead alerts follow behavior. Speed-to-lead alerts use an engagement score where clicks, answers, RSVPs and purchases weigh more than an open, so a pre-fetched open alone doesn't make someone a hot lead.
Practical takeaway
- Treat open rate as directional for any list with a meaningful share of Apple Mail, which, per The 2026 State of Email Client Rendering, is most consumer lists.
- Weight clicks, poll and quiz answers, form submissions and purchases more heavily than opens when judging a campaign.
- Compare open rates across time periods or segments only when their Apple Mail shares match. The inflation isn't constant, so the comparison isn't like for like.