Exporting Interactive Email to Your Own ESP

Keep the ESP you already trust and add interactive email to it. Export compiles your email into one HTML file, with a version for every inbox built in, ready to paste into Mailchimp, Brevo, SendGrid, Klaviyo, Campaign Monitor, ActiveCampaign, HubSpot or Mailjet. Votes, answers and purchases still come back to MailInApp.

Subject

New arrivals, just for you

Export compiles your email into one HTML file, ready to paste into any ESP's custom-HTML campaign editor. You keep the ESP you trust, your readers get interactive email, and every vote and answer comes back to MailInApp.

Lists, automations and a sending reputation built up over years are worth keeping. Export brings interactive blocks to the ESP you already use.

The workflow

Finish the design in the studio, click Export in the Send tab, then paste the HTML into your ESP's custom or paste-in-code campaign option. Mailchimp, Brevo, SendGrid, Klaviyo, Campaign Monitor, ActiveCampaign, HubSpot and Mailjet all accept it. The file includes a version of each block for every inbox, so every reader can take part. See How the fallback engine works.

Exporting a campaign to Mailchimp

  1. In Mailchimp, go to Campaigns → Create, create an email, and choose Code your own → Paste in code. If you're in Mailchimp's new builder, it switches you to the classic builder for this step.
  2. Paste the whole exported file, from <!DOCTYPE to </html>, without trimming anything. The interactive parts rely on the <style> block at the top.
  3. Add Mailchimp's *|UNSUB|* merge tag as the unsubscribe link, which Mailchimp requires in every email. If your email's footer carries MailInApp's own unsubscribe link ({{unsubscribe_url}}), remove it before you export, so readers use Mailchimp's.
  4. For personalization, type Mailchimp's own merge tags, such as *|FNAME|*, straight into your text in the studio. Export keeps them as they are and Mailchimp fills them in at send time. MailInApp's own {{field}} tags are for emails sent from MailInApp, and an export leaves them empty.
  5. Use Preview and test → Send a test email and open the test in Gmail and Outlook before scheduling. Mailchimp adds its own footer and tracking code, so leave some room under the 102KB limit below.

The export already inlines the styles every inbox needs, so leave Mailchimp's Automatic CSS Inliner off. If you turn it on, check in the test send that the interactive blocks still respond.

What comes back

Poll votes, form answers, ratings and purchases from the exported email reach MailInApp and show in the email's Insights, counted for the email as a whole: totals per block and per option.

Results per person: send from MailInApp

Some features work for each reader by name: answers saved to contact fields, journeys started by an answer, a prize for each player, one-click booking and countdowns that end for each person. For these, send the email from MailInApp, natively from your own domain or through your SMTP relay, and every answer is tied to its contact.

What your ESP still owns

Delivery, domain authentication (SPF, DKIM and DMARC), list management, and its own unsubscribe, open and click tracking. Export brings the design and the interactivity.

Watch the 102KB ceiling

Gmail clips any message over roughly 102KB, hiding the rest behind "View entire message", footer and unsubscribe link included. The studio shows your email's size as you design and warns as you approach the limit.

Getting started

Design the email in the studio, click Export in the Send tab, and paste the HTML into your ESP's custom-HTML campaign editor. See Export & send with your ESP for the full workflow.

A typical build-and-send sequence

  1. 1

    Finish the design in the studio

    Build the email with the interactive blocks that fit. Every one of them goes into the export.

  2. 2

    Export the HTML

    Click Export in the Send tab. One file holds the email, its version for every inbox and the links that record each answer.

  3. 3

    Paste it into your ESP

    Create a campaign with your ESP's custom HTML or paste-in-code option and paste the whole file.

  4. 4

    Send a test, then the campaign

    Send a test through your ESP, open it in Gmail and on a phone, then send the campaign like any other.

Frequently asked questions

Do the interactive blocks still work after export?

Yes. Votes, form answers and every other interaction still reach MailInApp and show in the email's Insights. Delivery and list management move to your ESP.

Can I see who answered?

Answers from an exported email are counted for the email as a whole, so Insights shows totals per block and per option. To see each person's answers, save them to contact fields or start journeys from them, send the email from MailInApp, where every answer is tied to its contact.

Can I personalize an exported email?

Yes. Type your ESP's own merge tags, such as Mailchimp's *|FNAME|*, into the text in the studio. Export keeps them as they are, and your ESP fills them in at send time.

How many times can I export?

Each plan includes a number of exports a month. See pricing for each plan's allowance.

What does my ESP still handle?

Delivery, domain authentication (SPF, DKIM and DMARC), list management, and its own unsubscribe, open and click tracking. Export brings the design and the interactivity.

What if the email gets too large?

Gmail clips any message over roughly 102KB behind "View entire message", footer and unsubscribe link included. The studio shows your email's size as you design and warns as you approach the limit, so you can shorten copy or trim blocks before exporting.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.