Newsletter read-receipt pixels: what they track and what they miss

Newsletter, September 4, 1970, Number 2; Minneapolis Public Schools Newsletter - DPLA - 7b921ca8c86f803aee24d3546e1a411b (page 1).jpg

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

Newsletter read-receipt pixels: what they track and what they miss
Photo: Unknown via Wikimedia Commons (Public domain)

Every newsletter platform embeds a tracking pixel in your emails. It’s a one-by-one transparent image, loaded from the platform’s server when a recipient’s email client renders the message. The request tells the platform which subscriber opened which email, when, and roughly where.

But tracking pixels only measure image loads. They don’t measure reading time, scroll depth, or whether the subscriber actually looked at your content. They report technical events, not human attention—and the difference matters when you’re deciding what to write next or which subscribers to segment.

What the pixel actually records

When a subscriber’s email client requests the tracking pixel, your platform logs:

  • Subscriber identifier: usually a hashed token in the image URL that maps back to the contact record
  • Timestamp: server time of the request, sometimes multiple if the email is re-opened
  • IP address and user agent: used to infer location, device type, and email client
  • Referrer header: occasionally present, mostly stripped by modern clients

The platform translates these signals into open rate, device breakdown, and geographic distribution. But it can’t tell whether the subscriber skimmed the first sentence and closed the tab, or read every word twice.

More importantly: many email clients now block or proxy tracking pixels. Apple Mail Privacy Protection, introduced in 2021 and now nearly universal among iOS users, prefetches images through relay servers. The pixel fires when Apple’s server caches the email—not when the subscriber opens it. Gmail’s image proxy does something similar. The result is inflated open rates and timestamps that don’t reflect actual reading behavior.

The engagement signals you’re not seeing

Tracking pixels miss the metrics that correlate most strongly with subscriber value:

Time in message. A subscriber who spends three minutes with your email is more engaged than one who opens and closes in five seconds. Email platforms don’t measure dwell time because the pixel fires once on load—there’s no scroll listener or exit event.

Scroll depth. Did the subscriber reach your call-to-action? Did they see the PS at the bottom? The pixel can’t answer that. Web analytics tools measure scroll percentage; email can’t.

Re-reads. Some platforms count multiple opens if the pixel fires again, but most modern clients cache images aggressively. A subscriber who revisits your email three times over a week looks identical to one who opened it once.

Forwarding without opens. If a subscriber forwards your email to a colleague who reads it but never loads images, you see zero engagement. The original subscriber gets no credit for distribution, and the new reader is invisible.

What to measure instead

Clicks are a better proxy for attention than opens. A subscriber who clicks a link demonstrated intent—they moved from passive receipt to active navigation. Track click rate as your primary engagement metric, not open rate.

Link clicks also let you infer content preference. If 12% of your list clicks the tutorial link and 2% clicks the sponsor block, you know what’s working. Open rates tell you the subject line succeeded; click rates tell you the body delivered.

Reply rate is even better. A reply costs the subscriber time and thought. If you’re running a smaller list—under 5,000 subscribers—track replies per send and treat them as your North Star metric. Platforms like Beehiiv and MailerLite surface reply counts in campaign reports; use them.

For high-value subscribers, consider moving conversations off email entirely. A Slack community, a Discord server, or a lightweight forum gives you read receipts, typing indicators, and reaction counts—all the engagement signals email strips away.

When pixel data still matters

Tracking pixels aren’t useless. They’re just overweighted.

Use open data to test subject lines. Run A/B tests on small segments, measure open rate delta, and apply the winner to the rest of your list. The pixel is reliable enough for relative comparison, even if absolute numbers are inflated.

Use device and client breakdowns to guide design decisions. If 60% of your opens happen on mobile and your email renders poorly in Gmail’s mobile app, fix the template. The pixel tells you where your subscribers read, even if it doesn’t tell you whether they absorbed anything.

Use geographic data to time your sends. If most opens cluster in US Eastern morning hours, schedule accordingly. The timestamp might be proxied, but aggregate patterns smooth out the noise.

And use suppression lists built from non-openers cautiously. If a subscriber hasn’t opened in 90 days but clicks every third email, they’re engaged—the pixel just isn’t firing. Segment on clicks and replies before you prune based on opens alone.

One more thing: if you’re debugging deliverability, open rate by domain is still useful. If Gmail opens drop suddenly while Outlook and Apple Mail hold steady, you’ve likely hit a spam filter. The pixel won’t tell you why, but it’ll tell you where to investigate.

Tracking pixels measure technical events. Clicks, replies, and conversions measure attention. Optimize for the latter, and treat open rates as a rough directional signal—not ground truth.

Want more tooling deep-dives like this? Subscribe to One Two Three Send and get operator-focused breakdowns every week—no fluff, no beginner listicles, just the mechanics that matter.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

Other newsletters you might like

Local Edinburgh

Local Edinburgh is a website that is dedicated to the promotion of Edinburgh as a travel destination. Edinburgh is Scotland’s capital city renowned for its heritage culture and festivals.

Subscribe

Ireland Moments

A daily newsletter and blog celebrating Ireland — its places, culture, music, history and the stories worth sharing from the Emerald Isle.

Subscribe

Love London

A newsletter for Londoners who want to rediscover their own city. Travellers planning their first or fifth visit. Anglophiles who fell in love with London through literature, film, or a rainy afternoon on the South Bank.

Subscribe

Scottish Rugby Fans

The best Scottish rugby updates, straight to your inbox — Six Nations, the Nations Championship, Glasgow and Edinburgh. Only when there's something worth reading.

Subscribe

Newsletters via the One Two Three Send network.  ·  Want your newsletter featured here? Click here