This destination connector is in beta and only available to select customers. To request access, contact your Adobe representative.
Use the Marketo Engage Person Sync connector to stream updates from person audiences to the corresponding records in your Marketo Engage instance.
The Marketo V2 Audience Sync Connector should not be used in Create mode in conjunction with the Profile Update Sync Connector
Target Identity | Description |
---|---|
A namespace that represents an email address. This type of namespace is often associated to a single person and therefore can be used to identify that person across different channels. |
You can map attributes from Experience Platform to any of the attributes that your organization has access to in Marketo. In Marketo, you can use the Describe API request to retrieve the attribute fields that your organization has access to.
This section describes which types of audiences you can export to this destination.
Audience origin | Supported | Description |
---|---|---|
Segmentation Service | ✓ | Audiences generated through the Experience Platform Segmentation Service. |
Custom uploads | ✓ | Audiences imported into Experience Platform from CSV files. |
Refer to the table below for information about the destination export type and frequency.
Item | Type | Notes |
---|---|---|
Export frequency | Streaming | Streaming destinations are “always on” API-based connections. As soon as a profile is updated in Experience Platform based on audience evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations. |
If your company has access to multiple organizations, make sure that you use the same organization in both Marketo Engage and Real-Time CDP, where you are setting up the destination connector to Marketo. If you have already configured a destination, you may select an existing Marketo account to use with your new configuration. If not, click the Connector to Destination prompt, which will allow you to set the name, description, and Marketo Munchkin ID of the desired destination. Your Marketo Instance’s Munchkin ID can be found in the Admin->Munchkin menu.
The user setting up the destination must have Edit Person permission in the Marketo instance and partition.
Once you have selected your instance, you will also need to select the Lead Partition which you want the configuration to integrate with. A Lead Partition is a concept in Marketo Engage used to separate lead records by business concern, such as a brand or a sales region. If your Marketo subscription does not have the Workspaces and Partitions feature, or if no additional partitions have been created in your subscription, then only the Default partition will be available. A single configuration can only update lead records which exist in its configured partition.
After an audience has been activated to the Marketo destination for the first time, backfilling profiles that already existed in the audience prior to Marketo destination activation can take up to 24 hours. Going forward, any time profiles are added to the audience, they’ll be added to Marketo immediately.
When sending updates to Marketo engage, records are selected based on the selected partition and one or two user-selected fields. If your destination is configured with the North America partition, and has Email Address and Company Name configured as deduplication fields, then all three fields must match to apply changes to an existing record. For example:
If no matching lead record is found, a new record will be created.
Read Activate profiles and segments to streaming segment export destinations for instructions on activating audience segments to this destination.
In the Activate Audiences step, you will be able to select from any person audiences which are visible to you.
For changes to a particular person attribute to be sent to Marketo Engage, the field must be mapped from a Real-Time CDP field to Marketo Field.
Experience Platform datatypes and Marketo datatypes can be mapped in the following ways:
Experience Platform Data Type | Marketo Data Type |
---|---|
String | String, Text Area, Url, Phone, Email |
Enum | String |
Date | Date |
Date-time | Datetime |
Integer | Integer |
Short | Integer |
Long | Float |
Double | Currency, Float, Percent |
Boolean | Boolean |
Array | Not supported |
Object | Not supported |
Map | Not supported |
Byte | Not supported |
In some cases it is desirable to allow integrations to set the value of a field if there is none, while preventing integrations from making updates to fields which already have a value. If you need to prevent the destination connector from overwriting existing values in your Marketo Engage instance, you can configure fields to block updates in the Admin->Field Management section of your Marketo instance and toggling the Adobe Experience Platform source type.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the data governance overview.