mailinapp

Exporting Interactive Email to Your Own ESP

You don't have to leave an ESP you already trust to get interactive blocks and the fallback engine. Export compiles a project into one static HTML file — kinetic, static, and Outlook-safe tiers all included, plus links to MailInApp's hosted interaction endpoints — ready to paste into Mailchimp, Brevo, SendGrid, Klaviyo, Campaign Monitor, ActiveCampaign, HubSpot, or Mailjet.

Subject

New arrivals, just for you

Export compiles a project into one static HTML file — all three fallback tiers plus links to MailInApp's hosted interaction endpoints — ready to paste into any ESP's custom-HTML campaign editor, so the interactive blocks carry over without leaving delivery you already trust.

Interactive blocks and the fallback engine aren't a reason to migrate off an ESP with lists, automations, and sender reputation already built up — export hands the compiled result over instead.

The workflow

Finish the design in the studio, click Export, then paste the compiled HTML into your ESP's custom/paste-in-code campaign option — Mailchimp, Brevo, SendGrid, Klaviyo, Campaign Monitor, ActiveCampaign, HubSpot, and Mailjet all accept it.

What still carries over

Poll votes, form submits, and every other interaction still post to MailInApp's own hosted endpoints and roll into the Responses dashboard — only delivery and list management move to your ESP.

What doesn't: per-recipient attribution

Export mints an unbound live-view token with no recipient row, so merge tags resolve to empty strings and interactions the exported copy drives are recorded anonymously (rate-limited per IP/campaign) rather than attributed to a specific person, unlike a MailInApp-native send.

What your ESP still owns

Delivery, domain authentication (SPF/DKIM/DMARC), list management, and its own unsubscribe/open/click tracking — export only replaces the design-and-interactivity layer.

Watch the 102KB ceiling

Gmail clips any message over roughly 102KB, dropping the <style> block and silently disabling kinetic interactivity. The studio tracks your compiled size live 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 compiled 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 whichever interactive blocks fit — the export carries every one of them over unchanged.

  2. 2

    Export the compiled HTML

    One file containing all three fallback tiers (kinetic, static, Outlook) plus links to the hosted interaction endpoints and live view.

  3. 3

    Paste it into your ESP's custom-HTML editor

    Any ESP that accepts custom/paste-in HTML works — create a campaign there and paste the export in as-is.

  4. 4

    Send a test, then send for real

    Test through the actual ESP (some rewrite HTML slightly), open it in Gmail and on a phone, then send the real campaign through the ESP like any other.

Blocks built for this

Frequently asked questions

Do the interactive blocks still work after export?

Yes — poll votes, form submits, and every other interaction still post to MailInApp's own hosted endpoints and roll into your Responses dashboard; only delivery and list management move to your ESP.

Are responses attributed to a specific recipient the way a native send is?

No — export mints an unbound live-view token with no recipient row, so merge tags resolve to empty strings and interactions the exported copy drives are recorded anonymously (rate-limited per IP/campaign) rather than tied to a specific person, unlike a MailInApp-native send.

Is there a limit on how many times I can export?

Yes — exports are metered per owner per calendar month by plan, since it's the one send-adjacent path that bypasses every other MailInApp volume meter entirely.

What does my ESP still need to handle?

Delivery, domain authentication (SPF/DKIM/DMARC), list management, and its own unsubscribe/open/click tracking — export only replaces the design-and-interactivity layer, not the sending infrastructure underneath it.

What happens if the compiled HTML is too large?

Gmail clips any message over roughly 102KB, dropping the <style> block and silently disabling kinetic interactivity — the studio tracks your compiled size live and warns as you approach that ceiling so you can shorten copy or trim blocks before exporting.

Related docs

See also

Build this in the studio

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

Start building freeSee all use cases