(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. Use it to 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

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: “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 identifies 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
Supported
Description
Segmentation Service
Yes
Audiences generated through the Experience Platform Segmentation Service.
All other audience origins
No

This category includes all audience origins outside of audiences generated through the Segmentation Service. Read about the various audience origins. Some examples include:

  • custom upload audiences imported into Experience Platform from CSV files,
  • look-alike audiences,
  • federated audiences,
  • audiences generated in other Experience Platform apps such as Adobe Journey Optimizer,
  • and more.

Supported audiences by audience data type:

Audience data type
Supported
Description
Use cases
People audiences
Yes
Based on customer profiles, allowing you to target specific groups of people for marketing campaigns.
Frequent buyers, cart abandoners
Account audiences
No
Target individuals within specific organizations for account-based marketing strategies.
B2B marketing
Prospect audiences
No
Target individuals who are not yet customers but share characteristics with your target audience.
Prospecting with third-party data
Dataset exports
No
Collections of structured data stored in the Adobe Experience Platform Data Lake.
Reporting, data science workflows

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

IMPORTANT

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.

IMPORTANT
The video does not entirely reflect current capability. For the most up-to-date information, 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.

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

recommendation-more-help
experience-platform-help-destinations