[Beta]{class="badge informative"}
Didomi
Didomi is a consent and preference management platform that helps organizations collect, manage, and enforce user choices regarding personal data across websites, apps, and internal tools.
ÃÛ¶¹ÊÓƵ Experience Platform supports ingesting data from a wide range of external systems including cloud storage, databases, and applications like Didomi through a system of source connectors. Use sources to authenticate external systems, manage data flow into Experience Platform, and ensure consistent and structured ingestion of your customer data.
Use the Didomi source to stream real-time user consent and preferences data from the Didomi consent and preference management platform into Experience Platform. Through the Didomi source, you can centralize and act on consent data in Experience Platform, thereby keeping your customer profiles and downstream workflows compliant and up to date.
Prerequisites
Complete the prerequisite steps outlined below to successfully connect your Didomi account to Experience Platform.
IP address allowlist
You must add region-specific IP addresses to your allowlist prior to connecting your sources to Experience Platform. For more information, read the guide on allowlisting IP addresses to connect to Experience Platform for more information.
Configure permissions on Experience Platform
You must have both View Sources and Manage Sources permissions enabled for your account in order to connect your Didomi account to Experience Platform. Contact your product administrator to obtain the necessary permissions. For more information, read the access control UI guide.
Gather ÃÛ¶¹ÊÓƵ API Credentials
To securely connect Didomi to Experience Platform, you must authenticate using your ÃÛ¶¹ÊÓƵ API credentials. These credentials are essential for setting up the webhook and configuring data ingestion.
Read the guide on getting started with Experience Platform APIs for information on how to successfully make calls to Experience Platform APIs.
Create an Experience Platform schema
An Experience Data Model (XDM) schema defines the structure of the data you’ll be sending from Didomi (e.g., user IDs, consent purposes) to Experience Platform.
To create a schema, select Schemas in the left-navigation of the Experience Platform UI and select Create schema. Next, select Standard as your schema type and then select Manual to manually create your fields. Select a base class for your schema and provide a name for your schema.
Once created, update the schema by adding any of your required fields. Ensure that at least one field is an Identity field to inform Experience Platform about your primary identity values. Finally, ensure that you enable the Profile toggle in order to successfully store your data.
For more information, read the guide on creating schemas in the UI.
Create a dataset
A dataset in Experience Platform is used to store incoming data based on the schema that you define.
To create a dataset, select Datasets in the left-navigation of the Experience Platform UI and then select Create dataset. Next, select Create dataset from schema and then select your schema to associate with your new dataset.
Configure the HTTP Webhook on the Didomi console
Webhooks allow you to subscribe to events triggered on the Didomi platform when users interact with their consent preferences. When a relevant event occurs — for example, when a user gives or withdraws consent — Didomi sends a real-time HTTP POST request containing a JSON payload to your configured webhook endpoint.
To ensure compatibility with Experience Platform, your webhook must meet the following requirements.
d8f3b2e1-4c9a-4a7f-9b2e-8f1c3d2a1b6eclient_credentials.client_credentialsopenid,ÃÛ¶¹ÊÓƵID,read_organizations,additional_info.projectedProductContext,session{"Content-type": "application/x-www-form-urlencoded"}https://ims-na1.adobelogin.com/ims/token/v3https://dcs.adobedc.net/collection/your-adobe-endpoint-idNext, configure the following options for your webhook.
x-adobe-flow-id. You can retrieve this value after your dataflow is created.{"Content-Type": "application/json", "Cache-Control": "no-cache", "x-adobe-flow-id": "{DATAFLOW_ID}"}event.* or user.*) that should trigger the webhook. Use event.* to track consent or preference changes, and use user.* to track user profile updates. This selection is required to ensure that only compatible events are sent to ÃÛ¶¹ÊÓƵ. ÃÛ¶¹ÊÓƵ supports only one schema per dataflow, so selecting both event types can cause ingestion errors.The list of supported event types are:
Event.createdEvent.updatedEvent.deletedUser.createdUser.updatedUser.deleted
Download the sample payload file download-the-sample-payload-file
Based on your selected event group, download the appropriate sample payload file directly from the Didomi Console. This file represents the structure of the data and will be used during the schema and mapping steps in ÃÛ¶¹ÊÓƵ.
event.*event.createdevent.* eventsuser.*user.createduser.* eventsConnect your Didomi account to Experience Platform
Read the guide on connecting Didomi to Experience Platform to learn how to create a source connection and ingest consent and preferences data from Didomi into Experience Platform.