BlueTicks for Gmail

WhatsApp-style read receipts for Gmail

Visit Website
July 29, 2026 I built WhatsApp-style read receipts for Gmail because every tracker wanted OAuth access to my inbox

Three weeks ago I shipped BlueTicks, a Chrome and Firefox extension that puts WhatsApp-style ticks in your Gmail Sent list: one tick when the email goes out, two blue ticks the moment it is opened, in real time.

The itch was simple. I kept wondering whether my emails had been read, and every tracker I tried either demanded OAuth access to my whole mailbox or stamped a visible signature onto the message. Both felt disproportionate for something this small.

So the constraints came first: no OAuth, no access to the Google account, no email content on my servers, nothing added to what recipients receive. Subject lines and recipients stay in the browser. The detection itself is the classic tracking pixel, which means it has the classic limits (image proxies, Apple Mail Privacy Protection), and I would rather say that plainly than pretend detection is perfect.

Where it stands today: 25 users on the Chrome Web Store with five 5-star reviews, and 2 daily users on Firefox. That Firefox number is the interesting one. The add-on has been live since mid-July and the listing is genuinely good, but I only realised this week that not a single one of my directory listings actually linked to the Firefox page. They all said "Chrome and Firefox" in prose and then linked to Chrome. So the whole Firefox funnel was a dead end I had built myself.

The other thing I have been documenting is the directory grind. I have vetted around twenty launch directories that advertise a free tier. Most of them gate it behind putting their badge on my site, a queue measured in weeks, or a paywall that only appears at the last step. One of them showed free slots in its calendar while every single date was disabled in the markup. I keep a written log of which ones are honest.

A Peerlist launch went out on Monday and a Uneed launch is queued for August 16. There is a free tier with a monthly cap, and the paid plan is 4 dollars a year.

If you want to try it: Chrome Web Store https://chromewebstore.google.com/detail/blueticks-for-gmail/hipmeeilnlifaoegpfiodlnapplogpkn and Firefox Add-ons https://addons.mozilla.org/en-US/firefox/addon/blueticks-for-gmail/

Happy to answer anything about how the real-time delivery works, the privacy trade-offs, or the directory grind.

3 Comments

  1. 1

    I liked that the constraints came before the implementation.

    Sometimes the product isn't defined by what it can do, but by what it deliberately refuses to require from users. That tends to create a very different kind of trust.

    1. 1
      You wrote this a month ago and I am only answering now, which is my fault and not a scheduling subtlety: my own tool for finding unanswered comments required a digit before the word day, and this platform writes a day ago. Anything older than about a day fell out of the list silently, and yours was the oldest, so it fell out first. The sentence I kept was that a product can be defined by what it refuses to require. At the time that was a design intention on my part, and I could not have shown you anything to back it. I can now. I downloaded the packages of eight Gmail tracking extensions straight from the Chrome Web Store and read the manifest each one ships with, which is the list a user accepts at install and never sees again. Inside that one category the range surprised me. At the permissive end sits an extension that wants every site you browse plus your cookie jar, and one that can switch your other extensions on and off. At the other end are several that never leave Gmail. The store listing makes them look interchangeable. What that measurement taught me is narrower than your sentence and sits underneath it. Refusing to require something is invisible at the moment it matters. The install screen shows what a product asks for, never what it declined to ask for, so the restraint you are describing has no surface where a user could notice it. The only way I have found to make it visible is to publish the comparison and put my own row in it, without coming out on top. The trust part I am less sure about than you are. I have no measurement that connects a narrower permission set to anyone choosing it, and I have looked. What I have is the opposite direction: the comparison is the kind of thing people read and cite, and it works whether or not my product wins on it. For context, I build a small Gmail extension, which is why I had that comparison lying around. It does not ask for access to your inbox, and that constraint came before anything I built on top of it. The comparison is public and dated, with the commands, so it can be rerun on any category rather than taken on trust.
      1. 1

        That’s a much more interesting finding than simply saying “less access = more trust.” I’d be interested in continuing the conversation beyond the thread — would you be open to sharing the best email to reach you on?

About

Email is the only channel that never answers back: you send, then you guess. BlueTicks for Gmail exists so a mail to a client or a recruiter tells you when it was read, right inside Gmail, without changing how you write.