How an image pixel records an event
When a browser renders an image element, it requests the URL in its src attribute. A server can count that request as an event and read standard request details such as time, user agent, IP address, and—depending on the referrer policy—the page origin. Query parameters can add a concise event name or campaign identifier.
The generated element is one pixel wide and has empty alternative text, so assistive technology treats it as decorative. The preview deliberately does not load the endpoint; it shows the request as text so creating a snippet never pollutes your data.
Use parameters as a small, intentional schema
Prefer stable parameters such as event, campaign, or placement. Avoid names, email addresses, full page URLs with sensitive query strings, or persistent visitor IDs. The receiving endpoint should validate values, limit retention, and ignore unknown parameters.
A cache-buster makes otherwise identical requests unique. This generator uses a clear timestamp placeholder because static HTML cannot compute a new value by itself. Replace it in your template or application when the pixel is rendered.
Consent and delivery considerations
An image request still shares data with its destination even when it sets no cookie. Decide which lawful basis applies, state the purpose in your privacy notice, and render the snippet only after any required consent. Keep the endpoint under your control where possible and use HTTPS for transport security.
Pixels provide a narrow delivery mechanism, not a complete analytics model. For broader measurement, use a purpose-built privacy-friendly analytics system that handles events, sessions, retention, and reporting without turning every implementation detail into a custom endpoint.