Marketing Cloud Next Supported Consent Actions

For Marketing Cloud Next, there are a few methods to manage consent:

1) Manually

• Bulk import of consent data. 
• Manual updates in the Consent Status component on individual records. 

2) End user updates

• Unsubscribe URLs in emails.
• Preference Page.
• Opt outs from SMS/WhatsApp.

3) Specific Flow actions

• Consent Request Action (also labeled Create Consent) in Automation Event-Triggered Flows (includes Form-Triggered Flows)
• Create Consent Action in Data-Cloud Triggered Flows

Unsupported Consent updates

The below are unsupported methods for updating consent. Note that this list may not be exhaustive and there may be other unsupported methods. Refer to the earlier section for supported methods. 

• Any Flow Type other than Data Cloud Triggered Flow or Automation Event-Triggered Flow (only these types of flows have the supported consent action, see above section). 
• The below Flow Actions are unsupported:
  • MessagingConsent.MessagingConsent Flow Action
  • MessagingConsentV2.MessagingConsent Flow Action
• Data Cloud Batch Data Transforms to update a DLO that is mapped to the Communication Subscription Consent DMO.
• Mapping consent values through via a data stream into Communication Subscription Consent DMO.

If you use any above methods to update consent:

• Consent may not respected correctly during messaging sends even though it appears that updates were saved in the Communication Subscription Consent DMO.
  • In some cases, this means that an email may not send even though an email address appears opted in. 
  • In other cases, this may mean that an email may send inadvertently, even though the email address appears opted out.
• The consent in the Communication Subscription Consent DMO may not align the consent showing on individual records in the Consent Status component.