> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/email-open-tracking-and-tracking-pixels/knowing-more-on-tracking-pixels.md).
# Knowing More on Tracking Pixels
Understanding open tracking pixels: implementation, purposes, and detection
Batch emails may include tracking pixels inserted at the request of Batch customers ([see here](/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/email-open-tracking-and-tracking-pixels/managing-email-tracking-pixels.md)). Pixels are generated dynamically by SparkPost, the downstream mail delivery partner acting as a sub-processor.
### **Purposes**
Data controllers use pixels for the following purposes within the Batch product:
1. **Campaign performance:** Open rate analysis to measure and optimize campaign performance: personalizing content, adjusting send frequency, or selecting the appropriate channel (email, SMS, push).
2. **Profiles & cross-channel targeting:** Building recipient profiles based on demonstrated preferences and interests, in order to target them in contexts other than email: websites, mobile applications, other communication channels.
3. **Deliverability:** Individual-level open rate measurement for deliverability purposes.
When users provide consent for tracking pixels, two distinct pixels are inserted into every email: one near the top of the message body and one near the bottom. Pixels are generated dynamically by SparkPost, our mail delivery partner.
### Technical Characteristics
Two distinct pixels are inserted into every email when consent is granted for a specific profile: one near the top of the message body, one near the bottom. The dual placement (top/bottom) is used to improve open detection reliability across email clients that block remote image loading selectively.
Each send produces URLs that are unique per recipient and per campaign.
All tracking pixels share the following properties:
| Property | Value |
| ----------- | ---------------------------------------------- |
| Domain | `go.eu.sparkpostmail1.com` |
| Path prefix | `/q/` |
| Dimensions | 1x1px |
| File Type | Transparent GIF |
| HTML tag | `![]()
` with `width="1"` `height="1"` `alt=""` |
**Example pixel (raw HTML source):**
{% code overflow="wrap" %}
```html
```
{% endcode %}
### **How to Detect Tracking Pixels?**
#### → **Reference method: HTML source analysis**
Inspect the raw HTML source of the email. This is the exhaustive method. It identifies all tracking URLs present in the message.
Detection criteria:
* `![]()
` tag with `width="1"` and `height="1"`
* `src` attribute containing the domain `go.eu.sparkpostmail1.com` and path starting with `/q/`
#### → **Applicable tools**
* Email clients with "View source" or "Show original" functionality (e.g., Gmail > three-dot menu > "Show original")
* Command-line: `grep -i 'sparkpostmail1.com/q/'` against the raw `.eml` file
* Privacy/compliance auditing tools that parse MIME and extract `![]()
` src attributes
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.batch.com/guides-and-best-practices/email-deliverability/email-authentication-and-sending-structure/email-open-tracking-and-tracking-pixels/knowing-more-on-tracking-pixels.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.