Skip to main content
Emailens/Integrations
Try Free

Mailchimp email preview and QA

Check a campaign across 21 clients without an export, using the campaign page link Mailchimp already generates.

URL import verifiedMerge tags detected

Verified end to end on a live campaign, 2026-08-31: fetched through Mailchimp's eepurl short link, unwrapped from the share and translate furniture, and rendered across all 21 clients. 141KB, 48 links, scoring 82 with 15 of 21 clients clean.

Setting it up

  1. 1

    Get the campaign's browser link

    Most ESPs put a view-in-browser link in the email itself, and that page is the HTML that was actually sent. Send yourself a test, open it, and copy that link. How each platform produces one differs, so see the note below.

    On Mailchimp: Mailchimp calls the browser copy of a sent email the campaign page. The *|ARCHIVE|* merge tag is replaced with that page's link when the campaign sends, and several Mailchimp templates include one already. Send yourself a test, open the email, and copy the link behind View this email in your browser.

    *|ARCHIVE|*

    Exporting is the route that does not work here: Mailchimp's own docs say drag-and-drop templates cannot be exported, and only custom-coded templates offer Export as template. The campaign page sidesteps that entirely.

    Mailchimp: about campaign pages
  2. 2

    Paste it into Emailens

    Open New Preview and paste the link into Import from your ESP. We fetch the page and check it across 21 clients, with dark mode, accessibility, size and merge-tag detection.

  3. 3

    Gate the send, if it is automated

    POST the same link to /api/gate and get one boolean back. Put it in front of a send in Zapier or CI and a campaign that regressed never goes out. Pro plan.

Import a Mailchimp campaign

Unreplaced merge tags

Mailchimp is the one ESP whose syntax we match by name rather than by shape, because *|TAG|* is unique to it. A tag left unresolved ships to the recipient literally, in body text and in href, src and alt attributes, where it is hardest to spot in review.

*|FNAME|*reported asMailchimp merge tag

Worth knowing

  • An unreplaced *|FNAME|* is the classic Mailchimp send accident: the tag renders literally to every recipient whose merge field is empty.
  • The campaign page is the sent HTML, so what you check is what shipped, not what the builder previewed.

Before you send

A preview tells you what is wrong. The pre-send gate answers one boolean, so a Mailchimp campaign that regressed against the last version you approved never goes out. Put it behind a Zapier filter or a CI step.

Pre-send gate API

Check a Mailchimp campaign

21 clients, dark mode, and merge-tag detection. Free tier, no credit card.

Get Started Free