A Chrome extension that tells you when someone opens the email you sent from Gmail, and why each open counted. Free with a Google sign-in, or run it on your own server.
To maya@harbourline.co, cc tom@harbourline.co · sent today 09:14 · Q1 outreach
Opened ×2
Hits for this email, newest first
Time
Kind
Via
User agent
13:02
Open
Gmail proxy
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
11:47
Open
Gmail proxy
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
10:02
Self view
Gmail proxy
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
09:14
Prefetch
Direct
Mozilla/5.0
Maya opened it 2 h 33 min after you sent it. Google's proxy fetched the image for her.
What a tracker cannot see
Every tracker counts image loads. Likelyread sets aside your own views and Apple’s prefetches, and shows you why each open counted.
Every hit gets a verdict
GET /p/7f3c9e2a-41d8-4b6e-9c1a-2e5f8d0b7a43.gif
Received
11:47:03, 2 h 33 min after sending
From
66.249.84.21, a Google address
User agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
Within 20 s of sending?No
Within 60 s of you opening it yourself?No
User agent exactly “Mozilla/5.0”, from Apple’s network?No
Open, via Gmail proxy
Counted. Maya’s inbox is Gmail, so the request comes from Google, not from her.
GET /p/7f3c9e2a-41d8-4b6e-9c1a-2e5f8d0b7a43.gif
Received
09:14:52, 31 s after sending
From
17.58.101.4, an Apple address
User agent
Mozilla/5.0
Within 20 s of sending?No
Within 60 s of you opening it yourself?No
User agent exactly “Mozilla/5.0”, from Apple’s network?Yes
Prefetch
Not counted. Apple Mail Privacy Protection loads every image when the email arrives, read or not.
GET /p/7f3c9e2a-41d8-4b6e-9c1a-2e5f8d0b7a43.gif
Received
10:02:11, 48 min after sending
From
66.249.84.17, a Google address
User agent
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
Within 20 s of sending?No
Within 60 s of you opening it yourself?Yes, 2 s after
User agent exactly “Mozilla/5.0”, from Apple’s network?No
Self view
Not counted. The extension saw you open your own email and told your server first.
GET /p/7f3c9e2a-41d8-4b6e-9c1a-2e5f8d0b7a43.gif
Received
09:14:21, the second you pressed Send
From
Your own browser
User agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 Chrome/141.0 Safari/537.36
Within 20 s of sending?Yes, 0 s
Within 60 s of you opening it yourself?Not checked
User agent exactly “Mozilla/5.0”, from Apple’s network?Not checked
Self view
Not counted, and usually never sent: the extension stops your browser from loading your own pixel.
What it does in Gmail
Switch it on with the eye
beside Send. Your own rereads are set aside
Self,
Apple’s robot is flagged
Prefetch,
and each campaign gets its open rate
62%.
Tracking never blocks or delays a send. If the extension or your server fails, the email goes out as written, untracked, and its registration retries for seven days.
OpensCountedGoogle’s proxy fetches the image when the email is opened.Seen
RepeatsOften missedThe proxy caches the image, so a second open may never reach you.Partial
LocationNoneEvery Gmail open arrives from a Google address.Hidden
YouFiltered out20 s around sending, 60 s after you open it in Sent.Handled
DeliveryPrefetch, not an openApple loads every image as the email arrives, from its own network, with the bare user agent Mozilla/5.0. Without Privacy Protection the load comes from the reader’s device and counts as an open.Flagged
OpensMostly invisibleAfter the prefetch Apple shows its own copy, so later opens rarely reach you.Hidden
LocationNoneRequests come from Apple’s relays, not from the reader.Hidden
OpensOnly if images loadMany company setups block remote images by default. Those opens are never seen.Partial
LocationRoughly, from the IPStored only while STORE_IP is on. Turn it off and no address is kept.Your call
ScannersCan look like opensSome security gateways fetch images to check them. Their user agents vary.Caution
ForwardsCount as opensAnyone the email is forwarded to loads the same pixel.Caution
Several toOne pixel per emailYou learn that someone opened it, not who.Partial
Images offNothing at allNo image, no hit. Silence is not proof it went unread.Hidden
For comparison, Mailtrack's free plan shows only the first open and adds its signature to your emails, and its full history costs $19.99 a month (mailsuite.com, October 2026).
Fair questions
Because an image loading is all any tracker ever sees. Gmail caches, Apple prefetches and forwards travel. Likelyread sorts out the loads it can tell apart, so the opens you see are the ones that count.
It depends where your recipients are. In France, the CNIL’s April 2026 recommendation says tracking opens to measure a campaign needs the recipient’s prior consent, B2B included. Check before you track.
No. Install the extension and sign in with Google. If you would rather keep everything on your own machine, run the server yourself: a small Linux box with Docker (512 MB of memory is plenty) and a subdomain pointed at it.
git clone https://github.com/Hugo-SEQUIER/likelyread.git
cd likelyread/deploy && cp .env.example .env
# set DOMAIN and LIKELYREAD_TOKEN
docker compose up -d
On Likelyread Cloud, on our server in Germany, visible only to you, never sold or shared. You can download or delete all of it from your Account page. Self-hosted, it lives in one SQLite file on your machine and nothing reaches us. The extension has no analytics either way.
No. If the extension or the server fails, the email is sent exactly as written, without the pixel. Gmail’s Send is never blocked or delayed.
You send from Gmail on the web, in Chrome. Your recipients can read in any app that loads images; the Limits section above says what each one reveals.
A hidden image served from a brand-new domain can raise spam scores. Serve it over HTTPS from a domain with some history.
Tracking is free. Pro costs $36 a year or $5 a month and adds campaign analytics and full history. Self-hosting is free with every feature: it is MIT-licensed open source.