Email tracking pixel generator
Create a real remote image and a private activity link. No server setup or account is required.
Save the private link. Anyone with it can view, pause, or delete this pixel, and it cannot be recovered if lost.
Create a hosted pixel. No account required.
A request to the pixel is a signal, not proof that a person read the message.
What this email tracking pixel generator creates
The generator creates two different credentials. The public pixel URL belongs in a compatible HTML email. It contains an opaque random ID and returns a one-pixel transparent GIF. The private management link contains a separate secret used to view activity, pause collection, or delete the pixel.
Save the private link when it appears. We store a hash of its secret rather than a recoverable copy, so there is no reset email or account recovery in this version. Anyone who receives the full private link can manage the pixel.
Use the HTML without causing your own event
The result shows the image element as text and never renders the remote image. Copying or downloading the snippet therefore does not create an event. Do not paste the pixel URL into a browser merely to inspect it unless you intend to record a test request.
A normal Gmail compose box does not provide a supported raw-HTML insertion workflow. Code may appear as text or be rewritten. Use a compatible email editor, a tested integration, or the Gmail extension below.
How the email tracking pixel generator reports activity
Open the management link to see the state, total image requests, first and latest request times, and a paginated event list. The page refreshes while it is visible. It does not store the management key in a site account or send it to analytics.
You can pause the pixel without breaking the email image. Requests still receive a transparent GIF but are not recorded. Deleting removes the current pixel record and events; later image requests still receive a transparent GIF and cannot recreate the deleted record.
Thirty-day retention and service limits
A pixel expires 30 days after creation. Pausing does not extend its life. Each pixel has an event cap, and creation is rate-limited to reduce automated abuse. These are product rules rather than a claim that each browser or IP address represents one person.
After expiry the private report stops returning historical activity. Cleanup runs separately, so an expired record may remain briefly in storage before scheduled deletion. Hosting infrastructure can also retain operational data according to its own backup and security systems.
A request is not a verified read
Remote images are imperfect measurement. A mail proxy may fetch an image before a person reads the message. A client may cache it, block it, or load it only after the recipient chooses to display remote content. Forwarding can cause another person to request the same URL.
The report therefore says “image requests.” It does not report a verified person, reading time, delivery certificate, agreement, or attention. For important decisions, ask the recipient for a direct response.
Give the email tracking pixel generator a neutral label
The optional label helps you recognize a test, but it is stored with the pixel. Do not enter recipient addresses, message bodies, passwords, medical information, or other sensitive content. A neutral description such as “September proposal” is enough.
Does this require a login?
No. Access is controlled by the private management link, which cannot be recovered if lost.
Does the website send email?
No. It creates and hosts a pixel. You decide where to place the HTML and which messages are appropriate to test.
Can I track links too?
No. This release records only requests to the generated image route. It does not rewrite or monitor links.