Skip to main content
Emailens/Integrations
Try Free

Braze email preview and QA

No browser copy to fetch, so paste the HTML instead. Built for teams who ship email from a pipeline anyway.

Paste the HTMLMerge tags detected

Braze URL import is being tested and is coming soon. We have not yet imported a live Braze campaign end to end, so this page does not claim it works, and it will say verified only once one has. Paste the HTML in the meantime: every check here works exactly the same either way. We would rather say untested than assume, because the documentation for one platform on this page read perfectly well and its URL turned out to be a login screen.

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 Braze: Braze is the exception on this page: it has no built-in view-in-browser page. Its documentation's approach is to host the content yourself and link to it. So skip the URL step and paste the HTML straight in, or post it to the API.

    If you do link to a self-hosted page, that page is your own HTML rather than something Braze rendered, so import the source you deploy rather than the campaign.

    Braze: upload an HTML email template
  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 Braze campaign

Unreplaced merge tags

Braze uses Liquid with its own attribute syntax nested inside, so it is caught by the same {{ ... }} rule. 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.

{{ ${first_name} }}reported asHandlebars/Mustache

Worth knowing

  • If you already author Braze HTML in a repo, the pre-send gate is the better fit than manual previews: one request, one boolean.

Before you send

A preview tells you what is wrong. The pre-send gate answers one boolean, so a Braze 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 Braze campaign

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

Get Started Free