Use the workflow that fits your email client.
Your MailReveal workspace and API work independently of the recipient’s browser. Tracking requires an HTML email with a remote image. A request records an image load; it cannot prove who read your email.
Browser workspace
Signup, API key creation, tracking activity, login, and logout are tested in Chromium, Firefox, and WebKit, including Android-sized Chromium and iPhone-sized WebKit layouts. These are automated browser-engine tests, not tests on every physical phone.
Gmail on desktop
The Chrome extension pilot inserts a separate tracker into English Gmail compose windows and inline replies, including To, Cc, and Bcc recipients. Wait for “Tracking ready” before sending. It is installed manually and is not yet in a browser extension store. The extension does not run in Safari or Firefox.
Gmail on your phone
Connect your own Google account, prepare a tracked draft in MailReveal, then open Gmail Drafts and send it there. Connecting Google does not automatically track emails composed directly in the Gmail mobile app. Google may restrict access while its OAuth app is in testing or review.
Outlook, Apple Mail, and other HTML clients
Use an API-generated tracker in each outgoing message, or paste a reusable HTML signature for aggregate activity. The client must preserve and load the remote image. We have not completed delivered-message verification in every Outlook, Apple Mail, or native mobile version. Plain-text messages cannot include image tracking.
What the signals mean
- Gmail proxies and caches images. Repeated opens may not create repeated events.
- Apple Mail Privacy Protection, previews, and security scanners can load images without a person opening the message.
- Image blocking and offline reading may create no event at all.
- Group emails, forwards, and reused signatures do not identify an individual reader.