Read Receipts vs Email Open Tracking

Both promise to tell you whether your email was read. They work in opposite ways, and they fail in opposite ways too.

Table of contents

A read receipt asks the recipient to confirm. Open tracking measures a technical event without asking anyone. That single difference decides which one you should use, and when neither is appropriate.

What a read receipt actually is

A read receipt is a request embedded in the message header. The recipient's email client sees it, and depending on its configuration, either prompts the person, sends the confirmation silently, or ignores the request entirely.

Three consequences follow from that design:

• It is visible. The recipient knows you asked. In an internal or contractual exchange that is fine. In a sales conversation it changes the tone before the first reply.
• It is optional. Declining is a normal, supported action. Many clients decline by default.
• It is binary and rare. When it works you get one confirmation. You learn nothing about a second or third read.

Read receipts also depend on the recipient's software. Zoho Mail supports them. Google Workspace supports them, gated behind an administrator setting. Personal Gmail accounts do not offer them at all.

What open tracking actually is

Open tracking adds an invisible image to the message. When the email is displayed and images load, that image is requested from a server, and the request is recorded.

The recipient is not asked and sees nothing. You get a timestamp, and if the message is opened again later, you get that too.

The trade-off is precision. An open is inferred from an image request, and image requests can happen without a human reading anything, or fail to happen even when someone reads carefully.

Side by side

• Consent: the receipt asks, the tracker does not.
• Reliability: the receipt is exact when it arrives, but it often never arrives. The tracker almost always produces data, of lower certainty.
• Repeat opens: the receipt sees one. The tracker sees each one.
• Availability: the receipt depends on the recipient's client. The tracker depends on yours.
• Perception: the receipt is transparent and can feel heavy. The tracker is discreet and can feel intrusive if you use it badly.

Which one for which situation

Use a read receipt when the confirmation itself matters: a contractual notice, a document that must be acknowledged, an internal process where being seen to have read something is the point. The visibility is a feature.

Use open tracking when what you need is timing: a quote, a proposal, a follow-up on a conversation that went quiet. You are not trying to prove anything, you are trying to decide when to write again.

Use neither for newsletters and mass sends, where aggregate statistics from your sending platform are more meaningful than individual events, and for personal correspondence, where measuring a friend's reading habits is simply odd.

The mistake both tools invite

Neither method tells you that someone read your email. A receipt tells you a client confirmed it. A tracker tells you an image loaded. Both are proxies.

The practical rule: never say out loud that you know someone read your message. It is intrusive, and it is not reliably true. Use the information to choose your moment, not to score a point.

Support across the major clients

Whether a read receipt reaches you depends entirely on the recipient's software, and the landscape is uneven.

• Personal Gmail: no support at all. The request is silently discarded.
• Google Workspace: supported, but disabled by default and often restricted to internal recipients by the administrator.
• Zoho Mail: supported, both to request and to respond.
• Outlook and Microsoft 365: supported, with per-user settings that frequently decline automatically.
• Apple Mail: no interface for requesting them, and receipts are typically ignored.
• Mobile clients: support is inconsistent and often absent.

The consequence is arithmetic rather than philosophical. Writing to a mixed audience, a large share of your requests will produce nothing at all, and you will not know which.

What each one does when it fails

The failure modes are as informative as the features.

A read receipt fails silently and completely. You get nothing, and you cannot distinguish between a declined request, an unsupported client, and a message nobody opened. Three very different situations, one identical outcome.

Open tracking fails in two directions. Blocked images produce silence on a message that was read. Privacy proxies and security scanners produce opens nobody made. You get data, some of which is wrong, and the errors have recognisable shapes.

Between a method that tells you nothing and one that tells you something imperfect, the second is more useful, provided you know how it lies.

The ethical difference, stated plainly

A read receipt asks permission. Open tracking does not. That is a real distinction and it deserves more than a shrug.

What makes tracking defensible is proportionality: measuring one message you had a genuine reason to send, in order to time your next one, is very different from recording every email you send to everyone forever. The technique is identical; the practice is not.

This is why a per-message toggle is more than an interface detail. It is what keeps the decision conscious, and it is the difference you would point to if someone ever asked you to justify it.

A simple decision rule

Ask what you would do with the answer.

If you need proof that someone received something, for a process or a contract, request a receipt and accept that it may not come. If you need to know when to write again, track the open and accept that the data is approximate. If the answer would not change your next action, do neither, and save yourself the data and the discomfort.

Conclusion

Read receipts are honest and unreliable. Open tracking is discreet and approximate. For commercial email, where the real question is "when should I follow up", the second usually wins, provided you treat the data as a signal rather than a verdict.

Frequently asked questions

Which one should I use for a quote?

Open tracking. A receipt is visible, can be declined, and reports a single opening. A quote is typically opened several times and forwarded internally, and that pattern is what tells you when to call.

Can the recipient tell that I am tracking opens?

Not at a glance. Unlike a read receipt, nothing is displayed. It is visible in the message source to anyone who looks.

Can I use both on the same message?

You can, but it is the worst combination: you take the visibility cost of the receipt and the imprecision of the tracker, with a recipient likely to notice both.

All articles →