Gmail Read Receipt: Setup, Limits and DNS

How do I turn on read receipts in Gmail?

Google Workspace Admin Help describes read receipts as a Workspace feature. An admin has to switch it on for the organisation before anyone can request a receipt. On a personal @gmail.com account the option doesn't exist, and no setting will make it appear. On a Workspace account it works in two stages: an admin enables the feature, then each user requests a receipt message by message.

1. 1 Admin step: sign in to the Google Admin console, go to Apps > Google Workspace > Gmail, then open the user settings that contain Email read receipts.
2. 2 Choose who receipts may go to: nobody, addresses inside your organisation plus a list of named external addresses, or any address. You can also have users prompted before a receipt goes to an address outside the organisation.
3. 3 Save, then allow time for the change to roll out. Google notes that Admin console changes can take a while to reach every user.
4. 4 User step: in Gmail on a computer, write your message, click More options (the three vertical dots next to Send) and choose Request read receipt.
5. 5 Send. If the recipient agrees, the receipt arrives in your inbox as a separate message showing when the email was opened.

If Request read receipt is greyed out or missing, there are almost always two possible causes. Either the account is a personal one, or the admin hasn't turned on receipts for the organisational unit your user belongs to.

Why didn't my Gmail read receipt come back?

A Gmail read receipt is a request, not a measurement. Technically it's a Message Disposition Notification (MDN), a mechanism standardised by the IETF. The sending client adds a header asking for a notification, and the receiving client decides whether to send one. Gmail can't force it. These are the usual reasons nothing comes back:

• The recipient declined. Gmail and most other clients that support receipts show a prompt, and declining or ignoring it means no receipt.
• The recipient's client doesn't support MDN. Plenty of mobile and webmail clients drop the request header without telling anyone.
• The recipient's organisation blocks outgoing receipts. A Workspace admin on their side can switch receipts off completely or limit them to internal addresses.
• The message was read in a preview pane, or on a device that never showed the prompt.
• The message went to a mailing list or group address. Receipts are designed for individual recipients.

No receipt doesn't mean nobody read the email. A missing receipt tells you nothing about whether the message was delivered or read. That's why you can't use it as a delivery check.

Read receipts vs. open tracking: which method fits?

Many people who search for a Gmail read receipt really want to know whether an email was opened, without the recipient having to confirm it. That isn't a native read receipt. It's open tracking with an invisible image (a tracking pixel), offered by browser extensions and sending platforms. The three methods compare like this:

Method	How it works	Who needs to cooperate	Where it stops
Native Gmail read receipt (Workspace only)	A header requests an MDN; the recipient's client sends a notification	Your admin, the recipient's client and the recipient	Not available on personal Gmail; the recipient can decline; many clients ignore the request
Gmail tracking extension (e.g. Mailtrack, Boomerang, Streak)	Adds a tracking pixel to messages sent from Gmail; an image load counts as an open	The recipient's client must load images	Image blocking hides opens; privacy proxies that preload images record opens nobody made
Open tracking in a sending platform (e.g. Brevo)	The platform inserts a pixel into each campaign or transactional message	The recipient's client must load images	Same pixel limits; shows total and per-contact opens, not proof that anyone read the message

Apple Mail Privacy Protection preloads remote images, so it records opens that never happened. Image blocking in Outlook and corporate mail gateways does the opposite and hides real opens. Our breakdown of what an email open rate can and cannot tell cold senders covers both distortions.

Should you request read receipts on cold emails?

For B2B cold outreach, a read receipt is the wrong tool. The prompt tells a stranger you want proof they read your message, which is an odd first impression. It also only works if you send from Workspace and the prospect's client plays along. And it answers none of the questions that matter for a campaign: did the receiving server accept the message, where did that server file it, and did anyone reply?

There's a legal side too. The EU ePrivacy Directive requires consent before information is stored on or read from a user's device, unless that's strictly necessary for a service the user asked for. Germany puts this rule into national law in the TDDDG (Telecommunications Digital Services Data Protection Act). Whether a particular tracking setup falls under it is a question for your lawyer, not something a settings page can answer. Separately, Germany's Act against Unfair Competition (UWG) sets consent requirements for advertising email, whether or not you track anything.

Replies and bounces are more reliable signals. A bounce notice tells you exactly why a message was refused. A reply in the thread tells you someone read it.

Gmail DKIM: what it is and where to set it up

Gmail DKIM is the signature Google Workspace adds to outgoing mail. Receiving servers use it to check that the message really came from your domain and wasn't changed on the way. Gmail signs with a default key until you set up your own. With your own key, the signature aligns with your From domain, and that alignment is what DMARC checks. You generate the key in the Admin console under Apps > Google Workspace > Gmail > Authenticate email, publish it in DNS, then click Start authentication. Until you click that button, Google keeps signing with its default key, even if the record already exists. Our G Suite DKIM setup guide walks through each step and the common errors.

Gmail DKIM record: what the TXT entry looks like

The Gmail DKIM record is a TXT record. Its host name is the selector followed by _domainkey. Google's default selector is google, so the host is google._domainkey under your domain. The value the Admin console generates starts with v=DKIM1; k=rsa; p= followed by the public key. Long keys can be too long for a single field in some DNS panels, so you may have to split the value into several quoted strings. If your DNS provider adds your domain to the host field automatically, enter only google._domainkey. Otherwise you'll end up with the domain twice and the lookup will fail. If you also send through Brevo, Brevo publishes its own DKIM selector. It sits next to Google's and doesn't replace it.

Gmail SPF record: the value and the one-record rule

The Gmail SPF record authorises Google's servers to send mail for your domain. Google Workspace Admin Help documents it as a TXT record at the domain root: v=spf1 include:_spf.google.com ~all. The SPF standard allows only one SPF record per domain. If you publish two v=spf1 records, the check returns an error instead of a pass. So if Brevo or another service also sends for the domain, add its include to the same record rather than publishing a second one. The standard also limits how many DNS lookups one evaluation may trigger, and every include counts toward that limit. A long chain of services can therefore break SPF even when each entry is correct. The full Workspace DNS set (MX, SPF, DKIM and DMARC) is in our Google Workspace DNS records guide. You can check what's currently published with the SPF, DKIM and DMARC checker.

How EmailFlow OS sends video outreach from your own domain

EmailFlow OS doesn't use read receipts, and it doesn't replace your DNS setup. It relies on it. You record one video and upload it to EmailFlow OS, connect your Brevo account and your sending domain, and import your prospect list into EmailFlow OS. EmailFlow OS then turns that one recording into a personalised version for each recipient, not one per company. Each version goes out from your own inbox, through your own Brevo account and your own sending domain, never through a shared platform sender.

So the SPF, DKIM and DMARC records you publish for your domain are the ones receiving servers check, and the sender reputation you build stays with your domain. Where a message gets filed is still up to the receiving server. The full setup is described on the EmailFlow OS personalised video email page.

Questions people ask

? Can you get a read receipt on a free Gmail account?

No. Google documents read receipts as a Google Workspace feature for work and school accounts, and an admin has to turn it on. Personal @gmail.com accounts don't have the Request read receipt option. The alternative is pixel-based open tracking from an extension, which works differently: it records image loads, not a confirmation sent by the recipient.

? Does the recipient know I requested a read receipt?

Usually, yes. With a native read receipt (a Message Disposition Notification), the recipient's client typically shows a prompt asking whether to send the notification. A tracking pixel works differently: nothing is shown, and an open is recorded when the email's images load. That's also why image blocking and privacy proxies that preload images distort pixel data.

? Can I request a read receipt in the Gmail mobile app?

Google's help pages describe requesting read receipts in Gmail on a computer, through More options in the compose window. If the option doesn't appear on your phone, write the message on a computer. Whether a receipt comes back still depends on the recipient's client and their organisation's settings, not on the device you sent from.

? Does a read receipt prove my email was delivered?

No. A receipt only comes back if the recipient's client supports Message Disposition Notifications and the recipient agrees to send one. An email can be delivered and read with no receipt at all, or be filed as spam and never seen. To check delivery, look at the Authentication-Results header and any bounce notices. Postmaster data shows your reputation at the domain level.