Adobe Marketo Engage

Introduction

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

Implementation

Connection

Didomi connects to Adobe Marketo Engage on your behalf through the following credentials:
  • Client ID: To get your client ID, navigate to your Marketo Engage Interface -> Admin -> Integration -> Launchpoint menu.
  • Client secret: To get your client ID, navigate to your Marketo Engage Interface -> Admin -> Integration -> Launchpoint menu.
  • Instance: Your instance is the Endpoint provided in Marketo Engage through Interface -> Integration -> Web services -> REST API

Options

  • Upsert mode: You can choose allowing Didomi to create leads in Marketo, by setting upsert_mode to true. Otherwise, when a consent is collected but the organization_user_id value does not match with any lead in Marketo, the consent update will not be propagated to Marketo.
  • Bidirectional flow: Please note that the bidirectional flow is not supported at the moment.

Mapping

Didomi uses the entity Person (Lead) of Marketo and sends the Lead attribute property when updating a lead. Hence consent events are mapped to Marketo's lead attributes.
Property
Description
Required
Upsert mode
By setting upsert_mode to true you allow Didomi to create leads in Marketo
No, Default value = false
Client ID
A client ID from your Marketo account
Yes
Client secret
A client secret from your Marketo account
Yes
Instance
Your Marketo REST api endpoint
Yes
Properties
Mapping for properties between Didomi and Marketo
Yes

Example

{
"upsert_mode": true,
"config": {
"client_id": "your_client_id",
"client_secret": "your_client_secret",
"instance": "your_marketo_endpoint",
"properties": [
{
"id": "lead_attribute_api_name",
"value": "consents_purposes_newsletter_enabled"
}
]
}
}