Skip to content
Learn · Updated July 2026

Email tracking

Email tracking records what happens to a message after it is sent — typically whether it was opened, whether links were clicked, and sometimes whether it was forwarded. Open tracking works by embedding a tiny image that loads from your server when the message is displayed, which is why it has become substantially unreliable.

How it works

A one-pixel image with a unique identifier is embedded in the message. If the recipient's client loads images, your server records a request and counts an open. Click tracking rewrites links to route through your domain before redirecting, which is more reliable because a click requires deliberate action.

Why open rates stopped meaning much

Apple's Mail Privacy Protection pre-fetches images through a proxy whether or not the recipient reads the message, so a large share of recorded opens are machine-generated. Corporate security scanners do the same. Treat open rate as a rough directional signal at best and never as a scoring input.

Tracking domains matter

Rewritten links carry reputation. Using a shared tracking domain means inheriting the reputation of everyone else on it; a tracking subdomain of your own sending domain, over HTTPS, keeps that reputation yours.

How Autocloz handles it

Autocloz tracks opens and clicks with per-workspace tracking domains rather than a shared one, and reports reply rate as the primary engagement metric precisely because open rate is no longer trustworthy. Sequence exit is driven by replies, never by opens.

FAQ

Is email open tracking still accurate?

Not reliably. Apple's Mail Privacy Protection pre-fetches tracking images regardless of whether a message is read, and corporate scanners do the same, so recorded opens include a large share of machine activity. Clicks and replies are far more trustworthy signals.

Should I use a shared tracking domain?

No. A shared tracking domain means your links carry the reputation of every other sender using it. Use a tracking subdomain of your own sending domain, served over HTTPS, and never a public link shortener.

Related terms