# Managing Email Tracking Pixels Consent
## About Tracking Pixels
Tracking pixels are invisible **1x1 transparent images embedded in the HTML** of an email. They have no visual function. When a recipient opens the email, their mail client loads the image from a remote server, triggering an HTTP request that records the open event.
They serve several purposes within the Batch platform:
* **Campaign performance measurement:** tracking open rates to optimize sends, A/B test subject lines, adjust frequency, and select the right channel.
* **Engagement scoring and targeting:** building audience segments based on engagement behavior for CRM personalization.
* **Deliverability monitoring:** detecting inactive profiles to clean lists and adapt sending frequency or stop delivery.
* **Retargeting:** crossing open data with user interests to target profiles on other channels.
To help customers comply with local legislation, especially in the European Union, Batch allows you to control whether tracking pixels are included in emails sent to a given profile.
## Sending Tracking Pixels Consent to Batch
You can share with Batch the consent status at the profile level.
This can be done using the [Profiles API](https://doc.batch.com/developer/api/cep/profiles/update), by passing the consent status in the native attribute `$email_open_tracking_consent`. It accepts two values:
* `granted`
* `denied`
You can review the consent status for a profile using the Profile view:
## Tracking Pixels Management
### → Email Sending
Batch will automatically insert a tracking pixel in emails sent to profiles whose `$email_open_tracking_consent` is set to `granted`.
Profiles with a `denied` value, or no value at all for `$email_open_tracking_consent`, will not receive emails containing a tracking pixel.
When a tracking pixel is not included in an email, the following data is not collected for that send:
* Email opens are not recorded.
* Open-based engagement scores are not updated.
* Audience segments that rely on open behavior will not reflect that send.
* Retargeting logic based on email opens will not be triggered.
### → Bypassing Batch Tracking Pixels Management
If you are certain that you exclusively target users from regions where consent is not required to use tracking pixels, you can bypass Batch's tracking pixel management to always include a tracking pixel in all your emails.
This can be done from your project's settings → Channels → Email.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/managing-email-tracking-pixels-consent.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.