Hello,
I am trying to understand the Consent Data Model in Data Cloud. I'd studied knowledge articles on Privacy DMOs, but I couldn't understand how Data Cloud and MCA works with Organization's In-house Consent Management service.
I have 2 to 3 Data Streams bringing in the Email Marketing Consent of Subscribers, identified by their email address. I'd mapped ContactPoint Email, Comm. Subscription Consent, Individual and Party Objects.
Consent Id is set to Email + Subscription + Subscription Channel ID
Individual/Party ID is set to unique ID for 3 data streams.
Comm Sub. Consent DMO captures the Consent Changes and Audit trail as new data flows into the system.
While building the segment and adding rules, the segment doesn't look at latest consent rather all old records associated to the subscriber.
Say, the Consent DMO has OptIn and OptOut Records of a subscriber, say OptOut is the latest transaction.
If a build a segment by Consent Status as "OPT_IN", the subscriber with latest optOut status pops up in the segment.
How do I ensure that DC/MCA always checks the latest privacy consent of a subscriber? Am I missing something here? Any resource/documentation on this topic would be highly appreciated.
Hello Gokul,
This is a super common confusion when working with the Consent Data Model in Data Cloud. What’s happening is that your segment logic is reading all historical consent records, not just the most recent one, so it’s pulling in both opt-ins and opt-outs. To fix this, you need to make sure Data Cloud is using the latest consent transaction per subscriber. Usually, this means setting up a unified or calculated field that identifies the most recent consent record — for example, filtering by the latest Consent Date or Modified Date in your segment logic. In your mapping, ensure that the Comm Subscription Consent DMO has the right relationship to the Individual or Contact Point Email, and that your segment filter specifically targets the most recent record (like “latest consent status = OPT_IN”). MCA/Data Cloud doesn’t automatically dedupe consent history, so you have to add that “latest” logic manually, either through a calculated field or within your segmentation rule. Salesforce’s docs on “Consent and Preference Management in Data Cloud” go into this detail — definitely worth checking out for examples on using the Most Recent Record pattern for consent segments.
