Under GDPR, which combination of settings helps ensure subscriber tracking choices are respected in MC Connect?

• A. Enable DoNotTrack Attribute on each Subscriber; Create a DoNotTrack Preference Attribute
• B. Enable DoNotTrack Attribute on each Subscriber only
• C. Create a DoNotTrack Preference Attribute only
• D. DoNotTrack is not supported

Answer: (A)

To respect GDPR-tracked consent in MC Connect, you need both a per-subscriber DoNotTrack indicator and a DoNotTrack Preference attribute. The DoNotTrack Attribute on each subscriber acts as the enforcement signal: when it’s set, tracking for that subscriber is suppressed across data collection and integrations. The DoNotTrack Preference Attribute provides a user-facing, auditable record of the choice, which can be surfaced to the subscriber and synchronized with external systems. Having both allows you to enforce the opt-out while also maintaining a clear, governed record of the user’s preference that can be used for reporting and compliance. Without the per-subscriber signal, tracking cannot be reliably blocked; without the preference attribute, there’s no explicit, trackable record of the user’s choice. DoNotTrack is supported in this context, so stating that it isn’t would be inaccurate.