> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Consent Attribute and Open Tracking Pixel

> Understand the Email Open Tracking Consent attribute, how to update it, and how it controls whether the open tracking pixel is included in an email.

This article explains the behavior of the **Open tracking consent** setting, exactly when the open tracking pixel and consent management link are included in an email. For how to configure the setting itself, refer to Open tracking consent under [Email General Settings](/docs/user-guide/campaigns-and-channels/email/getting-started-with-email/configure-email-channel#general-settings-tab).

## How the Tracking Pixel Actually Works

An email open tracking pixel is a single-pixel, transparent image embedded in the email body. When a recipient opens the email, their mail client loads this image in the background, which reports the open back to the sender. This is the mechanism behind open-rate tracking.

In countries where regulators require the recipient's consent before an open tracking pixel can be included, its inclusion must be based on that consent, and recipients need a straightforward way to opt out of being tracked.

## How the Consent Attribute Controls Tracking

<img src="https://mintcdn.com/moengage/q8wg1kf74EEj29AV/images/how_consent_works.png?fit=max&auto=format&n=q8wg1kf74EEj29AV&q=85&s=2af4fcfb537428f959ae485d04f0fadc" alt="how_consent_works.png" width="1454" height="602" data-path="images/how_consent_works.png" />

For recipients whose country matches one of the regulated countries, or when you've selected **Use consent attribute** for missing-country cases (while configuring), MoEngage checks the **Email Open Tracking Consent** attribute to decide whether to include the tracking pixel.

The table below covers the possible combinations of your settings and a recipient's data, and the resulting behavior for that recipient's email.

| Open Tracking Consent Toggle | Regulated Countries (config) | Missing Country Setting (config) | Recipient's Country | Recipient's Consent Attribute | Tracking Pixel | Consent Link |
| ---------------------------- | ---------------------------- | -------------------------------- | ------------------- | ----------------------------- | -------------- | ------------ |
| Disabled                     | N/A                          | N/A                              | N/A                 | N/A                           | Included       | Not included |
| Enabled                      | France, Italy                | N/A                              | France              | TRUE                          | Included       | Included     |
| Enabled                      | France, Italy                | N/A                              | France              | FALSE                         | Not included   | Included     |
| Enabled                      | France, Italy                | N/A                              | India               | N/A                           | Included       | Not included |
| Enabled                      | France, Italy                | Look at consent attribute        | Not present         | TRUE                          | Included       | Included     |
| Enabled                      | France, Italy                | Look at consent attribute        | Not present         | FALSE                         | Not included   | Included     |

<Info>
  * France and Italy are used here only as example values for **Regulated Countries**. The same logic applies to whichever countries you configure.
  * In the absence of an explicit opt-in, a recipient is always treated as opted out. This is a regulatory requirement and consent cannot be assumed or defaulted to "yes." Make sure this attribute is being updated through one of the supported paths below before you rely on it.
  * If a recipient's consent status changes to opted out after an email was sent, MoEngage stops attributing opens to that recipient going forward. This applies even if the tracking pixel was already included in that email, whether because the recipient was opted in at send time or because the email was sent before this feature was enabled.
</Info>

## Update the Consent Attribute

You can update this attribute using:

* User Import
* Server-to-Server (S2S) Data API
* The consent management page, where recipients can set their own preference

## Consent Management Link and Page

<img src="https://mintcdn.com/moengage/rbqymHttjuNA5dTB/images/consent_page1.png?fit=max&auto=format&n=rbqymHttjuNA5dTB&q=85&s=e9124e6a6dae31674848326ebf306665" alt="consent_page1.png" width="1051" height="238" data-path="images/consent_page1.png" />

* When open tracking consent is enabled, MoEngage inserts a consent management link in the footer of emails sent to recipients in your regulated countries, based on the specific combination of settings and recipient data described in the table in [How the Consent Attribute Controls Tracking](/docs/user-guide/campaigns-and-channels/email/getting-started-with-email/consent-attribute-and-open-tracking-pixel#how-the-consent-attribute-controls-tracking) section above. This link is separate from your unsubscribe link. Recipients who use it to opt out of tracking continue to receive your emails as normal; they just won't be tracked for opens. The link takes recipients to a MoEngage-hosted consent page where they can view and update their open tracking preference.
* MoEngage raises an **Email Open Tracking Consent Updated** event on a user's profile only when the attribute is updated through the MoEngage-hosted consent management page. This means the event is raised when the recipient clicks the consent link in an email, lands on the page, and updates their preference there.
* If you update the **Email Open Tracking Consent** attribute directly through the Server-to-Server (S2S) API or User Import, no event is raised. MoEngage only generates this event for changes made through the consent management page flow; it has no way to detect an attribute being overwritten directly. If you need your own record of such changes, you'll need to track them on your end.
* The consent management page is unbranded and available only in English. There's no support for using a custom or self-hosted consent page.
