Gmail, with a clearer email timeline.

MailReveal connects through Google's OAuth consent screen. In the private workspace, open Connections → Email accounts → Connect with Google, select your Gmail mailbox, and approve the requested permissions. Your Google password stays with Google. The connected address appears in Connections.

Send a tracked email

Prepare an email in MailReveal and choose Send email. MailReveal inserts a unique image into the HTML message and submits it through Gmail's API using your connected address. Provider acceptance is recorded separately from image-load activity.

Send from Gmail on your phone

Choose Save draft in Gmail. Open that draft in Gmail on your phone and send it there. The tracking image is already in the draft. Sync sent history in MailReveal to match the tracked message with Sent mail. A Google connection does not automatically add trackers to other emails composed in native Gmail.

Compose in Gmail on Chrome

The MailReveal Chrome extension pilot adds a separate tracker to each new Gmail compose window. Install it from Connections → Email accounts, connect a tracker-only API key, and reload Gmail. Add one recipient and a subject, then wait for “Tracking ready” before sending. For replies, use Gmail’s “Edit subject” to open a compose window. Cc/Bcc and inline replies are not supported in this pilot.

The extension shares only sender, recipient, and subject with MailReveal. It keeps your key outside the Gmail page, does not upload email bodies, and does not send emails itself. Direct MailReveal image requests from your own Gmail browser are blocked to reduce compose previews. Gmail proxies, previews in other clients, and privacy features can still distort or hide opens. Installation on Chrome does not add tracking to new emails composed on your phone.

For any HTML email client or agent, call POST /api/v1/trackers (or the MCP create_email_tracker tool) for each email, then insert the returned signatureHtml into that email before sending. Signed webhooks carry the subject, recipient, and unique message ID. A fixed signature URL cannot recover these details after an email has been sent.

Why we request these permissions

Account identity: identifies the connected email address. Gmail compose: creates drafts and sends messages you request. Gmail read: verifies the mailbox and checks recent Sent messages to reconcile tracked drafts and uncertain sends. Unrelated mail content inspected during matching is not retained in the message database.

Signatures, APIs and agents

A reusable HTML signature works in email clients that support HTML images, without connecting Gmail. It provides aggregate activity rather than an individual email or recipient history. Authorized API and MCP integrations can prepare trackers and retrieve activity, and signed webhooks can send events to trusted systems selected by the owner.

You control the connection

Disconnect in Connections or revoke access in your Google Account. MailReveal currently provides one private workspace and one connected Gmail account. Public customer onboarding is under development, and Google OAuth verification is pending. Image loads are signals, not proof of reading.