Email tracking pixel generator

Build a small HTML image snippet with a unique identifier. You bring the endpoint; this browser tool handles the code.

What this email tracking pixel generator creates

The email tracking pixel generator takes an HTTPS image endpoint and adds a random message ID. It returns an image element with one-pixel dimensions, empty alternative text, and an escaped URL. Existing query parameters stay in place, while an existing id parameter is replaced with the new identifier.

The optional message label stays in the form for your reference. It is not included in the generated URL. Avoid putting recipient addresses, passwords, or private message content into tracking links. An opaque identifier is easier to manage without exposing unnecessary information.

What you need before sending

1. Supply a server endpoint you control that returns a valid image over HTTPS.
2. Implement your own event collection and decide how long records should be retained.
3. Test the snippet in a compatible HTML email editor using accounts you control.
4. Explain any tracking practices appropriately and check the requirements that apply to your situation.

This site does not provide a hosted tracking service. Generating a URL does not create a server route, database, dashboard, or notification system. Downloaded snippets are text files so you can inspect the markup before integrating it.

Why we never preview the generated image

Loading the image here could create an event on your server before an email was sent. Instead, this email tracking pixel generator displays the markup as text. It never fetches your endpoint, never inserts a remote image into the page, and never sends mail on your behalf.

Click Generate again to produce a fresh identifier. Copy transfers the HTML to your clipboard after you click the button. Download saves a text file. Refreshing or closing this tab clears the form; the website does not keep a copy of your input.

Test the endpoint separately

Before embedding the snippet in a message, check that your server returns an image rather than an HTML error page. Keep test identifiers separate from production messages so your own checks do not pollute an activity history. Review how your server handles caching, repeated requests, and expired identifiers. This builder cannot validate those server behaviors because it deliberately does not connect to your endpoint.

A request is not a verified read

Mail applications can block remote images, reuse cached content, or load images through a proxy. Some privacy features retrieve content in the background without the recipient opening the message. Your server must treat these events as imperfect observations.

A data URL containing a transparent image cannot send an event to a remote server. Likewise, a static image address with no collection logic cannot produce an activity history by itself. Accurate interpretation requires much more than generating markup.