Sendinblue

Introduction

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

Implementation

Connection

Didomi connects to Sendinblue on your behalf through API calls using an API key. Therefore, every time preferences are collected using the Didomi Platform, it triggers an event that updates the attributes of your Sendinblue profiles. You can use the Didomi user's property organization_user_id to identify and link your profiles on both platforms.

Mapping

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

Options

  • Upsert mode: You can choose allowing Didomi to create contacts on Sendinblue, 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 Sendinblue, the consent update will not be propagated to Sendinblue.
  • Bidirectional flow: Please note that the bidirectional flow is not supported at the moment.

Configuration

Didomi needs the following configuration items to set up the connection with Sendinblue:
Property
Description
Required
Upsert mode
By setting upsert_mode to true you allow Didomi to create contacts on Sendinblue.
No Default value = false
API Key
API key of your Sendinblue to connect to the Sendinblue API
Yes
Properties
List of properties to match between Didomi and Sendinblue
Yes

Example

1
{
2
"upsert_mode": true,
3
"config": {
4
"api_key": "api_key",
5
"properties": [{
6
"id": "EMAIL_NOTIFICATION",
7
"value": "consents_purposes_newsletter_enabled"
8
}]
9
}
10
}
Copied!
The configuration of the Sendinblue integration cannot be done in the Didomi Console at the moment. Please reach out to [email protected] to get your Sendinblue integration configured and provide the elements listed above.