Bots and scanners are filtered out.
Apple's privacy proxy, corporate scanners, and Gmail prefetches get labeled as machines — never counted as reads.
Lots of machines open your email before a human does: Apple Mail Privacy Protection pre-loads images for its users, corporate gateways like Mimecast and Proofpoint scan attachments and links, and Gmail itself prefetches images at delivery. Most trackers count every one of those as an 'open' — which is how you end up with emails 'read' 30 seconds after sending at 3am.
MailViewed classifies every single pixel load. Machine fetches are labeled — you'll see them in the email's timeline as filtered (bots/scanners) with the reason — and they never turn a tick green, never fire a notification, and never count in your open rate.
What counts as a real open
- A load through Gmail's image proxy when a person displays your email in Gmail.
- A direct image load from a real mail client (Outlook, Apple Mail on desktop, Zoho, and so on).
- A click on a tracked link — the strongest proof someone is reading.
One machine deserves its own mention: the Gmail app on phones. The moment your email's push notification reaches your recipient's phone, the app pre-downloads the message and its images so it opens instantly when tapped — a pixel load with nobody reading. MailViewed holds a first open that arrives within moments of delivery and counts it only once something a machine can't fake confirms it: a link click, a reply, a normal open after the delivery window — or, if your recipient also uses MailViewed, their own extension confirming the open the instant their Gmail displays it. Your recipient opening the email later counts exactly as usual.
Your first two sends are the exception. A new account's first tracked emails are almost always tests, opened within seconds — so for those two, an open counts the moment it happens (the timeline row says so). From the third send on, the full protection above applies to every email.
This honesty is measurable: open your email's detail page and the timeline shows the human opens and the filtered scanner loads, side by side, with reasons. Ambiguous loads (a Gmail refetch that might or might not be a re-open) are stricter still: recorded internally, shown only once something confirms a human was reading.