Skip to main content

Hi everyone,

I am trying to better understand how Marketing Cloud Next (Growth/Advanced) consent management is supposed to work with Contact Point Emails and the Consent Status component.

On Leads, we have:

  • Email
  • Secondary Email

Both of these automatically appear in the Consent Status component where subscription consent statuses for different Marketing Cloud Next subscription types are displayed. 

 

How should Contact Point Emails be correctly tied to Marketing Cloud Next subscription consents?

 

 

consent statuses.png

 

 

 

When looking at the related Individual record, I can also see the Contact Point Emails related list, where additional email addresses can be manually added. 

 

individual contact point emails.png

 

 

Observed behavior:

  • If I populate Primary Email or Secondary Email on the Lead, those email addresses are automatically created under Contact Point Emails.
  • However, if I manually add a new Contact Point Email on the Individual, it does NOT automatically appear in the Consent Status component and does not seem tied to MCN subscription consents.

I found articles suggesting that I should create a N:1 relationship between:

  • Communication Subscription Consent DMO 

    and

  • Contact Point Email DMO

For example: 

Communication Subscription Consent.ContactPointId → Contact Point

Email.Id

However, Salesforce documentation here: 

Salesforce Help Article

mentions under “Unsupported Consent updates”: 

“Mapping consent values through via a data stream into Communication Subscription Consent DMO.”

 

This confused me because it sounds like directly populating or syncing Communication Subscription Consent may not be supported. 

 

Questions:

  1. What is the correct architecture/pattern for tying additional Contact Point Emails to Marketing Cloud Next subscription consents?
  2. Should manually-created Contact Point Emails automatically appear in the Consent Status component, or is that component only tied to standard Lead email fields?
  3. Is there a supported way to associate Communication Subscription Consent records with Contact Point Emails in Data Cloud?
  4. If yes, which exact fields/relationships should be mapped?
  5. Is there some additional process or activation required for manually-added Contact Point Emails to become consent-aware in MCN?

Trying to understand the intended design here because currently there seems to be a disconnect between:

  • Contact Point Emails
  • Consent Status component
  • Communication Subscription Consent DMO
1 answer
  1. May 11, 11:32 AM

    @Zuzanna Jarczynska

     

    Hi Zuzanna, 

    First, let's state that the Consent is based on the Email address itself, not the related Contact Point. Although a blackbox, I'd the Consent component  gets all email-type fields for the current Lead or Contact and then queries the Communication Subscription Consent DMO. 

    To your points 

    1- See  here

    2- This relationship is handy, and almost mandatory for segmentation purposes. 

    3- Nope, relies on email address. 

    4- NA 

    5- Nope. 

    Also you mentioned the unusupported methods to update the consent status. It is related to the actual cache used. See here

     

    Hope this helps 😎

0/9000