HubSpot email preview and QA
Personalisation tokens that quietly fail to resolve, caught before the send rather than in a reply.
HubSpot URL import is being tested and is coming soon. We have not yet imported a live HubSpot 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
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 HubSpot: In the email editor, open the setup icon in the left sidebar and turn on the View in browser toggle under Template, then set the page title and URL slug. In a coded template the variable is {{ view_as_page_url }}.
{{ view_as_page_url }}The web version does not go live until the email is sent or published as a test, so there is nothing to import before then. HubSpot also does not offer web versions on free trial accounts.
HubSpot: create a web version of your marketing email - 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
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.
Unreplaced merge tags
HubSpot personalisation tokens are HubL, which shares the {{ ... }} delimiters, so an unresolved token is detected 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.
{{ contact.firstname }}reported asHandlebars/MustacheWorth knowing
- A token with no fallback set renders as an empty gap, which reads as a formatting bug rather than a personalisation one.
- HubSpot marks these pages as not indexable by search engines, which has no effect on importing them.
Before you send
A preview tells you what is wrong. The pre-send gate answers one boolean, so a HubSpot campaign that regressed against the last version you approved never goes out. Put it behind a Zapier filter or a CI step.
Check a HubSpot campaign
21 clients, dark mode, and merge-tag detection. Free tier, no credit card.
Get Started Free