Marketo Engage destination

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


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

Supported identities and 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

Target Identity Description
ECID 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.
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

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.

Export type and frequency

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

Item Type Notes
Export type Segment export You are exporting all members of a segment (audience) with the identifiers (email, ECID) used in the Marketo Engage destination.
Export frequency Streaming Streaming destinations are “always on” API-based connections. As soon as a profile is updated in Experience Platform based on segment evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations.

Set up destination and activate segments


For detailed instructions on how to set up the destination and activate segments, read Push an Adobe Experience Platform Segment to a Marketo Static List in the Marketo documentation.

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


The Experience Platform user interface is frequently updated and may have changed since the recording of this video. For the most up-to-date information, please refer to the guide linked above.

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.

On this page