Understanding the Difference
The MessagingConsentV2.MessagingConsent activity is a new feature in Salesforce Marketing Cloud that allows for the registration of consents. However, as noted in the Salesforce documentation, it is recommended to use the Consent Request or Create Consent activities instead.
The root cause of the confusion is that MessagingConsentV2.MessagingConsent only writes to the Communication Subscription Consent DMO, but does not update the cache, which is the source of truth for consents.
This means that while MessagingConsentV2.MessagingConsent may appear to be registering consents, it is not actually updating the cache, which can lead to inconsistencies and errors.
Using the Preferred Methods
To register consents in Data Cloud, it is recommended to use the Consent Request or Create Consent activities. These activities handle the cache and ensure that consents are properly registered and updated.
By using the preferred methods, you can ensure that your consents are properly registered and updated, and that you are in compliance with relevant regulations.
Best Practices
Checklist for Registering Consents in Data Cloud
- Use the Consent Request or Create Consent activities to register consents.
- Ensure that the cache is updated when registering consents.
- Use the Communication Subscription Consent DMO to store consents.
- Regularly review and update your consent registration processes to ensure compliance with relevant regulations.
- Test your consent registration processes to ensure they are working correctly.
What is the difference between MessagingConsentV2.MessagingConsent and Consent Request?
MessagingConsentV2.MessagingConsent only writes to the Communication Subscription Consent DMO, while Consent Request handles the cache and updates the DMO.
Can I use MessagingConsentV2.MessagingConsent to register consents in Data Cloud?
While it is possible to use MessagingConsentV2.MessagingConsent, it is not the preferred method as it does not handle the cache.
What are the recommended activities for registering consents in Data Cloud?
The recommended activities are Consent Request and Create Consent.
How do I ensure that my consents are properly registered and updated?
By using the preferred methods and regularly reviewing and updating your consent registration processes.
Need help shipping this in production?
Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.
