Actito

Introduction

Didomi allows you to synchronize your Actito profiles subscriptions with the preferences collected through Didomi consent events.

Implementation

Connection

Didomi connects to your Actito account through an API Key to update the subscriptions of an Actito profile every time preferences are collected using the Didomi Platform. Users are matched between Didomi and Actito using the Didomi user's organization_user_id property.

Options

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

• Bidirectional flow: Actito can also be integrated in a bi-directional fashion by setting up a webhook on the Actito portal pointing to webhooks.didomi.io. This will sync Didomi with your Actito profile updates.

Mapping

Didomi uses the entity profile of Actito and sends the subscription update. Hence consent events are mapped to the subscription properties of Actito profiles.

Important: This integration will only synchronize the subscription properties present at the moment of the activation. If a new subscription property is added to Actito, make sure to update your Didomi integration accordingly.

Configuration

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

Property	Description	Required
Upsert mode	By setting upsert_mode to true you allow Didomi to create contacts in Actito	No, Default value = false
API Key	API key of the account to connect to the Actito servers	Yes
Entity ID	ID of the Actito entity of the account.	Yes
Table name	Name of the Actito table where profiles are stored	Yes
User unique key	A unique user attribute to identify your users	Yes
Mappings	List of subscription properties to match between Didomi and Actito	Yes

On top of the properties to map as subscriptions from the configuration, we also automatically include all the properties (if any) from the Didomi user's metadata object as Actito profile attributes.

Example

{
    "type_id": "actito",
    "authentication": {
        "private_api_key:" "PRIVATE_API_KEY"
    },
    "properties": {
        "entity_id": "ENTITY_NAME",
        "table_name": "TABLE_NAME",
        "user_unique_key": "USER_UNIQUE_KEY"
    },
    "mappings": [
        {
            "id": "ACTITO_EMAIL_SUBSCRIPTION",
            "value": "consents_channels_email_enabled",
        }
    ],
    "upsert_mode": true,
    "enable_webhooks": false,
    "enable_emailing": false
}

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

Learn how to configure Didomi-Actito integration in the Didomi Console in this help center documentation.