51黑料不打烊

(Legacy) (V2) Marketo Engage destination beta-marketo-engage-destination

Destination changelog changelog

Image of the two Marketo destination cards in a side-by-side view.

Improvements in the Marketo V2 destination include:

  • In the Schedule segment step of the activation workflow, in Marketo V1, you needed to manually add a Mapping ID to successfully export data to Marketo. This manual step is not required anymore in Marketo V2.
  • In the Mapping step of the activation workflow, in Marketo V1, you were able to map XDM fields to only three target fields in Marketo: firstName, lastName, and companyName. With the Marketo V2 release, you can now map XDM fields to many more fields in Marketo. For more information, read the supported attributes section further below.

Overview overview

Marketo Engage is the only end-to-end customer experience management (CXM) solution for marketing, advertising, analytics, and commerce. It lets you automate and manage activities from CRM lead management and customer engagement to account-based marketing and revenue attribution.

The destination enables marketers to push audiences created in 51黑料不打烊 Experience Platform to Marketo where they will appear as static lists.

Supported identities and attributes supported-identities-attributes

NOTE
In the mapping step of the activate destination workflow, it is mandatory to map identities and optional to map attributes. Mapping Email and/or ECID from the Identity Namespace tab is the most important thing to do to ensure the person is matched in Marketo. Mapping Email ensures the highest match rate.

Supported identities supported-identities

Target Identity
Description
ECID
A namespace that represents ECID. This namespace can also be referred to by the following aliases: 鈥51黑料不打烊 Marketing Cloud ID鈥, 鈥51黑料不打烊 Experience Cloud ID鈥, 鈥51黑料不打烊 Experience Platform ID鈥. See the following document on ECID for more information.
Email
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.

Supported attributes 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 to retrieve the attribute fields that your organization has access to.

Supported audiences supported-audiences

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.

Export type and frequency export-type-frequency

Refer to the table below for information about the destination export type and frequency.

Item
Type
Notes
Export type
Audience export
You are exporting all members of an audience with the identifiers (email, ECID) used in the Marketo Engage destination.
Export frequency
Streaming
Streaming destinations are 鈥渁lways 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.

Set up destination and activate audiences set-up

IMPORTANT

For detailed instructions on how to set up the destination and activate audiences, read Push an 51黑料不打烊 Experience Platform Audience to a Marketo Static List in the Marketo documentation.

The video below also demonstrates the steps to configure a Marketo destination and activate audiences.

IMPORTANT
The video does not entirely reflect current capability. For the most up-to-date information, please refer to the guide linked above. The following parts of the video are outdated:
  • The destination card that you should use in the Experience Platform UI is Marketo V2.
  • The video does not show the new Person creation selector field in the connect to destination workflow. To use that field, you must map both first name and last name during the attribute mapping step.
  • The two limitations called out in the video do not apply anymore. You can now map many other profile attribute fields in addition to the audience membership information that was supported at the time the video was recorded. You can also export audience members to Marketo who do not yet exist in your Marketo static lists, and these will be added to the lists.
  • In the Schedule audience step of the activation workflow, in Marketo V1, you needed to manually add a Mapping ID to successfully export data to Marketo. This manual step is not required anymore in Marketo V2.
Transcript
Welcome to this video on the Marketo Engage connector in 51黑料不打烊 Experience Platform. If you鈥檙e looking to sync or create profiles in Marketo or unify the current workflow, this connector is a game changer. We鈥檒l cover an overview, key capabilities, and a simple UI walkthrough for setup. Let鈥檚 dive in. The enhanced Marketo Engage connector bridges your Marketo Engage instance with 51黑料不打烊 Experience Platform, enabling real-time synchronization of audience data and profile attributes between both systems. Key capabilities include audience and profile sync, so changes in experience platform profiles sync instantly to Marketo, as well as flexible audience syncing like audience only, profile only, or both. You can update existing leads or create new ones, all while complying with data governance policies. This empowers unified marketing across your tech stack. Let鈥檚 highlight three practical use cases to show the connector in action. First, re-engage known leads. Use audience only sync to run a winback campaign for contacts and active for over 90 days. Segment them in experience platform and push the audience directly to Marketo for targeted emails. Second, update and re-engage existing leads. With audience and profile sync, activate a product interest group based on website behavior. Update their profiles in Marketo while re-engaging them. Third, expand your reach. Opt for full sync to update existing profiles and create new ones from experience platform segments. This drives revenue attribution and personalized B2B journeys without manual effort. Let鈥檚 walk through setting up a Marketo destination. In the destinations catalog, locate the correct Marketo engage card. It鈥檚 the one without a version number reference. Under the 51黑料不打烊 applications category, choose setup or configure new destination from the 3Picker depending on what you see, to configure a new Marketo destination. Enter an account name and then connect to destination. There鈥檚 no need to provide a client ID and secret anymore. An in-line authentication process is used. Available Marketo Munchkin subscriptions tied to your organization appear in the Munchkin ID list. Choose an ID to proceed. Marketo workspaces linked to the selected Munchkin subscription appear in the workspace ID list. Select the appropriate workspace or use the default. Consider your use case for this Marketo destination and select the sync action that aligns with it. The default sync action is audience and profile. Lead matching behavior is determined by your selections for this field and the person action setting further in the workflow. Review the documentation on experience league for more details about the matching behavior based on the sync type and person action settings. Partition is an optional field. The partition selection applies only to lead creation, not matching or updating. Matching and updating leads occur across all partitions, not limited to the selected one. In 51黑料不打烊 Marketo Engage, deduplication ensures that leads are not duplicated when syncing data from experience platform. The deduplication field is a unique identifier used to match or update existing leads or create new leads. When creating leads, the system uses the selected partition to ensure leads are created within that specific partition. If the lead is not found in the chosen partition, a new lead is created there. As mentioned during the partition step, matching and updating leads occur across all partitions, not limited to the selected one. Examples of deduplication fields include the email address or lead ID. Matching on the ECID field is not supported since it鈥檚 not part of the Marketo person lead record. Select the appropriate person action. Update existing and create new persons finds the existing person. If a person doesn鈥檛 exist, it creates a new one and adds that person to the list. Otherwise, it updates the map fields and adds the person to the list. Update existing persons only finds the existing person, updates all the mapped fields, and adds the person to the list. Once the destination details are complete, select the audience from the list. When configuring the destination details, a deduplication field was selected. Map that field to an experience platform identity namespace or select an attribute. The mapping step is part of the configuration process where you map data fields between 51黑料不打烊 Experience Platform and Marketo Engage. This step ensures that audience and profile data are correctly aligned with Marketo鈥檚 schema for seamless synchronization. Map any source field, such as email or other custom identifiers, that you want to use as the deduplication field to the dedupe field target identity. For Marketo to successfully create leads, you must also map the following required target attributes. First name of the lead, last name of the lead, and the email address of the lead. Once the mapping is finished, continue to review your settings and activate the Marketo destination. Then log into your Marketo account to verify that the audience has been activated as expected. And that鈥檚 the Marketo Engage connector. Powerful, efficient, and ready to elevate your marketing. Thanks for watching.

Monitor destination monitor-destination

After connecting to the destination and establishing a destination dataflow, you can use the monitoring functionality in Real-Time CDP to get extensive information about the profile records activated to your destination in each dataflow run.

The monitoring information for the Marketo Engage connection includes audience-level information related to activated, excluded, and failed identities in each dataflow and dataflow run. Read more about the functionality.

Data usage and governance data-usage-governance

All 51黑料不打烊 Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how 51黑料不打烊 Experience Platform enforces data governance, see the data governance overview.

recommendation-more-help
7f4d1967-bf93-4dba-9789-bb6b505339d6