Adobe Source Connector

Overview

The Didomi Source Connector enables you to stream real-time user consent and preference data from the Didomi Consent & Preference Management Platform into Adobe Experience Platform (AEP). Adobe 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. These connectors let you authenticate external systems, manage data flow into Adobe, and ensure consistent and structured ingestion of customer data. This connector allows you to centralize and act on consent data in Adobe Experience Platform, keeping your customer profiles and downstream workflows compliant and up to date.

Prerequisites

Before connecting the Didomi Source Connector to Adobe Experience Platform, you must complete the following setup steps:

1. Create a Schema and Dataset in Adobe

Adobe Experience Platform uses schemas and datasets to define and store structured data.

• Schemas define the structure of the data you’ll be sending from Didomi (e.g., user IDs, consent purposes).

• Datasets are used to store the incoming data based on the schema you define.

You will create both of these using the Adobe Experience Platform UI in the next section of this guide.

⚠️ Note: If you already have a schema and dataset that you plan to use, you can skip these steps.

2. Gather Adobe API Credentials

To securely connect Didomi with Adobe Experience Platform, you will need to authenticate using Adobe API credentials. These values are required to set up the webhook and configure data ingestion.

For full instructions on how to retrieve these values, refer to the official Adobe guide:

Create a schema

1. Navigate to the Schemas tab in the Adobe Console.

2. Choose the option to manually create fields.

3. Select the type of Profile Schema you are registering.

4. Provide a name for the schema and complete the creation.

5. After creation, update the schema by adding any required fields.

6. Ensure that at least one field is tagged as an identity so Adobe can recognize the primary value.

7. Enable Profile for the schema — this is essential for storing data.

Create dataset

1. Navigate to the Datasets section in Adobe Experience Platform.

2. Select the option to create a dataset using the previously created schema.

3. Once the dataset is created, you can proceed with configuring the source connector.

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 Adobe Experience Platform, your webhook must meet the following requirements:

1. Navigate to the Didomi Marketplace.

2. Select the option to Configure Webhook.

3. Add the webhook configuration.

Field	Description	Required	Value
Client Secret	Secret key associated with your Adobe API credentials.	✅	YOUR_ADOBE_CLIENT_SECRET
API Key	Public API key used to authenticate requests to Adobe services.	✅	YOUR_ADOBE_API_KEY
Grant Type	Must always be set to client_credentials.	✅	client_credentials
Scope	The authorization scopes.	✅	openid,AdobeID,read_organizations,additional_info.projectedProductContext,session
Authentication Header	Additional headers required for the Adobe token request.	✅	{"Content-type": "application/x-www-form-urlencoded"}
Token URL	Adobe token endpoint.	✅	https://ims-na1.adobelogin.com/ims/token/v3
Endpoint URL	The final Adobe connector URL (provided at the end of the setup).	✅	https://dcs.adobedc.net/collection/your-adobe-endpoint-id

1. Configure the webhook options.

Field	Description	Required	Value
Request Headers	Custom headers for the webhook. Make sure to include the x-adobe-flow-id (provided later).	✅	{"Content-Type": "application/json", "Cache-Control": "no-cache", "x-adobe-flow-id": "your-flow-id"}
Flatten	Must be checked. Ensures that the webhook data is sent as a flat object.	✅	Enabled
Event Types	Select the specific group of Didomi events (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 Adobe. Adobe supports only one schema per dataflow, so selecting both event types can cause ingestion errors. You can find a full list of supported event types here.	✅	Event.created, Event.updated, and Event.deleted — or User.created, User.updated, and User.deleted

1. 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 Adobe.

Event Group	Sample File to Download	Filtering Option
event.*	Download a sample for event.created	Filter only for event.* events
user.*	Download a sample for user.created	Filter only for user.* events

Connect to Didomi Source Connector

In the Experience Platform UI, select Sources from the left navigation to access the catalog of sources available in Experience Platform. Find the Didomi source card and click on Add data.

Add the source data schema

In the Experience Platform UI, add the schema for the source data using the file downloaded in the previous step.

Configure the dataflow details

1. In the Experience Platform UI, select the dataset created in the previous step.

2. Make sure the Profile dataset option is enabled.

Configure the mapping

In the Adobe Experience Platform UI, you can configure the mapping between the source data from Didomi and the target dataset in Experience Platform.

The mapping is used specifically to transfer purpose data from Didomi into the Adobe Experience Platform dataset. These purposes represent the user's consent choices (e.g., for analytics, personalization, advertising, etc.) and are the only accepted mapping fields in this integration.

As mentioned in the previous step, you should have downloaded a sample webhook payload from the Didomi webhook settings. This file represents the structure of the data that Didomi sends and serves as the mapping schema in the Adobe Experience Platform UI. Use this file to map each Didomi purpose to the appropriate fields in your Adobe dataset.

Finish the configuration on Adobe

In the Experience Platform UI, after completing the configuration, you can review the configuration parameters that were missing from the initial webhook setup. Once these values are available, return to Didomi and update the webhook configuration.

Update the webhook configuration

After you finish the configuration on Adobe, update the webhook configuration with the following values:

• Endpoint URL: The streaming endpoint provided by Adobe.

• Adobe Flow ID: The flow ID shown during the final step of the Adobe setup.

Once this is complete, Didomi will begin sending PMP/CMP events through the integration, and the data will be stored in your Adobe dataset.