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&utm_campaign=may_launch" width="1" height="1" alt="" style="display:none" />
Inside an HTML attribute, the & between parameters is written as &. 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.