Marketo
This guide will walk you through connecting your Adobe Marketo Engage account to Composa, enabling you to export email templates directly to Marketo.
Prerequisites
Before connecting, you'll need:
A Marketo (Adobe Marketo Engage) account with administrator access
Your Marketo Munchkin ID
Your Marketo API Client ID and Client Secret (from a LaunchPoint API service)
Connecting Marketo
Step 1: Get Your Munchkin ID
Log in to your Marketo dashboard
Navigate to Admin > Integration > Munchkin
Locate your Munchkin ID in the format:
XXX-XXX-XXXCopy this value
Step 2: Create or Retrieve API Credentials
In Marketo, go to Admin > Integration > LaunchPoint
Find an existing API service with email template permissions, or create a new one
Click the service to view its details
Retrieve or generate the Client ID and Client Secret
Copy both values
Note: The API service must have permissions to create and manage email templates. If creating a new service, ensure it's assigned a role with these permissions.
Step 3: Connect in Composa
In Composa, go to Settings > Integrations
Find Marketo (Adobe Marketo Engage) and click Connect
Enter your Marketo Munchkin ID
Enter your Client ID and Client Secret
Click Validate
Composa will validate your credentials against your Marketo account.
Step 4: Select a Default Folder
After validation, you'll be prompted to select a default folder in Marketo where exported templates will be stored. This folder is where new email templates from Composa will be created.
Select your preferred folder from the dropdown
Click Save
Your Marketo integration is now active.
Exporting Templates to Marketo
Once connected, exporting a template to Marketo is simple:
Open a template in the Composa editor
Click the Export button in the toolbar
Select Export to Marketo
Your template is created as a new email template in Marketo
The template appears in your selected default folder
You can now use this template in your Marketo campaigns
Handling Duplicate Template Names
If a template with the same name already exists in Marketo, Composa automatically appends a timestamp to the template name to ensure uniqueness. For example:
Template name:
Welcome EmailIf duplicate exists, Composa creates:
Welcome Email - 2024-01-15-143022
This prevents accidental overwrites and allows you to manage multiple versions of templates as needed.
Template Details
When you export a template to Marketo:
The template name matches the template name in Composa (with timestamp appended if a duplicate exists)
The template includes all HTML, styling, and content from your Composa template
The template is created in the default folder you selected during setup
The template is created as a draft, allowing you to review it before use
Images and assets are included based on Composa's export settings
Disconnecting Marketo
To remove the Marketo integration:
Go to Settings > Integrations
Find Marketo (Adobe Marketo Engage) in the list
Click Disconnect
Your Marketo account and any previously exported templates remain unchanged. You can reconnect at any time.
Troubleshooting
"Invalid Munchkin ID" Error
Verify that your Munchkin ID is correct and in the format
XXX-XXX-XXXConfirm that it matches the ID shown in Admin > Integration > Munchkin
"Invalid Client ID or Client Secret" Error
Double-check that both values are copied correctly from your LaunchPoint service
Verify that the API service is active and has not been revoked
Ensure the API service has email template permissions
"Validation Failed" Error
Verify all credentials are correct
Confirm that your Marketo account is active and accessible
Check that the API service has sufficient permissions
Try disconnecting and reconnecting your Marketo account
Export Fails
Verify that your Marketo integration is still active in Settings > Integrations
Check that your credentials still have the necessary permissions
Ensure your Marketo account has space to create new templates
Try selecting a different default folder during reconnection
Need Help?
For additional support:
Contact Adobe Marketo support for account-specific issues
Reach out to the Composa team for integration questions
Last updated
