Does an Email Tracking Pixel Hurt Deliverability? We Tested It
The same pitch scored 10/10 sent plain and 6.9/10 with an open pixel. What the pixel changes, why open rates lie, and why we kept tracking on anyway.
On September 8, we sent the same press pitch twice to a seed test address. Same words, same sender, same inbox, same day. The only difference was the open tracking pixel.
Without the pixel, the pitch scored 10 out of 10. With it, 6.9.
Then we kept the pixel on anyway.
Here’s what the pixel actually changed, how much of that drop was really the pixel, what the open data turned out to be worth, and why we made that call. If you’re asking whether an email tracking pixel hurts deliverability, this is the most honest answer we can give you: some, it depends on the email, and the open numbers it buys you are shakier than most dashboards admit.
How do email tracking pixels work?
A tracking pixel is a tiny image, one pixel by one pixel, with an address unique to that one email. When the recipient’s mail app loads the image, the server hosting it logs an “open,” with a time stamp.
We host our own. Every pitch that goes out with tracking on gets its own pixel address, and every load of that image lands in a log we can read.
That’s the mechanism. Here’s the side effect most people miss: turning tracking on turns a plain text email into an HTML email with an image in it. A plain pitch has words and nothing else. A tracked pitch has words plus a remote image. Spam filters see that change before any person sees the email.
Does an email tracking pixel hurt deliverability? Our seed test
A seed test is a throwaway address that scores whatever you send it. It runs the message through SpamAssassin, the open source spam filter many mail servers use, checks the sending IP against blocklists, and checks your authentication.
Here’s what came back:
| Sent plain | Sent with the pixel | |
|---|---|---|
| Score | 10 out of 10 | 6.9 out of 10 |
| Image rule | None | HTML_IMAGE_ONLY_16, about 1.05 points |
| Other HTML flags | None | HTML_MESSAGE, a remote image |
| Blocklists | Clean | A hit on Google’s relay IP |
| SPF, DKIM, DMARC | Pass | Pass |
Not all of that 3.1 point drop was the pixel. The tracked send happened to leave through one of Google’s shared relay IPs that was on a blocklist at that moment. That cost about two points on its own (SpamCop’s list inside SpamAssassin, plus a separate blocklist check). The plain send left through a different Google IP. That’s Google’s rotating address, not ours, and there’s nothing to fix.
Take the blocklist out and the pixel’s own cost is about a point: the HTML_IMAGE_ONLY_16 rule.
What HTML_IMAGE_ONLY_16 means
SpamAssassin’s rule file describes it as an HTML email with images and only 1,200 to 1,600 bytes of words.
That’s the classic shape of image spam: a picture doing the selling and a few lines of text. SpamAssassin has a whole family of these rules, from emails with almost no words up to 3,200 bytes of them. The shorter the email, the more the image looks like the point of it.
A press pitch is short on purpose. Ours was about 1,300 bytes of words, right in the middle of that band. So the pitch got scored as an image email, even though the only image in it was invisible.
Two practical takeaways:
- Length changes the math. A longer email with a pixel lands in a different band of these rules, or clears them entirely past 3,200 bytes of words.
- One rule is a nudge, not a verdict. About a point out of 10 won’t sink a well authenticated email on its own. Stack it on a blocklist hit, a cold domain or spammy wording, and it starts to matter.
Why open rates lie
Even when the pixel works perfectly, what it records isn’t a person reading your email.
Machines open first. On a client’s press round in August, 88 pitches went out with tracking on. 39 of them registered an “open” within two minutes of sending. Before that, across 255 tracked cold emails, 67 opened within two minutes, 15 of them within five seconds. Fifteen different people don’t all open a cold email within five seconds of it landing. Our read is that security scanners at the receiving companies load every image the moment a message arrives.
Apple opens everything. Apple’s privacy page says its Protect Mail Activity setting downloads remote content in the background by default, “regardless of whether you engage with the email.” Anyone using Apple Mail with that setting on registers an open whether they read a word or not.
Some real reads never show. Gmail shows images automatically by default, but its help center says that if Gmail thinks a sender or message is suspicious, images won’t load automatically. Plenty of mail apps and corporate settings block images too. Those reads never fire the pixel.
So the honest numbers looked like this. On the cold emails, the report said 57% opened. Take out the machine opens and it was closer to 31%. And a pitch that never fires tells you nothing on its own: from the sending side, there’s no telling whether it hit a spam folder, blocked images or an inbox that hasn’t gotten to it yet.
That’s the same lesson as ad dashboards: a counter isn’t a record. An open is a counter.
So why did we keep the pixel?
Because the decision wasn’t “pixel or no pixel.” It was “is a point on a seed test worth the signal?”
On the press rounds, we decided yes. Authentication was clean on both sends: SPF passed, DKIM was valid and aligned to our domain, and DMARC was in place. The pixel’s cost was a single rule. And even noisy open data says something. A pitch that never fires after a few days is worth a second look, and a real open is a decent cue for when to follow up.
What we don’t do is report the raw open rate as if it means something. We read it after taking out the machine opens, and we judge the round on replies.
When to keep tracking on, and when to send plain
Here’s how we’d make the call for any send:
Keep tracking on when:
- You’re sending a round and need to know, roughly, which sends went anywhere at all.
- Follow up timing matters, and a second open days later is a useful nudge.
- The email is long enough that the image rules barely touch it.
Send plain when:
- It’s a short, high stakes, one to one email, where every point of trust counts.
- The inbox or domain is new and still building a sending reputation.
- You’re testing deliverability itself. Then you want the cleanest possible baseline, which is exactly what our plain 10 out of 10 was.
Either way, run a seed test before a big send. We covered the rest of that checklist in email deliverability before a big send.
How to read your open data honestly
- Drop every open within two minutes of sending. Treat those as machines.
- Treat a lone open as a maybe. An open with no click and no reply could be Apple loading the image in the background.
- Don’t read “never opened” as “not interested.” It could be a spam folder, blocked images or an inbox that hasn’t gotten to it.
- Judge a send on replies and clicks. Those take a person.
- Watch for opens that don’t turn into replies. If people open and don’t answer, the problem is usually the message, not deliverability. We wrote about that in why cold email gets opened and ignored.
FAQ
Do email tracking pixels affect deliverability?
They can. The pixel turns a plain email into an HTML email with a remote image, and spam filters score that. In our seed test, the image rule cost about one point out of 10 on a short pitch. A longer email is affected less.
Are email open rates accurate?
No. Security scanners load images on arrival, Apple’s privacy setting loads them in the background, and blocked images hide real reads. In our data, a reported 57% open rate was closer to 31% once the machine opens came out.
How do I know if my email went to spam?
Open data can’t tell you. A seed test shows how filters score the message, and a pitch that never opens could be in spam or simply unread. Replies are the only proof that a person saw it.
Should cold emails be plain text or HTML?
For short one to one emails, plain text scores cleanest. Ours scored 10 out of 10 plain. If you track opens, the email becomes HTML, so check it with a seed test first.
Does Gmail block tracking pixels?
Gmail shows images automatically by default, which loads the pixel. If Gmail thinks a sender or message is suspicious, it won’t load images until the reader allows it, so the pixel doesn’t fire.
A point is a price, not a verdict
A tracking pixel costs something. On a short pitch, about a point. Whether that’s worth it depends on what you’ll do with the data, and on whether you’ll read it honestly. If you’d rather have someone run your sends and read the numbers straight, that’s what our email marketing work is built on.
Want a second set of eyes on your email setup before a big send? Book a 15-minute call and we’ll look at it with you. No deck, no fluff. Strategy first. Tactics second. The work works.
Reliable PR & Marketing is a strategy-first marketing agency in Bakersfield, California. We run integrated SEO, PR, web, and content for founder-led companies across Kern County and nationwide. Strategy first. Execution always.