> ## Documentation Index
> Fetch the complete documentation index at: https://help.emaillove.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Marketo

> Create Marketo emails and templates, choose classic editing options, and update verified exports without losing track of changes in Marketo.

Export a Builder email to Adobe Marketo Engage as an **email in a program or folder**, or as an **email template only**. Email exports get their own backing template in Design Studio.

The integration supports verified updates, classic editable regions, movable modules, native image controls, approved snippets and mapped dynamic content. Classic movable modules are available to all connected accounts.

## Connect Marketo

You need a workspace owner or admin in Builder and an administrator who can set up Marketo API access.

1. In Marketo, open **Admin > Users & Roles**. Create an API role with **Read-Write Assets** and **Approve Assets**, with access to the Default workspace and each workspace you will use.
2. Assign that role to an **API-only user**.
3. In **Admin > LaunchPoint**, create a **Custom** service for that user. **View Details** shows its **Client ID** and **Client Secret**.
4. In **Admin > Web Services**, copy the **REST API endpoint**. Builder also accepts the Munchkin ID.
5. In Builder, open **Integrations > Marketo**, enter those values, and click **Connect**.
6. Choose a **Template folder** under **Design Studio folder for email templates**, then save. Choose a folder that can hold email templates, rather than the Design Studio root.

The template folder is required even when the finished email goes into a program. Marketo needs a template to create the email. Approving that backing template does not approve the email itself.

For the credential locations, see [Adobe's authentication guide](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication).

![Adobe Marketo Engage connection form in Builder](https://mintcdn.com/emaillove/qYrzRKTscc4O0qPw/images/builder/guides/connect-marketo.jpg?fit=max\&auto=format\&n=qYrzRKTscc4O0qPw\&q=85\&s=133dc3f95110894fe20bc9006b839f37)

Connect Adobe Marketo Engage in Integrations before exporting. This example shows blank connection fields; use the credentials for your account.

## Choose how people will edit it

| Choice | What you get in Marketo | Next export from Builder |
| - | - | - |
| **Editable in Marketo's classic editor** off | The compiled HTML design | Update the verified destination or create a new copy |
| **Classic editable regions** | Editable content sections in the classic editor | Update while the saved content and region structure still match, or create a new copy |
| **Classic movable modules (new copy)** | Sections people can move and duplicate in the classic editor | Create a new copy |

> [!NOTE]
>
> These formats target Marketo's classic editor, not the New Email Designer. Export permissions and any account-specific export pause still apply.

Movable modules do not support updating an existing export. After someone reorders, duplicates or edits modules in Marketo, create a new copy from Builder to keep that work intact. Layouts that cannot be separated into supported modules stop the export.

### Edit buttons and images in Marketo

With **Classic movable modules (new copy)** selected, supported buttons get native label and destination fields. Supported images get an image picker and alt-text field; images that already have a link also get a destination field. Unlinked images stay unlinked.

Each module has its own values. You can duplicate a module and change its image, button or link independently. Image dimensions and responsive layout are retained, so choose replacement images with the original aspect ratio and check the mobile preview. Button labels and links are applied to both the regular HTML and Outlook button.

![Marketo classic editor Local Variables panel with module-specific button text, button URL, image picker, alt text and image URL](https://mintcdn.com/emaillove/ClQjHwBgP98FJIyP/images/builder/guides/marketo-native-image-controls.jpg?fit=max\&auto=format\&n=ClQjHwBgP98FJIyP\&q=85\&s=dd5c6d1664316181f31bd313e2a9f2fc)

Open a module in Marketo's classic editor to find its button and image fields under Local Variables. Use the image-picker icon beside the image field to choose a replacement.

Personalized images, background images, responsive picture sources and images that share a link with text keep their original content. Unsupported buttons also retain their original content. Builder reports notices for content it cannot turn into native controls. Review the text alternative after editing in Marketo.

### Replace a section with a snippet

1. Select **Classic movable modules (new copy)**.
2. Under **Marketo snippets**, click **Browse approved snippets**.
3. Choose an approved snippet for each section you want to replace. Leave **Keep this section's content** selected for the others.
4. Export and preview the result in Marketo.

![Builder Marketo snippet settings with one section retained and another assigned to an approved static snippet](https://mintcdn.com/emaillove/ClQjHwBgP98FJIyP/images/builder/guides/marketo-snippet-selection.jpg?fit=max\&auto=format\&n=ClQjHwBgP98FJIyP\&q=85\&s=f277323ffd16be2929338dec0962b487)

Choose an approved snippet for the section it should replace. Other sections can keep their existing content.

This creates a native snippet reference. The snippet's content is managed in Marketo, and it replaces the whole selected section. Use approved, static classic snippets in the same Marketo workspace as the destination. Create or approve the snippet in Marketo before browsing. Segmented snippets are not supported by this flow.

### Map content versions to a segmentation

For an email export, Builder can map saved content versions to an existing approved Marketo segmentation. Marketo's segment rules decide who sees each version; Builder does not copy its condition rules into Marketo.

1. In Builder, arrange one adjacent section per version of a saved condition, including **Everyone else**. The versions must have compatible layouts.
2. In the export dialog, choose **Classic movable modules (new copy)** and click **Browse approved segmentations** under **Dynamic content**.
3. Select a segmentation, then choose a content version for every segment. Marketo **Default** is fixed to **Everyone else**.
4. Keep **Copy images into Marketo** off for this export. Dynamic content uses the current image URLs.
5. Sync a new copy, then preview every segment and its text alternative in Marketo before sending.

![Builder dynamic-content mapping with an approved Marketo segmentation, a targeted content version and Default fixed to Everyone else](https://mintcdn.com/emaillove/ClQjHwBgP98FJIyP/images/builder/guides/marketo-dynamic-content-mapping.jpg?fit=max\&auto=format\&n=ClQjHwBgP98FJIyP\&q=85\&s=ed72125d812d09ce9e9a8d1c47c9b329)

Map every segment to a saved content version. Default always uses Everyone else.

Leaving a group at **Export Everyone else only** exports only that fallback. An incomplete mapping blocks export. If the approved segments change, reopen the dialog and map them again.

Native dynamic content is available for new email copies, not template-only exports or updates to existing copies. It supports up to 100 segments, including Default, in the destination's Marketo workspace. Dynamic sections do not expose native image or button variables; static modules elsewhere in the email keep those controls. A dynamic section cannot also be replaced with a snippet. Builder does not create or change segmentations, audience rules or recipient records.

## Export an email or template

1. Open the email in Builder and click **Export**.
2. Under **Export to your ESP**, select your Marketo account.
3. Choose **Email in a program** or **Email template only**.
4. For an email, find its program or browse to a folder. For a template, choose a Design Studio template folder.
5. Check the **Name in Marketo**, sender details and editing options.
6. Click **Sync to Marketo** or **Create the template**.

![Marketo export dialog with Create a new one, Email in a program, destination folder and name fields](https://mintcdn.com/emaillove/ClQjHwBgP98FJIyP/images/builder/guides/marketo-export-destination.jpg?fit=max\&auto=format\&n=ClQjHwBgP98FJIyP\&q=85\&s=ba862a93d2962f7ac09ac88ce651f567)

Check the Marketo account, destination and name before syncing a new copy.

Program search covers recent programs. If the program is missing from search, use **Browse Marketing Activities instead** and navigate the folder tree.

For email exports, the dialog also includes:

* **From name**, **From address** and **Reply-to**. Empty values use the connection or Marketo defaults.
* **Description** for identifying the asset.
* **Operational email**. Use this only for transactional or legal messages: operational emails can bypass unsubscribe and marketing-suspension settings. Changing this choice on an existing exported email requires a new copy.
* **Turn off open tracking**.
* **Approve it in Marketo**. When this is off, the email remains a draft. Check it each time if your connection has automatic approval enabled.
* **Send a sample to**. Enter an address only when you want Marketo to send a sample. Leaving it empty sends no sample.

Exporting does not schedule a campaign or send to an audience. If a required content step fails, Builder stops later approval and sample-send steps. Review the reported status before trying again.

## Host images in Marketo

In the connection's **Optional settings**, turn on **Copy images into Marketo** and choose an **Images and Files folder**. Builder copies supported images into Design Studio and uses their hosted URLs. Images that cannot be copied keep their existing URLs, with a warning in the sync result.

Leave this off to keep the image URLs already used by the email.

## Update an earlier export

Reopen **Export > Marketo** and choose **Update the email**, **Update the template**, or **Create a new one**. Confirm an update with **Update in Marketo**.

Before updating, Builder checks the destination against the last verified export. It reads the saved result back before recording success. Verified exports now retain their editable, operational and open-tracking choices, so the next update dialog can restore them.

Builder stops an update when it finds changed remote content, incompatible editable regions, or a template that could affect other emails. An older export without a verified baseline also needs a new copy. There is no force-overwrite option in this flow.

If you have edited the email in Marketo, keep editing that version there or create a new copy from Builder. Marketo edits do not sync back into Builder.

## Personalization

Authored Marketo merge tags are preserved. Configure the required tokens in Marketo and preview them in the program that will send the email.

Builder does not create program-level My Tokens, generate Velocity script tokens from conditions, or author native Marketo global variables. A token remaining intact in the exported code does not confirm that it resolves for a recipient.

## Troubleshooting

| What you see | What to do |
| - | - |
| No template folder selected | Open the Marketo connection and choose a Design Studio email-template folder. |
| A program is missing from search | Browse the folder tree instead. Check the API user's workspace access. |
| The destination changed or its structure is incompatible | Review it in Marketo. Keep that version or create a new copy from Builder. |
| The template is shared with other emails | Create a new copy so an update does not change those emails. |
| Classic movable modules require a new copy | Select **Create a new one**. Existing modular exports cannot be updated in place. |
| A character or emoji is unsupported | Remove the character identified by the error, then try again. |
| The outcome is uncertain or partially saved | Check the recorded delivery status and the assets in Marketo. Do not start another export until the first attempt is resolved. Contact Email Love if it remains unresolved. |

Review desktop and mobile rendering, the text alternative, links and personalization in Marketo before sending. Builder does not clone programs, schedule campaigns, publish to Sales Insight, sync landing pages or import Marketo performance reports.

See [verified updates and delivery status](https://help.emaillove.com/builder/sending/esps.md#verified-updates-and-delivery-status) for the shared export behavior.

## Connection and reporting

See the [Adobe Marketo Engage integration guide](https://help.emaillove.com/builder/integrations/marketo.md) for connection setup and current aggregate reporting support. For the shared Reports and AI workflow, see [Email insights and reporting](https://help.emaillove.com/builder/reports/email-insights.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.