Data CloudArchitect (Hardest)consentgdpractivationsegmentation
Design consent-aware segmentation for GDPR marketing activation
Real World Scenario
Global brand activates Data Cloud segments to Meta and email ESP; legal flags risk of targeting users who withdrew marketing consent in one country but not another.
Expected Answer
• Model consent as first-class attributes on unified individual with jurisdiction and channel granularity
• Apply consent filters at segment definition layer not only at activation export
• Use calculated insights for consent expiry and re-permission windows
• Activation targets must receive only consent-qualified fields — minimize PII surface
• Audit trail linking segment version to activation job Id
• Test edge cases: consent update mid-activation batch
• Document lawful basis per segment for DPO review
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Model consent as first-class attributes on unified individual with jurisdiction and channel granularity Also consider: Apply consent filters at segment definition layer not only at activation export In practice: Use calculated insights for consent expiry and re-permission windows Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Consent is not a checkbox on export — bake into segment logic or face regulatory activation stops.