Deliverability Case Study: "Apple Proxy"
Hendrix's "Foxy Lady" is a leering, fuzz-heavy 1967 hard-rock come-on, and the parody keeps the swagger but turns the object of desire into a number: the open rate. The sender is infatuated with a metric that looks devoted and is mostly a machine. The "Apple Proxy" is Apple Mail Privacy Protection (MPP), and the song follows the sender from seduction to disillusion to a decision to chase something real.
Here is the technical breakdown of the deliverability concepts detailed in the song:
Verse 1: The Open Faker
"You know you're a cold little open faker / ... / And you know you're a fake little stat-maker"
- The Deliverability Context: Open tracking works by embedding a tiny remote image (the tracking pixel) in each email. When the image is fetched from your server, your Email Service Provider (ESP) records an "open." MPP, launched with iOS 15 and macOS Monterey in September 2021, breaks that link. When a user enables it in the Apple Mail app (and most do, because Apple offers it at setup), Apple's proxy servers download all remote content in the background, usually soon after delivery, whether or not a human ever looks at the message. Your pixel fires and your ESP logs an open. "Cold" is accurate: no one is reading. "Faker" is fair too, because the open is real at the HTTP level and means nothing at the human level.
- The Scope: MPP applies to the Apple Mail app, whatever the account is. A Gmail or Outlook address read in Apple Mail on an iPhone is proxied, but the same address read in the Gmail app is not. Your inflated audience is "everyone who reads in Apple Mail," which for many consumer lists is a large share.
Chorus 1: "I Want to Know Who Read"
"I want to know who read, uh huh, yeah / These opens don't mean a thing, no, ha!"
- The Deliverability Context: That is the one thing MPP is designed to deny you. Because the proxy fetches the pixel for every message delivered to a protected inbox, an MPP open tells you only that the email reached an Apple Mail client. It does not tell you it was read, when it was read, or whether it was read at all. The proxy also masks the recipient's IP address, so open-based location and device data degrade to a coarse region.
- The Correction Senders Need: "Don't mean a thing" goes slightly too far. An Apple proxy open does confirm delivery to that client, which is weak evidence that the message was not rejected. It says nothing about engagement, though, and the chorus is right that it should never be read as interest.
Verse 2: Skewing the Scene
"Now I see you, heh, are skewing the scene / ... / You make me want to get up and scream"
- The Deliverability Context: The damage does not stay inside one dashboard number. Everything downstream that keys on opens is skewed:
-
Inactivity and sunset rules: an Apple Mail subscriber who hasn't read anything in a year still "opens" every send, so open-based suppression never removes them. Your "engaged" segment fills with people who are not engaged.
-
Subject-line A/B tests: picking a winner on open rate is close to random when a large share of opens in both variants are automatic.
-
Open-triggered automations: "opened but didn't click" follow-ups and send-time optimization fire on proxy behaviour, not human behaviour.
- Why It Matters for Placement: Mailbox providers do not see your ESP's open pixel data. Gmail and the others filter on their own internal signals. MPP inflates your view of engagement, not your reputation. The risk is indirect: you keep mailing people who don't want the mail, because your data says they do, and then the complaints and ignored messages that the providers can see will catch up with you.
Chorus 2 & 3: "Show What's Real" and "Track You Down"
"I've made up my mind / I'm tired of wasting all my precious time / You've got to show what's real, what's real"
"Yeah, I'm gonna track you down, haha / These opens don't prove a thing, no"
- The Resolution: "Show what's real" is the correct pivot. Measure what a proxy cannot fake: clicks, click-to-open rate (CTOR) only where opens are non-proxied, replies, conversions, and on-site activity tied to the email.
- On "Tracking You Down": Most ESPs now try to flag proxy opens, using Apple's proxy IP ranges and fetch patterns, and report them separately as "machine opens." Use that flag to exclude MPP opens from engagement logic. Don't treat it as a way to recover who actually read. Trying to fingerprint past a privacy feature the user switched on is not a deliverability tactic. It is a consent problem, and in jurisdictions where open tracking already requires consent, it compounds the problem.
The outro's
"Oh, you mess my stats" is the honest verdict: MPP didn't break email, it broke one metric. The sender who stops loving the open rate and starts measuring action gets a truer picture of the list, and a list that is actually healthier.
Is your open rate up, with clicks flat and revenue flatter? You may be in love with the Apple Proxy. Since Apple Mail Privacy Protection (MPP), a big share of reported opens are machines pre-fetching your tracking pixel. Here is how to stop letting a proxy run your program.
Know What an Open Means Now
- Proxy opens confirm delivery to the client, not reading. Treat an MPP open as "arrived in Apple Mail," nothing more.
- Split your reporting. If your Email Service Provider (ESP) labels machine or Apple proxy opens, report human opens and machine opens separately. Never show a blended open rate to leadership as a measure of interest.
- Expect drift, not a reset. As Apple Mail's share of your list changes, your blended open rate moves for reasons that have nothing to do with content. Don't chase those swings.
Rebuild Engagement on Signals a Proxy Can't Fake
- Clicks first. Click-through rate (CTR) is your primary engagement metric. Watch out for clicks generated by security scanners: they tend to hit every link in a message within seconds of delivery. If your ESP filters those bot clicks, enable it.
- Downstream actions. Replies, logins, purchases, and on-site sessions attributed with UTM parameters are the clearest evidence a human read the mail.
- Recency of real action. Define "engaged" as a click or conversion in the last 90–120 days, not an open.
Fix the Logic That Still Keys on Opens
- Sunset policies: exclude MPP opens from inactivity rules, otherwise Apple Mail subscribers who never read stay on the list forever. Suppress after 90–120 days without a non-proxy signal, after a re-engagement attempt.
- A/B tests: pick subject-line winners on clicks or conversions. Open-based winners are unreliable when a large share of each variant opens automatically.
- Automations: audit every "if opened" branch and switch it to clicks or site behaviour, or route Apple proxy opens down the "not opened" path.
Don't Try to Out-Track the Proxy
- Respect the choice. Recipients enabled MPP on purpose. Fingerprinting or other workarounds turn a measurement problem into a trust and consent problem.
- Check your consent basis. In jurisdictions where tracking pixels require consent, open tracking is already regulated territory. Leaning on it harder only increases your exposure.
Conclusion
Apple Mail Privacy Protection didn't kill email measurement. It killed one lazy metric. Senders who rebuild engagement on clicks, replies, and conversions get a more honest list, sunset policies that actually work, and fewer recipients who quietly stopped wanting the mail.
Your Post-MPP Measurement Checklist:
- Report human and machine (Apple proxy) opens separately, and stop quoting a blended open rate.
- Redefine "engaged" as a click, reply, or conversion within the last 90–120 days.
- Remove MPP opens from sunset, re-engagement, and "opened but didn't click" automation logic.
- Judge subject-line A/B tests on clicks or conversions, not opens.
- Enable bot-click filtering so security-scanner clicks don't replace proxy opens as your new fake metric.
Educational content. Email deliverability evolves rapidly. Platform rules (Gmail, Yahoo, etc.), engagement signals, and ESP behaviours change frequently, and real-world issues often involve conflicting signals, data quality problems, and failure modes that general best practices can’t anticipate. Content on this site is provided for informational purposes only and does not replace a thorough analysis by a qualified deliverability professional.
Terms of Use