Marketo Engage destination beta-marketo-engage-destination

Destination changelog changelog

With the release of the enhanced Marketo V2 destination connector, you are now seeing two Marketo cards in the destinations catalog.
  • If you are already activating data to the Marketo V1 destination: Please create new dataflows to the Marketo V2 destination and delete existing dataflows to the Marketo V1 destination by February 2023. As of that date, the Marketo V1 destination card will be removed.
  • If you have not yet created any dataflows to the Marketo V1 destination, please use the new Marketo V2 card to connect to and export data to Marketo.

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 Adobe Experience Platform to Marketo where they will appear as static lists.

Supported identities and attributes supported-identities-attributes

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
A namespace that represents ECID. This namespace can also be referred to by the following aliases: “Adobe Marketing Cloud ID”, “Adobe Experience Cloud ID”, “Adobe Experience Platform ID”. See the following document on ECID for more information.
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 Describe API request 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
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.

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 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.

Set up destination and activate audiences set-up


For detailed instructions on how to set up the destination and activate audiences, read Push an Adobe 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.

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.
  • 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.
The Marketo Engaged Destination Connector enables marketers to activate Experience Platform segments in their Marketo instances. The connector is freely available to anyone who owns both Marketo and any version of Experience Platform. The connector uses email addresses to match Experience Platform profiles to Marketo leads. Segments pushed to Marketo will appear as static lists in your Marketo instance. Here’s what the new destination card will look like in destinations UI. When configuring the destination you’ll be asked to input a client ID and secret. These are the same credentials that you would use when creating a connection to the Marketo REST API. The connector enables you to select one or more segments to push via a single destination. For each segment that you elect to push to Marketo you’ll need to specify the Marketo list ID of the static list that you’d like the segment to be pushed to. This ID can be input into the Experience Platform UI in the mapping ID field, which is visible on the right-hand side of the screen.
Once activated Platform will stream audience membership information to Marketo where it will appear in a static list in your Marketo Instance. Here’s some important limitations to keep in mind regarding V1 of the connector. First of all, V1 only supports the sharing of segment membership information. No profile attribute data can be shared via this connector in V1. Profile attributes sharing will be available in a subsequent release. Furthermore, V1 only works for leads that already exist in your Marketa lead database. This means that if Experience Platform pushes a segment member who does not already exist in your Marketo database, as identified by their email address, the segment member will not be added to a list in Marketo. -

Data usage and governance data-usage-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.