Beta
Marketo Engage Person Sync connection
- Topics:
- Destinations
CREATED FOR:
- Admin
- User
IMPORTANTOverview
Use the Marketo Engage Person Sync connector to stream updates from person audiences to the corresponding records in your Marketo Engage instance.
IMPORTANTSupported Identities and Attributes
Supported Identities
Supported Attributes
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.
Supported Audiences
This section describes which types of audiences you can export to this destination.
Export Type and Frequency
Refer to the table below for information about the destination export type and frequency.
Set up Destination
IMPORTANT- To connect to the destination, you need the View Destinations and Manage Destinations access control permissions.
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.
IMPORTANT
- Name: A name by which you will recognize this destination in the future.
- Description: A description that will help you identify this destination in the future.
- Munchkin ID: The Munchkin ID is the unique identifier for a specific Marketo instance.
- Partition: a concept in Marketo Engage used to separate lead records by business concern
- First searchable field: Field to deduplicate on. The field must be present in each lead record of the input. Defaults to email
- First searchable field: A secondary field to deduplicate on. The field must be present in each lead record of the input. Optional
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.
IMPORTANTDeduplication Fields
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:
- The destination is configured with the North America partition
- Person with Email test@example.com and Company name Example Inc. in Experience Platform matches the destination audience
- Unless a record with those values already exists in the North America partition in Marketo, a new lead record will be created
If no matching lead record is found, a new record will be created.
Activate Audiences
IMPORTANT- To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
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.
Field Mapping
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:
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.
Data Usage and Governance
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.