AJO email open tracking cannot be governed by one profile switch

A consent field says a recipient may receive an email, but should that message contain an open-tracking pixel? An Experience League team with hundreds of templates asked for a profile-level switch to suppress the pixel across journeys. The community reply points to message-level open tracking and routing to variants, rather than a documented per-recipient pixel toggle within one message.

Separate permission to send from permission to track

Model the two decisions independently. A person may qualify for a service email while open measurement is restricted. Adobe's email tracking documentation describes the message settings for opens and clicks. Its pixel-tracking guidance discusses opt-out requirements in relevant contexts. Confirm legal requirements with the organization's privacy team; this is a product design question, not a legal conclusion.

Inventory before multiplying templates

Map each journey to its email assets, their open-tracking setting and their consent rule. Identify which messages genuinely require an untracked variant. Centralize common content in approved fragments where possible, then route before the email action to the appropriate tracked or untracked message. A naming convention and ownership register prevent one team from silently reusing a tracked template in an untracked path.

Prove the output, not only the branch

Use test profiles for each consent state. Inspect the resulting email HTML and network requests for the presence of the open pixel, and verify delivery and suppression decisions. Repeat after a template edit or migration. Record how reporting changes when opens are intentionally unavailable; an apparent drop in engagement may be a measurement change.

Adovo’s view

Consent is a property of the experience delivered, not just a field checked before delivery. The control has to survive the last mile into the actual message.