Email Tracking Pixel Generator

An email tracking pixel is a 1x1 transparent image embedded in an HTML email. When the recipient's mail client loads images, it requests that file from your server, and your server logs the request as an open. Every open rate you have ever seen was produced this way. Use the generator above to build the pixel tag with your own callback URL and whatever parameters you need to tie a request back to a specific campaign and subscriber.

How an email tracking pixel works

The pixel is an ordinary img tag pointing at a URL you control, sized to one pixel and made invisible. The interesting part is the request, not the image. When the mail client fetches it, your endpoint receives the query string you embedded, along with a timestamp, an IP address, and a user agent string. You record those, return a tiny transparent GIF or PNG, and you have an open event. Include a unique subscriber or send identifier in the query string if you want per-recipient tracking rather than a campaign-wide counter. Pair the pixel with tagged links from our UTM builder so opens and clicks land in the same reporting model.

Why open rates overstate reality

Open tracking is directional, not exact, and it has been getting less exact every year. Apple Mail Privacy Protection, introduced with iOS 15, pre-fetches every image in every message through Apple proxy servers whether or not the recipient ever looks at the email. Anyone reading in Apple Mail therefore registers as an opener of everything you send. Gmail proxies and caches images too, so a second look at the same email may never hit your server again. Many corporate gateways and desktop clients block remote images by default, which pushes the number the other way. Treat opens as a trend line and judge campaigns on clicks, replies, and revenue instead. Our guide to improving email open rates covers how to read the open rate after MPP. Our open rate calculator and CTOR calculator help you separate the two.

Privacy, consent, and disclosure

A tracking pixel collects personal data. Under GDPR, the UK GDPR, and similar regimes, that means you need a lawful basis for it and you must disclose it. The practical minimum is a plain-language line in your privacy policy explaining that you record opens and clicks, what you store, and how long you keep it. Several jurisdictions and interpretations require explicit consent rather than legitimate interest, so check your own position before rolling tracking out across an existing list. Never use a pixel to track people who have not opted in to receiving your email in the first place.

When to build your own pixel, and when not to

Building your own is the right call when you are sending from your own application, need the raw event stream in your own database, or are learning how the mechanism works. It becomes the wrong call quickly once you are running marketing campaigns, because you also have to host the endpoint, deduplicate Apple pre-fetches, filter bot opens, expire cached requests, and reconcile the whole thing against clicks and revenue. Sequenzy does that already: opens, clicks, and revenue per email are tracked out of the box, known security scanners are filtered out of your stats (with stricter bot filtering you can turn on), and reports show how many opens came through Apple, Gmail, and Yahoo privacy proxies, so you can read your numbers honestly without maintaining any of the plumbing. See campaign analytics for what that reporting looks like. If you are weighing other options, our comparison of email marketing platforms notes which ones report natively beyond opens and clicks.

Test a tracking pixel live

The live test at the top of this page gives you a hosted pixel without running a server. Copy it into an email, send the email to yourself, and open it. Each time the pixel loads, the page shows what fetched it: a mail client loading it directly, Apple Mail Privacy Protection prefetching it, Gmail or Yahoo loading it through their image proxies, or a security scanner inspecting the message. Running the test on an Apple Mail inbox is the fastest way to see why open rates are inflated: the "open" often arrives before you have looked at the email at all. Test pixels expire after 24 hours, and the tool stores only when the pixel loaded and which client or proxy fetched it, never an IP address or location.

Where to put a tracking pixel in your HTML

Most platforms place the pixel either at the very top of the body or just before the closing body tag. The top is the safer choice for long emails: Gmail clips messages larger than about 102 KB and hides the rest behind a "View entire message" link, so a pixel at the end of a clipped email never loads and the open is never recorded. Keep the tag a plain img element with width and height set to 1, an empty alt attribute, and no border. If you are building the email itself from scratch, the AI HTML Email Builder produces email-safe HTML you can drop the pixel into, and the Email Size Checker tells you whether the message is close to Gmail's clipping limit. Avoid putting it inside elements that some clients hide or strip, and give it an absolute https URL, since email clients do not resolve relative paths. If you send plain-text emails, there is nowhere to put a pixel, which is one reason plain-text campaigns report no opens.

Troubleshooting open tracking

If opens spike within seconds of sending, the cause is almost always machines, not readers: Apple Mail Privacy Protection downloads images in the background when messages arrive, whether or not anyone opens them, and corporate security filters open messages to scan links and images. If an email shows no opens at all, check that images are enabled in the client you tested with, that the pixel URL is reachable over https, and that the message was not clipped by Gmail. If the first open registers but repeat opens never do, the client is caching the image. Gmail's proxy is the usual reason, and no-cache headers only partly help. When numbers look wrong, compare them against clicks, which are much harder for proxies to fake.

How to tell if an email contains a tracking pixel

Open the message source ("Show original" in Gmail, "View source" in most desktop clients) and look for img tags that are 1x1 pixels or point at URLs with long unique identifiers in the path or query string. Most marketing and sales emails contain one. To stop them firing, turn off automatic remote image loading in your mail client, or use Apple Mail Privacy Protection, which loads images through a proxy so the sender cannot see your IP address or when you actually read the email.