13 July 2026 Mapp Engage now supports Email Tracking Consent, a way to record and respect each contact's consent for email open and click tracking, controlled per contact.
This is particularly relevant where email tracking may require the recipient's prior consent, such as in France and Italy — but the same mechanism is available to any sender who wants per-contact control over tracking.
Key Benefits
Contact-level tracking consent
Record whether each contact has consented to email open and click tracking, as a single source of truth across your messages.
Consent respected automatically
When a contact declines, their opens and clicks are no longer tracked, while the links in the message keep working normally.
Per-message override
Enforce tracking for messages that have to be measured regardless of consent, with responsibility for the lawful basis remaining with you.
How Does It Work?
Each contact has a
tracking_consentvalue with four states: granted, denied, withdrawn, or unknown. It is evaluated at send-out and covers both open and click tracking.Contacts who have denied or withdrawn consent receive no tracking pixel; the links in the message still work normally for the recipient.
If no value is stored (unknown), tracking stays on by default, so existing reporting does not change. This default can be switched off — contact your CSM to activate that option.
The value can be set via contact import and the Contact Update API, and exported for auditing. See Setting the tracking_consent attribute for the steps.
A per-message Tracking Override can enforce tracking regardless of a contact's consent state.
Availability
Email Tracking Consent is available to Mapp Engage users as of 13 July 2026. To understand what is changing, how the consent states work, and how to prepare your setup, see Email Tracking Consent.