Tracking Pixel Generator

Build a 1×1 image pixel snippet with campaign parameters.

Your own endpoint that logs the request and returns a 1×1 image.

Sent as the event parameter. Leave empty to skip it.

Custom parameters

Add your own keys, such as a list ID or a recipient merge tag.

A fixed value only stops caching once. For a new value on every send, use your email platform's merge tag, such as *|UNIQID|* or {{timestamp}}. Merge tags are left unencoded.

How much of the page address the browser sends with the request. Email clients usually send none.

Pixel

Enter your collector URL to build the pixel.

How an image pixel works

The snippet is a normal HTML image tag. It is one pixel square, has empty alt text so screen readers skip it, and is hidden with display:none. When the page or email renders, the browser requests the image URL, and every parameter you added travels with that request.

<img src="https://collect.example.com/pixel.gif?event=email_open&amp;utm_campaign=may_launch" width="1" height="1" alt="" style="display:none" />

Inside an HTML attribute, the & between parameters is written as &amp;. The generator escapes it, and any quotes or angle brackets in your values, so the snippet is valid HTML. Your server still receives a normal &.

When to use one

  • Emails, where scripts never run but images usually do.
  • Partner or marketplace pages that let you add an image but not a script.
  • Confirmation pages on systems you cannot add an analytics script to.

On your own website a script-based tracker records more: page views, referrers, sessions and events without a separate image for each one.

Building the collector

The endpoint only has to do two things: write the request (time, query parameters and, if you need them, user agent and IP) to a log or database, and reply with a small transparent GIF or PNG and a Cache-Control: no-store header. Keep personal data out of the URL unless you have a clear reason and consent, because image URLs end up in server logs and proxy caches.

Frequently asked questions

What is a tracking pixel?

A tiny, invisible image whose address points at a server you control. When an email or page loads the image, the browser requests that address, and the server logs the request together with the parameters in the URL.

Does this tool collect the data for me?

No. It only writes the snippet. The collector URL must be your own endpoint, or one from a tool you use, that records each request and answers with a 1×1 image.

Why are email open rates from pixels unreliable?

Some email clients block images until the reader allows them, so real opens go uncounted. Others, including Apple Mail with Mail Privacy Protection, fetch every image in advance through a proxy, so emails count as opened even if nobody read them.

What is a cache buster for?

Browsers and image proxies may reuse an image they have already downloaded instead of asking your server again. A value that changes on each load, usually filled in by your email platform's merge tag, makes every load a new request.

Do I need consent to use a tracking pixel?

In the EU and UK, a pixel that reads or stores information about a person, or lets you follow them, generally needs consent under the ePrivacy rules and GDPR, the same as a cookie. Other places have similar rules. Check what applies to you and describe the pixel in your privacy policy.

Related tools

All tools