Maildriply
All posts
5 min readby Maildriply Team

Gmail Read Receipts Don't Work — Use This Instead

Gmail read receipts only work on work or school accounts, and the recipient decides whether to send one. Here's what actually tells you when someone reads your email.

gmailread receiptsemail trackinghow-to
Illustration of a crumpled paper receipt next to an envelope sending a signal from a small pixel

Gmail read receipts only work on Google Workspace work or school accounts, and the recipient decides whether to send one, so most emails never return a receipt. Personal @gmail.com accounts can't request them at all. The practical alternative is open and click tracking: a per-recipient pixel shows roughly when the message was opened, and tracked links show who clicked, without asking the recipient anything.

Read receipts are built for email inside an organization, not for prospects, customers or anyone outside it. When a receipt is requested, the recipient sees a prompt and can send it or put it off. Most people dismiss it, and you're left guessing while having asked them for something they didn't expect.


Why Gmail read receipts fail for external email

Gmail's native read receipts have three hard limitations:

1. The recipient decides
When you request a read receipt, the recipient is asked whether to send it. In Gmail they can click Send receipts or Not now, and other email programs may not ask at all. Either way, the recipient has full control over whether you hear back.

2. Personal Gmail accounts can't use them
Google's read receipt help page says read receipts are only available for work or school accounts and don't work with personal @gmail.com addresses. If you send from @gmail.com, the option isn't there.

3. Admins and email programs can block them
A Workspace administrator chooses whether read receipts are allowed and which outside addresses they can go to (admin settings). Google also notes that receipts aren't returned for messages sent to a group mailing list, or when the recipient's email program doesn't sync in real time.


How email tracking pixels actually work

Our guide to email tracking in Gmail covers setup and accuracy in full. Here's the short version.

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 (here's how to set up real-time open notifications in Gmail)

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

This is the same mechanism used by every major email marketing platform, including Mailchimp, HubSpot and ActiveCampaign. It works in any email client that loads images, which is why opens are a strong hint rather than proof.


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, downloads remote content privately in the background when a message arrives, instead of when it's viewed (Apple). Unfiltered, those downloads show up as opens that never happened.

Gmail's security scan — Gmail loads every image through its own proxy to protect the recipient's privacy, so the fetch comes from Google's servers, not the recipient's browser (Gmail, 2013). That proxy fetch is a real open. Separately, Gmail runs a security scan seconds after delivery that loads images before anyone reads the message, and that one isn't.

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 detection (Apple's proxy IP ranges and user-agent patterns)
  • Telling Gmail's image proxy (a real open) apart from Gmail's security scan (not one)
  • 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 drop Gmail's prefetch bot, discard Apple MPP and known-bot fetches that land seconds after send, ignore your own views of the sent thread, and dedupe rapid repeats before an 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:

SignalGmail Read ReceiptEmail Tracking Pixel
Was it opened?Yes (with consent)Yes (automatically)
When was it opened?YesYes, with timestamp
Was it opened multiple times?NoYes
Which links were clicked?NoYes
Was it opened on mobile or desktop?NoSometimes. Gmail's proxy hides the device for Gmail recipients
Recipient locationNoRough at best. Proxies hide the recipient's real IP

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 drops the proxy loads it can identify, such as the ones that arrive seconds after sending, but a later MPP fetch can still look like a real open. Treat clicks as the stronger signal.

Unsubscribe: For any form of outreach, give recipients a clear way to opt out and honor it. Maildriply won't send a campaign to anyone marked as unsubscribed.


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 during early access, no credit card →

Explore Maildriply

Keep reading