Gmail Read Receipts Don't Work — Use This Instead

Gmail has a read receipt feature. You've probably tried it. You've probably been disappointed.

Here's the problem: Gmail read receipts are designed for internal corporate communication, not for emails you send to prospects, customers, or anyone outside your organization. When you send to an external address, the recipient gets a dialog asking if they want to send you a read receipt. Most people ignore it, dismiss it, or don't even see it.

The result: you have no idea if your email was opened, and you're annoying your recipient with a permission prompt they didn't ask for.

There's a better way.

Why Gmail read receipts fail for external email

Gmail's native read receipts have three hard limitations:

1. Recipient consent is required
When you request a read receipt, Gmail appends a special header to your email. When the recipient's email client sees that header, it may show a dialog asking if they want to confirm the read. "May" is doing a lot of work here — not all clients support it, and the ones that do give the recipient full control over whether to respond.

2. They only work reliably inside the same Google Workspace domain
Workspace-to-Workspace read receipts work because both organizations trust the same Google infrastructure. The moment your recipient is on Outlook, Apple Mail, or a different mail server, the receipt mechanism is unreliable at best.

3. They're disabled by default for most accounts
Your Workspace admin controls whether read receipts are enabled. If you're on a free Gmail account, the option may not appear at all depending on your account type.

How email tracking pixels actually work

Instead of asking the recipient for permission, a tracking pixel works invisibly:

1. When you send the email, a 1×1 transparent image is embedded in the HTML body
2. The image's src points to your tracking server: https://track.yourdomain.com/o/{token}
3. When the recipient opens the email, their email client loads the image
4. Your server records the request — IP, user-agent, timestamp — and logs an open event
5. You get notified

The recipient never sees a prompt. The tracking is passive.

This is the same mechanism used by every major email marketing platform — Mailchimp, HubSpot, ActiveCampaign — and it works reliably across every email client.

The accuracy problem: bots and proxies

Raw pixel tracking has one real challenge: not every image load is a human opening an email.

Apple Mail Privacy Protection (MPP) — introduced in iOS 15 — pre-fetches images in emails before the user opens them. If you don't filter MPP loads, you'll see phantom opens from Apple's proxy servers instead of real opens.

Gmail's image proxy — Gmail caches images to protect user privacy. When you send to a Gmail recipient, the first load of your tracking pixel may come from Google's proxy servers rather than the recipient's browser.

Known bot user-agents — Email security tools scan messages for malicious links, and that scanning loads images too.

A good tracker strips all of this before counting an open. Look for:

• Apple MPP fingerprint detection (specific IP ranges + user-agent patterns)
• Gmail proxy IP range filtering
• Bot user-agent blocklist
• Deduplication per recipient (so one human = one open, not ten)

Setting up tracking with Maildriply

Maildriply is built as a purpose-built Gmail tracker — not a CRM bolt-on, not a shared SMTP relay. Here's how it works:

OAuth scope: We request only gmail.send. We cannot read your inbox — the scope technically doesn't allow it.

Delivery: Every email leaves your own Gmail account through the Gmail API. No shared IP pools, no SMTP relay.

Bot filtering: We strip Apple MPP events, Gmail proxy loads, and null/known-bot user-agents before any open is counted.

Click tracking: Links are rewritten to HMAC-signed redirects. The destination URL is locked at send time on our server, so there's no open-redirect risk for your recipients.

Setup:

1. Sign in with Google at app.maildriply.com
2. Connect your Gmail account
3. Compose or use a template
4. Toggle tracking on, click send

That's it. The tracking pixel is injected automatically. You don't paste any code, and you don't configure any DNS records.

What tracking tells you that read receipts can't

Even if Gmail read receipts worked perfectly, they'd only tell you whether the email was opened. Pixel tracking gives you significantly more:

Privacy considerations

Tracking pixels are a standard web technology — the same mechanism that makes web analytics work. There are a few things worth knowing as a sender:

Disclosure: For mass email or cold outreach, disclosing that you track opens is increasingly expected and in many jurisdictions legally required. For one-to-one business email, norms vary.

Apple MPP: Apple Mail users who enable MPP effectively opt out of pixel tracking. A good tracker tells you when an open is likely MPP (proxy-triggered) vs. a real human open, and won't count the proxy load.

Unsubscribe: For any form of outreach, include a clear way for recipients to opt out. Maildriply injects an unsubscribe link into tracked sends.

Bottom line

Gmail read receipts were designed for internal Workspace communication. For external email — sales, recruiting, freelance follow-ups, investor outreach — they're unreliable.

A properly built tracking pixel with bot filtering gives you open and click data that's actually useful: when your email was read, which links were clicked, and how many times it was opened. All without asking your recipient for permission.

Try Maildriply free — 500 tracked sends/month, no credit card →