Adobe Experience Cloud
Introduction
Didomi allows you to sync user preferences to your Adobe CDP through a server to server native integration with Adobe Experience Cloud.
Implementation
Connection
Didomi connects to Adobe Experience Cloud CDP on your behalf using OAuth2, hence the need to provide the following parameters:
Client ID
Client secret
API key
In addition to that, and in order to target the exact workflow in your CDP you will also need to provide the following parameters:
Your Adobe Experience organization ID
Your schema ID
Your Dataflow ID and endpoint
Your Dataset ID
Learn more in this Help center doc.
Options
Upsert mode
You can choose allowing Didomi to create contact in Adobe Experience Cloud, by setting upsert_mode
to true. Otherwise, when a consent is collected but the organization_user_id
value does not match with any contact in Adobe, the consent update will not be propagated.
Bidirectional flow
Please note that the bidirectional flow is not supported at the moment.
Mapping
Didomi uses the entity profile of Adobe CDP and sends the profile attribute property when updating a profile. Hence consent events are mapped to Microsoft Dataverse's contact attributes.
Configuration
Client ID
Yes
Client secret
Yes
API key
Yes
Organization ID
Yes
Schema ID
Yes
Dataflow ID
Yes
Dataflow endpoint
Yes
Dataset ID
Yes
User identifier
Identifier property for users. Options: email
, id
, personID
.
Yes
Upsert mode
By setting upsert_mode to true you allow Didomi to create contacts in Adobe CDP
No, Default value = false
Mappings
Mapping for properties between Didomi and Adobe CDP
Yes
API Example
The configuration of the Adobe Experience Cloud integration can be done in the Didomi Console. First please reach out to support@didomi.io to get the integration's premium feature activated.
Learn how to configure Didomi-Adobe CDP integration in the Didomi Console in this help center documentation.
Last updated