Brevo HTML email templates, checked before they land

What lands in Brevo

Publish creates a Brevo template with its subject line for each language you select. You find it in Templates in Brevo. Names follow a pattern such as {Template}_{LOCALE}, so October_update becomes October_update_EN and October_update_DE. You can rename each one in the dialog.

Pushing again updates the template with the same name, including its subject. Connecting takes a Brevo API key, plus the sender name and email the template should carry. Sending, lists and scheduling stay in Brevo.

Checked against Brevo before the push

Once Brevo is your active ESP, the email template checker reads every language with Brevo’s syntax in mind. A missing unsubscribe tag is a blocker, not a footnote.

Unsubscribe tag

Looks for {{ unsubscribe }}. Missing means a blocker. Present but hidden or tiny is flagged as high risk.

Merge tags

Brevo tags such as {{ contact.FIRSTNAME }} are left alone. A tag written for a different ESP is flagged, because Brevo would print it as text.

Dead links

Every link is requested. Brevo click-tracking links (sendibt3.com and the other Brevo tracking hosts) are skipped, so tracking does not show up as a false 404.

Leftover tokens

A {{locale.*}} or {{theme.*}} token that did not resolve is a blocker. It would reach Brevo as raw text.

One HTML file, one Brevo template per language

The layout lives in one Shared HTML file. Copy, links, images and the subject change per language through {{locale.key}} tokens, edited in a grid or imported from Excel. That workflow has its own page: HTML email localization.

Compile turns each language into plain HTML. Publish then sends each one to Brevo as its own template. Fixing a link in the shared file fixes it in every language on the next push.

Subject and sender travel with the template

Brevo templates hold a subject line and a sender. The push fills the subject from that language’s subject in EmailStitch, so the French template arrives with the French subject. The sender name and email come from your Brevo settings in EmailStitch.

Brevo tags such as {{ contact.FIRSTNAME }} and {{ unsubscribe }} pass through Compile untouched.