Salesforce Decode
Salesforcedecode
Back to questions
Data CloudArchitect (Hardest)consentactivationprivacyad-platforms

Enforce marketing consent before Google and Meta audience activation

Real World Scenario

Legal discovered lookalike audiences exported to Meta included profiles who opted out of third-party sharing. Regulators opened inquiry into consent propagation failures.

Expected Answer

• Model consent status as first-class DMO attributes with source timestamp and legal basis • Filter activation queries with explicit consent predicates—never rely on segment naming conventions • Sync consent updates to suppressions lists in ad platforms within defined SLA • Separate segments for first-party owned channels vs third-party ad activation eligibility • Audit activation jobs logging profile count, consent filter version, and export file hash • Implement pre-flight dry-run counts comparing eligible vs blocked profiles before export • Coordinate with legal on jurisdiction-specific consent flags—GDPR, CPRA, state mini-laws

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Handle it in layers. First: Model consent status as first-class DMO attributes with source timestamp and legal basis. If that fails: Filter activation queries with explicit consent predicates—never rely on segment naming conventions. For edge cases in "How do you handle consent captured in offline stor…", Sync consent updates to suppressions lists in ad platforms within defined SLA. Activation without consent architecture is regulatory liability. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Activation without consent architecture is regulatory liability. Consent filters belong in query logic with audit artifacts—not post-export manual checks.