Dotdigital

Introduction

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

Implementation

Connection

Didomi connects to Dotdigital on your behalf through an API user that you can create by following these steps. You can then configure a username and password in the Didomi integration.

Options

• Upsert mode: You can choose allowing Didomi to create contacts on Dotdigital, 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 Dotdigital, the consent update will not be propagated to Dotdigital.

• Bidirectional flow: Please note that the bidirectional flow is not supported at the moment.

Mapping

Didomi uses the entity contact of Dotdigital and sends the attributes property when updating a contact, hence consent events are mapped to the contact attributes.

Configuration

Didomi needs the following configuration items to set up the connection with Dotdigital:

Property	Description	Required
Username	Your Dotdigital API username	Yes
Password	Your Dotdigital API user password	Yes
Endpoint URL	Make sure you add the regional API endpoint as described here	Yes
Upsert mode	By setting upsert_mode to true you allow Didomi to create contacts in Dotdigital	No Default value = false
Mappings	List of properties to match between Didomi and Dotdigital	Yes

Example

{
    "type_id": "dotdigital",
    "authentication": {
        "url": "your_api_url",
        "username": "your_api_username",
        "password": "your_api_user_password"
    },
    "properties": {},
    "mappings": [
        {
	    "id": "dotdigital_contact_attribute",
	    "value": "consents_purposes_newsletter_enabled"
        }
    ],
    "upsert_mode": true
}

The configuration of the Dotdigital integration can be done in the Didomi Console. First please reach out to [e-mail] to get the integration's premium feature activated.