Salesforce Marketing Cloud

Introduction

Didomi allows you to update your Salesforce Marketing Cloud contact attributes with the preferences collected through your preference management platform (PMP).

Implementation

Connection

Didomi connects to Marketing Cloud on your behalf through API calls using Installed packages. You need to fetch your Client id, Client secret and Authentication Base URI.

Options

  • Upsert mode
Please note that the upsert_mode option is always set to true for Salesforce Marketing Cloud. Which means that if the collected consent contains an organization_user_id that has no match in Marketing cloud, Didomi will create a new contact where the contact key value = organization_user_id value.
  • Bidirectional flow: Please note that the bidirectional flow is not supported at the moment.

Mapping

Didomi uses the entity Contact of Marketing Cloud. The PMP purpose/preference/value can be mapped with an attribute within attribute set of your Audience builder. Hence, a properties.id is a combination of attribute set and attribute name separated by a colon : (Cf. the example below).
For Salesforce Marketing Cloud native demographics (Email demographics, MobileConnect demographics..) your contact attributes may not be updated due to missing mandatory information. Here are some non exhaustive examples that you can also check with your Marketing Cloud expert:
  • Email Addresses: contacts with no attached email address will not be updated through Didomi and SalesForce Marketing Cloud integration.
  • MobileConnect Demographics: your contact must include a country code for the Locale value, otherwise the Didomi preference update will not be reflected on your contact
  • MobilePush Demographics: your contact must include an ApplicationID value.
  • GroupConnect: LINE Addresses and LINE Subscriptions fields are required for a contact to be updated with the Didomi preferences.

Configuration

Didomi needs the following configuration items to set up the connection with Marketing Cloud:
Property
Description
Required
Client ID
Client ID issued when you create the API integration in Installed Packages
Yes
Client Secret
Client secret issued when you create the API integration in Installed Packages.
Yes
Url
Url of the account’s authentication endpoint
Yes
Properties
Mapping for properties between Didomi and Salesforce Marketing Cloud
Yes

Example

"config":
{
"client_id": "xxxx-xxxx-xxxx-xxxx",
"client_secret": "xxxx-xxxx-xxxx-xxxx",
"url": "<https://xxx-xxx.auth.marketingcloudapis.com/v2/token>"
"properties": [
{
"id": "Attribute Set:Attribute Name",
"value": "consents_purposes_cookies_preferences_newsletter_channel_email_enabled"
}
]
}
The configuration of the Salesforce Marketing Cloud integration cannot be done in the Didomi Console at the moment. Please reach out to [email protected] to get your Salesforce Marketing Cloud integration configured and provide the elements listed above.
Last modified 3mo ago