Push to your email platform

The Builder can push a finished email straight to 27 platforms. A push creates a template, campaign or draft in the platform, with the HTML written for it: its merge tags, unsubscribe links and condition code. For any other platform, download the HTML. See Export and download.

Integration guides and reporting

Find a dedicated guide for each integration, including its connection fields, export behavior and reporting limits. Nineteen platforms support aggregate reporting in Builder. See Email insights and reporting to choose sources, check reporting access and enable sync or AI use separately.

Connect a platform

Go to Integrations. Only workspace owners and admins can open it.
Under Email service providers, click the platform.
Enter the details it asks for (see the table below). Each panel has a Where to find these link to the platform’s own help.
Save.

Saved keys are never shown again. To change one, enter a new one. Leaving the field blank keeps the old one. To connect a second account on the same platform, open the platform and click Connect another account. Give each account a name, so people can tell them apart in Export. You can connect platforms on any plan. Pushing is part of the Builder plan.

Push an email

Open the email and click Export.
Under Export to your ESP, click the platform, or the account.
Check the options in the dialog and confirm.

After a push, Open in the platform appears in Export. When you push the same email again, you choose whether to update what you pushed before or make a new one. Some platforms always make a new one (see the table). If the Builder can’t tell whether a push went through, it says Check your ESP before retrying.

Marketo, Klaviyo and Customer.io

These integrations support several export formats and check saved content before updating an earlier export. Their guides cover setup, editing options and limitations:

Marketo: create emails or templates, use classic editable regions, choose approval and sample options, and copy images into Marketo. Classic movable modules have limited availability and always create a new copy.
Klaviyo: choose HTML, hybrid editable regions or native drag-and-drop blocks. Native mode supports a product feed that selects products at send time. Static image-library import is not supported in native mode yet.
Customer.io: create Design Studio emails or reusable templates, choose HTML or editable components, and preview the saved content with sample data.

Klaviyo native export and Customer.io reusable-template export are available to all connected accounts, subject to your Builder role and plan.

Verified updates and delivery status

For Marketo, Klaviyo and Customer.io, Builder checks the destination against the last verified export before updating it. After saving, it reads the destination back before recording success. If the destination has changed, or an older export has no verified baseline, Builder stops the update. Review the existing version in your platform, then keep editing it there or create a new copy from Builder. There is no force-overwrite option. Edits made in the platform do not sync back into Builder. The existing export format stays fixed when updating. Create a new copy to switch formats. Marketo classic movable modules always require a new copy. When Klaviyo or Customer.io already has the exported content, Builder reports that no export allowance was used. A verified save confirms the content reached the platform. It does not confirm inbox rendering, recipient personalization or campaign settings. If a delivery is uncertain or only partly saved, check its reported status and the destination before starting another export. A timeout does not prove that nothing was created. Contact Email Love if the attempt remains unresolved.

Platforms

Built-in platforms

Platform	What it asks for	Options when you push
Braze	Braze instance (for example US-01 or EU-01) and a REST API key with templates.email create, update and list. Add content_blocks create and update to push content blocks.	Export as an email template or a content block. Add translation tags, and Tag link addresses too.
Iterable	Data center (US or EU) and a server-side API key with email template permissions. Optional: from name, from email, reply-to email.	Export as an email template or a snippet. Message type. Also send approved translations as locales.
Adobe Marketo Engage	REST API endpoint (the Munchkin ID also works), Client ID and Client Secret. Then a Template folder.	Create an email or template. Classic editable regions, optional approval, sample send and image hosting. Verified updates. Movable modules are limited to selected accounts and require a new copy.
Salesforce Marketing Cloud	Client ID, Client secret and REST base URI, from SFMC Setup › Apps › Installed Packages.	Add link aliases and Track link conversions.

Connectors

Platform	What it asks for	What a push makes	Pushing again
Acoustic	Pod, client ID, client secret, refresh token, database ID, from name, from address, reply-to address. Optional folder path and visibility.	Mailing template	Updates it
ActiveCampaign	API URL and API key	Template	Updates it
Airship	App key, master secret and region (US or Europe)	Email template	Updates it
Blueshift	User API key and region (US or EU)	Email template	Makes a new one
Brevo	API key. Optional sender name and email.	Transactional template	Updates it
Customer.io	App API key and region (US or EU)	Design Studio email or reusable template. Choose HTML code or Editable Design Studio components. Preview saved content with sample data.	Updates the verified destination
Emarsys	API username and secret, email category ID, contact list ID, sender name and email	Email campaign	Makes a new one
HubSpot	Private app access token (pat-…)	Coded template, in an “EmailLove” folder	Makes a new one
Klaviyo	Private API key (pk_…) with template read and write access	Template. Choose HTML code, Hybrid: editable text and images, or Native drag-and-drop.	Updates the verified destination
Mailchimp	API key (ending in your data center, such as -us21)	Template	Makes a new one
MailerLite	API token, sender name and email	Draft campaign	Updates it
MailerLite Classic	API key, sender name and email	Draft campaign	Updates it
Mailjet	API key and secret key	Template	Updates it
MoEngage	Workspace ID, API key, data center, sender name, and the email of the person creating it. Export as an email template or a content block.	Custom template	Makes a new one
Netcore	API key	Template	Makes a new one
OneSignal	App ID and app API key	Email template	Makes a new one
Pardot	Salesforce domain, business unit ID, consumer key and secret, Salesforce username, password and security token	Email template	Updates it
Postmark	Server API token	Template	Updates it
Sailthru	API key and shared secret	Template	Updates it
SendGrid	API key and region (Global or EU)	Dynamic template	Updates it
SendX	Team API key	Email template	Updates it
Stripo	API authentication token. Optional template folder ID.	Editable template	Makes a new one
Zeta	Site ID and REST API key. Optional template tags.	HTML template	Updates it

Import merge tags from your platform

For some platforms, workspace owners can import the platform’s merge tags into Dynamic Content: Iterable, Braze, Marketo, HubSpot, Mailchimp, SendGrid, Brevo, ActiveCampaign, Mailjet, MailerLite, MailerLite Classic, SendX, Blueshift and Acoustic. See Conditions and merge tags.

Platforms you can’t push to

For Dotdigital, choose it under For in Export, then copy or download the HTML and paste it into Dotdigital. For any other platform, choose HTML (fallbacks).

Plans

Pushing to a platform counts as an export. The Free plan has no exports. The Builder and Enterprise plans have unlimited pushes. See Plans and billing.