MailPixelEmail tracker.
Create a real pixel.
Use this email tracker to generate a hosted pixel now. Save its private activity link, then treat every image request as context—not proof of a read.
Prefer Gmail? Use the Chrome extension →No account required · 30-day pixels · Private management link
Ready in one step.
Browser storage is unavailable. Copy this private link before leaving the page.
Activity access is saved in this browser. Anyone using this browser profile can open and manage the pixel.
Create a hosted pixel. No account required.
A request to the pixel is a signal, not proof that a person read the message.
Saved on this browser
These private links stay only in this browser. Clearing browser data removes them.
How this email tracker works.
This email tracker hosts the image, records requests for 30 days, and lets the holder of the private link pause or delete the pixel.
Real image requests
Each valid image GET can create an event with a server timestamp. The email tracker never calls the new pixel from the creation screen, so it starts at zero.
Separate private access
The public image URL contains no dashboard credential. A different private link controls the activity report and cannot be recovered if lost.
Finite retention
Pixels expire after 30 days and have a request cap. Pause or delete earlier from the report if the experiment is finished.
One tiny image.
A private request timeline.
Copy the generated HTML or pixel URL. Activity access is saved in this browser, and the label belongs to your private report, so avoid personal data and message contents.
The snippet works only where remote HTML images are supported. Normal Gmail compose does not accept raw HTML as a supported workflow, so frequent Gmail users should use the extension.
Read the illustrated setup guide ↗Place it in a compatible HTML email workflow.
Use this browser to view requests, pause, or delete the pixel.
An image request is a signal, not a verified read.
Skip manual HTML insertion.
The Chrome extension adds tracking controls to Gmail. The website and extension are separate workflows in this release; activity is not automatically shared.
What the event can—and cannot—say.
An email tracker observes a remote image request. Mail clients, privacy proxies, forwarding, caching, and blocked images can all change that observation.
Generate separate URLs
The service creates an opaque image URL and a private management link. Never include a recipient address in the label or snippet.
A client may load the image
The service records a server-side request if the pixel is active. Automated proxy loading may generate the same signal.
Use it as context
A request is not verified identity, delivery, attention, agreement, or proof that the message was read.
Add the pixel in Gmail.
Follow the workflow we tested with a real message and learn how to interpret Gmail proxy requests.
Email tracker: honest answers.
Does this email tracker create a real pixel?
Yes. It creates a hosted image URL and private activity link. The service records image requests while the pixel is active and within its limits.
Can I paste the raw HTML directly into normal Gmail compose?
That is not a supported Gmail workflow. Use a compatible HTML editor or use our Gmail extension, which is designed for composing inside Gmail.
Can an image request prove someone read my email?
No. Privacy features and automated image requests can create a signal without a human read, while blocked images can hide a real read.
Does the website share data with the extension?
Not in this release. The website tool and Chrome extension are presented together, but their accounts, limits, and activity are not automatically combined.