Apple MPP and Gmail: what they mean for newsletter ad tracking
Apple Mail Privacy Protection (MPP), launched in iOS 15 and macOS Monterey in September 2021, changed email marketing measurement permanently. Gmail's image proxy caching creates similar challenges. Newsletter publishers using open-time ad serving need to understand how MailAdx handles both.
What Apple MPP does
MPP prefetches all remote content in emails — including ad images — on Apple's servers before delivering the email to the subscriber. This inflates open-based metrics and masks the subscriber's real IP address. For newsletters with high Apple Mail usage (typically 40–60% of B2B subscribers), measured open rates are directional signals rather than exact counts.
What Gmail does differently
Gmail routes email images through Google's proxy servers and caches them aggressively. Without special handling, a cached ad image would serve the same creative on every re-open. MailAdx uses a nonce-based bypass: the first fetch redirects to itself with a fresh random parameter, ensuring each genuine re-open triggers a new auction.
How MailAdx handles both
MailAdx is built for open-time serving with honest measurement. Apple MPP prefetch requests are detected via user agent and labeled "AppleMPP" in delivery reports — so you can filter them from genuine human opens. Gmail nonce bypass ensures fresh auctions on re-open despite proxy caching. Impressions reflect real ad delivery events, not ambiguous send-level counts.
Adapting your measurement approach
Combine open-time impression data with click-based and conversion-based measurement. Clicks through MailAdx redirect URLs are not subject to MPP inflation. Conversion tracking via UTM parameters or server-side webhooks is also unaffected. Set advertiser expectations around click and conversion performance alongside open-time impressions.
Conclusion
Apple MPP and Gmail proxying are permanent features of the email landscape. MailAdx's open-time architecture handles both with labeled reporting and Gmail nonce bypass. Read the full tracking documentation for implementation details.
