Comment on page
Didomi allows you to update your Sendinblue contact attributes with the preferences collected through your preference management platform (PMP).
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_idto identify and link your profiles on both platforms.
- Upsert mode: You can choose allowing Didomi to create contacts on Sendinblue, by setting
upsert_modeto true. Otherwise, when a consent is collected but the
organization_user_idvalue 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.
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.
You may also use a consent event to add or remove a contact to/from your Sendinblue blacklist. To do so, in the
propertiesobject you need use the id
EMAIL_CAMPAIGNS_SUBSCRIBEDand map it with a purpose or a preference value from your PMP.
Didomi needs the following configuration items to set up the connection with Sendinblue: