Exporting a Dyspatch Email to Customer.io

Use our integration with Customer.io to deliver engaging email experiences to your customers.

Dyspatch supports two Customer.io export types:

Newsletter — Export emails to Customer.io Broadcast Newsletters for blasts or scheduled sends.
Design Studio — Export emails as Customer.io Design Studio templates for use in any Customer.io workflow, including Campaigns.

The export type is determined by the Export Asset Type you selected when setting up your Customer.io integration.

Build and Approve in Dyspatch

In Dyspatch, use the Email Builder to create a beautiful, responsive, and engaging email. Collaborate with your team to approve and publish the email.

Once your email has been reviewed and approved by your team, you can move it into your Customer.io account by exporting it with the direct Customer.io Integration, or you can download your email to upload it to Customer.io manually.

See the Customer.io Integration Setup page if you'd like to use the direct integration and it is not yet set up in your organization.

Export a Published Email with the Customer.io Integration

Publish the email in Dyspatch and click Export.

Export published template from the Email Builder

Select Export to Integration, and choose your Customer.io integration.

Export Email to Integration modal in Dyspatch

Confirm or change your Email Name then Confirm & Export.

Rename and confirm export modal for Customer.io

If your integration is configured to export to Broadcast Newsletters, you'll also select the Newsletter you'd like to update on this modal

Your Dyspatch email will either be exported as a Design Studio template, or replace the selected Newsletter in Customer.io.

If there aren't any Newsletters in your Customer.io account and you'd like to export a Broadcast Newsletter to Customer.io, follow these steps below before exporting. Newsletters are designed for blasts or scheduled sends.

Prepare Customer.io Broadcast

Before you can export, you need to partially set up a Customer.io Broadcast.

Create and name your broadcast, select Newsletter as the Broadcast type. Configure your Customer.io People matching conditions or select Everyone in workspace for all emails specific to this integration.

Create Broadcast screenshot from customer.io

Select Email as the Message Channel type on the third page of the Customer.io Broadcast configuration page and save your progress.

Message Channel page 3 in customer.io broadcast setup

If you don't yet have any recipients, Customer.io will not allow you to create the Newsletter. Navigate to People > Add People > Add a Person to set one receiver for your newsletter. This will make it possible to integrate your emails.

Once the Broadcast is created, export your published email and select the Newsletter on the export modal.

Customer.io Broadcasts tab with exported Dyspatch email

Your exported emails will be available as a draft under the Broadcasts tab in Customer.io.

Note that you can set your email's metadata to include a sender email address and sender name for your Broadcast.

Exporting Your Email Manually to Customer.io

To manually download your email for Customer.io, navigate to your published email in Dyspatch.

Click Export > Download HTML and select Liquid as the download Language. Select the download button to save a zipped folder with your email code to your local machine.

Downloading your Email with the liquid templating language

This download includes your HTML email and other assets like plain-text content and email metadata. You must unzip the folder to retrieve your email's HTML code.

Now, Create a Broadcast Newsletter in Customer.io. When you get to step 3, Content, select Channel > Email and click on Content. Select <> Code to open their HTML code editor.

You can then copy & paste the HTML from your Dyspatch email by importing your HTML file into the Customer.io code editor. You may need to open the HTML as plain text, or if the email opens in a browser, view source to copy your HTML code.

Disable CSS preprocessing if you're importing emails into Customer.io from Dyspatch manually. This will ensure the emails work correctly on every device we support.