Marketo and Adobe Integration: How the Connections Work

Marketo and Adobe integration means connecting Adobe Marketo Engage to the rest of Adobe Experience Cloud through a shared Adobe organization. The main links run through Adobe Experience Platform (AEP). They include the connectors behind Real-Time Customer Data Platform (Real-Time CDP) B2B Edition, and Journey Optimizer B2B Edition. Marketo can also share audiences with Analytics, Target and Audience Manager, and use Adobe Experience Manager (AEM) assets and forms.

This post explains what each integration does, what you need before you start and where setups usually go wrong.

How does Marketo Engage connect to Adobe Experience Cloud?

It connects through Adobe organization mapping plus a set of product-specific connectors. Each connector moves a different kind of data, in a different direction, at a different speed.

Here's the map, based on Adobe's current Experience League documentation.

Integration	Direction	What it does	Key prerequisite
AEP Marketo Engage source	Marketo to AEP	Brings people, activities and B2B records into AEP	Org mapping, Marketo API credentials
AEP Marketo Engage destination	AEP to Marketo	Pushes AEP audiences into static lists	API-only user with write access
Journey Optimizer B2B Edition	Through AEP	Account and person journeys, actions in Marketo	AEP sandbox and a dedicated Marketo instance
Send a list to Experience Cloud	Marketo to Adobe	Shares list membership with other Adobe apps	Org mapping, ECID cookie sync
Sync an Experience Cloud audience	Adobe to Marketo	Brings an audience into a Marketo list	Org mapping
AEM Assets in Email Designer	AEM to Marketo	Uses AEM images in emails	Assets as a Cloud Service and Dynamic Media
AEM Forms submit action	AEM to Marketo	Sends form data to Marketo	LaunchPoint credentials in AEM
Tags Munchkin extension	Website to Marketo	Loads Munchkin tracking through tags	A tags property
GenStudio for Performance Marketing	Both ways	Moves email templates and variations	Same Adobe org, GenStudio entitlement

You won't need all of these. A common starting point is the Experience Platform source and destination. Teams then add Journey Optimizer B2B Edition or AEM Assets as their stack grows.

What do you need to set up first?

Start with Adobe Organization Mapping, a clean identity plan and dedicated API users. Almost every integration in the table depends on at least one of these.

Organization mapping. Adobe says you must enter your Adobe Identity Management System (IMS) Org ID in Marketo before syncing with other Adobe apps. Its examples include Audience Manager, the Real-Time CDP Marketo connector and Dynamic Chat. A few rules trip people up:

• Marketo and your other Adobe apps must be in the same Adobe org.
• The person mapping it must be an Org Admin for that org.
• Their Adobe user and Marketo user must use the same email address.
• If your subscription already runs on Adobe IMS, the Org ID is filled in and read-only.

Identity. Adobe says all new Marketo Engage subscriptions from 31 July 2023 come integrated with Adobe IMS. Users are then managed in the Adobe Admin Console. Older subscriptions may have moved since, so check which model you're on.

API users. Connectors such as the Experience Platform destination authenticate with a client ID and secret from a LaunchPoint custom service. Give each connector its own API-only user and role. Adobe's usage report tracks each API user separately, which makes it far easier to see which connector is using your daily quota.

Compliance. Adobe notes that a HIPAA-ready Marketo instance can't use the organization mapping and audience sharing integrations. If you're in healthcare, confirm this before you plan anything around them.

How does Marketo connect to Real-Time CDP and Adobe Experience Platform?

Through two separate connectors. A source brings Marketo data into Experience Platform, and a destination pushes Experience Platform audiences back into Marketo. Real-Time CDP B2B Edition is the product built around both.

The source connector. Adobe describes the Marketo Engage source as the way to bring B2B data from Marketo into Experience Platform and keep it current. It maps Marketo datasets to Experience Data Model (XDM) fields, including:

• Persons, activities, programs and program memberships.
• Companies, named accounts, opportunities and opportunity contact roles.
• Static lists and static list memberships.

You authenticate with your Munchkin ID, client ID and client secret. Adobe expects data to reach Real-Time Customer Profile in under 20 minutes, and the data lake in under 60 minutes. Both figures are at 95% confidence.

Licensing matters here. Adobe says you need Real-Time CDP B2B Edition to use all Marketo datasets for segmentation in Real-Time Customer Profile. Without it, you can still use the people and activities datasets. The B2B Edition also supports any number of Marketo instances, merged into one organization, which helps companies running more than one.

The destination connector. The Marketo Engage destination pushes audiences built in Experience Platform into Marketo, where they appear as static lists. It's a streaming destination, so profiles are sent as soon as audience evaluation updates them.

Setup needs an API role with Read-Write Person permission, an API-only user and its LaunchPoint credentials. You choose whether to match existing Marketo people only, or also create missing people. Adobe says the first activation can take up to 24 hours to backfill existing members. After that, new members are added straight away.

If Real-Time CDP is new to you, our guide to evaluating Real-Time CDP partners covers the wider platform work.

How does Journey Optimizer B2B Edition work with Marketo Engage?

Journey Optimizer B2B Edition runs on Experience Platform, not inside Marketo, but it still depends on Marketo for some services. Adobe's documentation describes the two as separate systems, each with its own data store.

Adobe sets out the architecture like this:

• Experience Platform is the main data store for accounts, people and opportunities.
• Journey Optimizer B2B Edition owns account journeys, buying groups and buying group roles.
• Each subscription comes with a dedicated Marketo Engage instance for entitlements and backend services, such as email delivery, sender configuration and branding domains.
• That dedicated instance is separate from your production Marketo instance.

You can connect existing Marketo instances, including production, so journeys can take actions there. Adobe's examples are adding people to a list or a request campaign. Account journeys don't appear in Marketo, though Marketo smart lists can filter on buying group membership.

This model is fairly new. Adobe's release notes describe an updated architecture in the 2025.10 release, where the two products stopped sharing a system and data store. Adobe adds that this model, once called the "simplified architecture", is now the default. Anything written before then may describe the older setup.

Our Journey Optimizer hiring guide covers how to find help with Journey Optimizer projects.

Can Marketo share audiences with Adobe Analytics, Target and Audience Manager?

Yes, through list sharing, but it's membership only. Adobe says the integration shares which lists a person belongs to, not their person attributes.

Sending lists out. You right-click a static list in Marketo and choose Send to Experience Cloud. Adobe lists these supported destinations: Advertising Cloud, Analytics, Audience Manager, Experience Manager, Real-Time CDP and Target. Analytics is supported only if you also own an Audience Manager license.

You can send a one-off copy, or tick Keep Audience Membership in Sync so later changes follow automatically. Adobe says it can take up to six to eight hours for membership to fully populate.

Bringing audiences in. You can also sync an Experience Cloud audience into a Marketo list. Adobe says the first sync can take up to 24 hours, and new records then sync in two to three hours.

How the match works. The link between systems is the Experience Cloud ID (ECID). When cookie sync is enabled, Marketo's munchkin.js captures ECIDs and matches them to its own cookie. That's why Adobe recommends loading munchkin.js alongside Adobe's visitor tracking code on the pages you care about.

For reporting, there are two more routes. Customer Journey Analytics (CJA) can report on Marketo datasets once they're in Experience Platform. And customers of Marketo's Real-Time Personalization (RTP) can send organization, industry and RTP segment data into Adobe Analytics.

How do Marketo and Adobe Experience Manager work together?

Marketo connects to AEM in three ways. AEM Assets works inside the Email Designer, an older importer works in Design Studio, and AEM Forms can submit data into Marketo.

AEM Assets in Email Designer. This is the current route. Adobe says it needs licenses for AEM Assets as a Cloud Service and Dynamic Media, with Dynamic Media with OpenAPI enabled. Other conditions apply:

• Only image assets are supported.
• Only repositories in the same Adobe org as Marketo are listed.
• Only Delivery tier repositories are supported.
• Users need the right Assets product profiles in the Admin Console.

The big benefit is linked references. Adobe says changes in AEM Assets flow through to live emails automatically. The flip side is that deleting an image in AEM leaves a broken image in your emails, although authors are notified.

The older Design Studio importer. Adobe documents an Asset Selector that imports AEM images into Design Studio. It supports AEM 6.4 and 6.5, and Adobe says it's fully supported only in Firefox. Imported images don't update when the AEM original changes, so they must be re-imported by hand.

AEM Forms. For AEM Forms as a Cloud Service, Adobe documents a Marketo Engage cloud configuration under Tools, then Cloud Services. It uses the client ID and secret from a Marketo LaunchPoint custom service. Adobe notes that AEM supports only the People (Leads) database among Marketo's databases.

How does identity work across Marketo and Adobe?

Marketo identifies people mainly by email address and its Munchkin cookie. Adobe's platform uses the ECID and other identity namespaces. Integrations work only as well as the bridge between the two.

A few documented rules shape that bridge:

• Munchkin cookies are per domain. A person known on one domain is anonymous on another. They stay that way until they fill out a form, click a tracked email or are matched through the API on that domain.
• The destination needs an identity. For the Experience Platform destination, mapping an identity, Email or ECID, is mandatory. Adobe says Email gives the highest match rate.
• ECID isn't native to Marketo data. For CJA reporting, Adobe suggests adding ECID as a custom field collected by munchkin.js, then using graph-based stitching.
• Tags can load Munchkin. The Marketo Munchkin extension for Adobe tags loads the tracking code without a separate script.

For most B2B teams, email is the practical primary identifier, with ECID as the bridge for anonymous web activity. Agree that rule before any connector is built, and write it down.

Which Marketo and Adobe integrations should you set up first?

Start with the one that solves a real problem today, then build in order of dependency. Organization mapping and identity come first, because almost everything else needs them.

A sensible order for many B2B teams looks like this:

• First, org mapping and tracking. Map the Adobe org, and make sure Munchkin and Adobe's tracking both run on your key pages. Without this, list sharing and identity matching stay weak.
• Second, the Experience Platform source. It puts Marketo data next to your CRM and web data in one place.
• Third, the destination. Once audiences are built in Experience Platform, push them back to Marketo lists for campaigns.
• Then the rest. Add AEM Assets, AEM Forms or Journey Optimizer B2B Edition, depending on whether content, forms or account-based programs matter most.

Skip any connector you can't name a use for. Each one adds an API user, a credential to rotate and another thing to monitor. A short list of well-run integrations beats a long list nobody checks.

What are the common pitfalls in a Marketo and Adobe integration?

Most problems come from org setup, identity gaps and wrong expectations about what each connector moves. These come up again and again in Adobe's own notes and FAQs.

• Different Adobe orgs. If Marketo sits in a different org from AEP or AEM, the integrations can't see each other.
• Org mapping fails. Usually the person isn't an Org Admin, or their Adobe and Marketo emails don't match.
• Lists look smaller in Adobe. Adobe explains that only people with a synced ECID can be shared. Empty lists, or lists with no ECIDs, aren't pushed at all.
• Expecting attributes. List sharing moves membership, not fields.
• Unsupported audiences. The Experience Platform destination accepts audiences from the Segmentation Service only, and people audiences rather than account audiences.
• Shared API users. One API user for every connector makes quota problems hard to trace.
• Stale images. Images from the older importer don't refresh when AEM changes.
• Wrong mental model of Journey Optimizer B2B. Account journeys live in Journey Optimizer, not in Marketo.

When something does break, our guide to Marketo integration troubleshooting services covers how a fix engagement runs.

What to do next

Use this checklist to plan your Marketo and Adobe integration.

• Confirm Marketo and every other Adobe app sit in the same Adobe org.
• Find the Org Admin who will complete organization mapping, and check their email matches in both systems.
• Decide your primary identifier and how ECID will be captured on your sites.
• Create a dedicated API-only user and role for each connector.
• Check your licenses: Real-Time CDP B2B Edition, Journey Optimizer B2B Edition, AEM Assets and Dynamic Media.
• List what each connector should move, in which direction, and how fresh it needs to be.

To find firms with experience on both sides, compare the Adobe Marketo Engage partner list with the Real-Time CDP partner list. For forms work, check the AEM Forms partners too. Brief shortlisted firms with the Marketo Engage RFP template, or start with a few questions in our partner advisor.