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 theorganization_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.
Example
The configuration of the Marketo integration can be done in the Didomi Console. First please reach out to support@didomi.io to get the integration's premium feature activated.
Last updated