Skip to main content

Salesforce Marketing Cloud email preview and QA

AMPscript that did not resolve is the one send accident nobody catches in review.

Paste the HTMLMerge tags detected

Salesforce Marketing Cloud URL import is being tested and is coming soon. We have not yet imported a live Salesforce Marketing Cloud 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 Salesforce Marketing Cloud: Marketing Cloud calls this View as a Web Page, usually abbreviated VAWP, and the link comes from %%view_email_url%%. Clicking it makes Marketing Cloud rebuild the email from the original send data.

    %%view_email_url%%

    Import soon after the send. VAWP links stop working once the account-level URL Expiration threshold passes, and for triggered or Journey Builder sends they can fail earlier still, because the personalisation data they rebuild from is subject to a retention policy.

    Salesforce: when VAWP links fail
  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 Salesforce Marketing Cloud campaign

Unreplaced merge tags

AMPscript's %%tag%% form is distinctive enough that the engine matches it by name, like Mailchimp's. 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.

%%FirstName%%reported asSalesforce AMPscript

Worth knowing

  • SFMC emails are frequently table-heavy and Outlook-targeted already, so the compatibility score is often the least surprising result. Unresolved AMPscript is the finding that tends to matter.

Before you send

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

Check a Salesforce Marketing Cloud campaign

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

Get Started Free