Didomi - Developers documentation
  • Introduction
  • SDKs
    • Introduction
    • Web SDK
      • Getting started
      • Tags and vendors management
        • Tags management
          • Events & Variables
            • Deprecated
            • Custom events
          • Tag managers
            • Adobe Launch/DTM
            • Eulerian
            • Google Tag Manager
              • Configure the Didomi / GTM integration
              • Didomi's GTM template
            • Tealium
            • Other tag managers
        • Custom Didomi <script> tags
        • Third-party integrations
          • Google Ad Manager / AdSense
            • GDPR via Non-Personalized Ads
              • Share consent and load/refresh ads
              • Share consent without loading or refreshing ads
            • US states laws
          • Google Consent Mode V2
          • Kameleoon
          • Piano Analytics (AT Internet)
          • Prebid
            • GDPR via IAB TCF
            • US states laws
          • Salesforce DMP (Krux)
        • IAB frameworks
        • Programmatic API
      • Configuration
        • Bots (SEO & Performance tools)
        • Configuration by URL
        • Cookies and storage
        • Custom domains for events
        • Notice
          • Behavior
          • Interactions
          • Look and feel
        • Preferences
        • Theme
      • AB tests
      • Custom domain
        • Domain delegation
        • Reverse proxy
      • Share consents between domains
      • Share consents across devices
      • Pass user choices in query string
      • Serve Didomi assets from your domain
      • Reference
        • API
          • Deprecated
        • Events
      • Performance
      • Versions
    • Mobile and TV SDKs
      • Android and Android TV
        • Setup
        • Logging
        • Reference
          • API
            • Deprecated
          • Events
        • Versions
      • iOS and tvOS
        • Setup
        • Logging
        • App Tracking Transparency (iOS 14.5+)
        • Reference
          • API
            • Deprecated
          • Events
        • Versions
      • Unity
        • Setup
        • Reference
        • Versions
        • Troubleshooting
      • React Native
        • Setup
        • Reference
          • Deprecated
        • Versions
      • Flutter
        • Setup
        • Reference
        • Versions
      • Consent notice
        • Getting started
        • Customize the notice
        • Customize the preferences popup
        • Customize the theme & UI
        • Load notice by ID
      • Third-party SDKs
      • Share consents across devices
      • Share consent with WebViews
      • Google Consent Mode v2
      • FAQ
    • AMP SDK
      • Blocking Behaviors
        • Load immediately on page load
        • Load only after consent (positive or negative)
        • Load only after positive consent
      • Consent status for vendors
    • Help & Support
  • API
    • Introduction
      • Authentication
      • Errors
      • Pagination
      • Filters
      • Caching
      • Rate limiting
      • Quotas
      • Translations
    • Data Manager
      • Regulations
      • Configuration Tree
      • Purposes
        • Purposes & Vendors Numerical IDs
      • Preferences Library
      • User Rights
    • Widgets
      • Consent notices
        • Notices
        • Configurations
        • Multi-Regulation Configurations
          • Migration of Existing Notices and API Updates
        • Deployments
        • Tutorials
          • Create and publish a consent notice
          • Create and publish a multi-regulation consent notice
      • Privacy widgets
        • Create a widget
        • Retrieve widgets
        • Edit a widget
          • Content & Design
            • Themes & Shapes
            • Components
              • auth
              • dsar_form
              • footer
              • header
              • preference
              • preference_value
              • save
              • section
              • sections
            • Options
          • Purposes & preferences
          • Settings
        • Deploy a Widget
          • Use your own subdomain
          • Use your own domain
          • Implement an embeddable widget on your website
        • Authentication
          • Manage authentication providers
          • Authenticate your end-user
        • Archive a widget
        • Headless widgets
          • Public Methods
          • Custom elements
          • Custom events
          • Event listeners
        • Tutorial
          • Launch a Preference Center from a mobile app
    • Compliance Reports
      • Properties
      • Reports
      • CSV format reference
      • Websites
    • Consents and Preferences
      • Events
        • Generate IAB TCF consent string
      • Links
      • Proofs
      • Tokens
      • Secrets
      • Users
      • Tutorial
        • Collect and operate data
    • Privacy Requests
      • Requests
      • Notes
      • Links
      • Emails
  • Integrations
    • Introduction
      • Quotas
    • Generic integrations
      • Batch export
        • Destinations
          • AWS S3 Bucket (owned by Didomi)
          • GCP Storage Bucket
        • Exported data
          • Notices consents
        • Logs
      • Webhooks
      • Batch import
      • Analytics export
        • Destinations
          • AWS S3 Bucket (owned by Didomi)
          • GCP Storage Bucket
    • Third-party apps
      • CMP integrations
        • Didomi-mParticle integration for your CMP
        • Deploy Didomi’s SDK for your Adobe Commerce website
      • Preference Management Platform integrations
        • Actito
        • Adobe Campaign Classic
        • Adobe Experience Cloud
        • Adobe Marketo Engage
        • Adobe Source Connector
        • Braze
        • Dotdigital
        • Hubspot
        • Mailchimp
        • Microsoft Dynamics 365
        • Salesforce Marketing Cloud
        • Salesforce Sales & Service Cloud
        • Selligent
        • Brevo (ex Sendinblue)
    • Tutorials
      • Configure a HTTP webhook
      • Configure a batch export
      • Configure an analytics export
    • Emailing
      • Configurations
        • Actito Email
        • Actito SMS
        • Adobe Campaign Classic
        • Adobe Campaign Standard
      • Emails
        • Templates
        • Manage your templates
Powered by GitBook
On this page
  • Introduction
  • Implementation
  • Connection
  • Options
  • Mapping
  • Configuration
  • API Example
  1. Integrations
  2. Third-party apps
  3. Preference Management Platform integrations

Adobe Experience Cloud

PreviousAdobe Campaign ClassicNextAdobe Marketo Engage

Last updated 11 months ago

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 .

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

Property
Description
Required

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

{
    "type_id": "adobe-experience-cloud",
    "authentication": {
        "client_id": "your_client_id",
        "client_secret": "your_client_secret",
        "api_key": "your_adobe_api_key",
    },
    "properties": {
        "organization_id": "your_adobe_organization_id",
        "dataflow_endpoint":"your_adobe_dataflow_endpoint",
        "dataflow_id":"your_adobe_dataflow_id",
	"schema_id": "your_schema_id",
	"dataset_id":"your_adobe_dataset_id",
	"user_identifier": ["email"]
    },
    "mappings": [
        {
	    "id": "adobe_profile_attribute_logical_name",
	    "value": "consents_purposes_newsletter_enabled"
	}
    ],
    "upsert_mode": true
}

Client ID of your project created in

Client secret of your project created in

API key of your project created in

Your Adobe Organization ID (from your )

The profile schema defined in

The ID of your HTTP API Dataflow in

The endpoint of your HTTP API Dataflow in

The ID of the Dataset created in

The configuration of the Adobe Experience Cloud integration can be done in the . First please reach out to to get the integration's premium feature activated.

Learn how to configure Didomi-Adobe CDP integration in the Didomi Console .

this Help center doc
Didomi Console
support@didomi.io
in this help center documentation
Adobe Experience Console
Adobe Experience Console
Adobe Experience Console
Adobe Experience Console
Adobe Experience Platform
Adobe Experience Platform
Adobe Experience Platform
Adobe Experience Platform