- Unsubscribe
<a href="{{ consent.page }}">Unsubscribe</a> (or {{ email.unsubscribe }} if the consent framework is off)- First name
{{ customer['first_name'] }}(Jinja)- With a fallback
{% if customer['first_name'] %}{{ customer['first_name'] }}{% else %}there{% endif %}- View in browser
<a href="{{ email.view }}">View in browser</a>
The Bloomreach Engagement unsubscribe link
Put this in the footer of every marketing email you code for Bloomreach Engagement:
<a href="{{ consent.page }}">Unsubscribe</a> (or {{ email.unsubscribe }} if the consent framework is off)
The law in most countries also wants the unsubscribe to be easy to find and free to use: see the email rules by country.
Personalisation in Bloomreach Engagement: first name with a fallback
Bloomreach Engagement uses Jinja. A first name on its own:
{{ customer['first_name'] }}
With a fallback, so an empty field never shows a blank or a raw tag:
{% if customer['first_name'] %}{{ customer['first_name'] }}{% else %}there{% endif %}
Showing something only to some people (an if / else):
{% if customer['tier'] == 'gold' %}Gold offer{% else %}Standard offer{% endif %}
View in browser, preferences and address tags
- View in browser:
<a href="{{ email.view }}">View in browser</a>
Making a coded template editable in Bloomreach Engagement
No editable-region markup for coded email. The HTML builder has Code, Edit (paragraph text, images, personalisation) and View modes; reusable pieces go in HTML blocks in the Asset manager.
<!-- Paste into the HTML builder (Code mode); marketers edit text and images in Edit mode -->
Getting your HTML into Bloomreach Engagement
Build the email in the HTML builder and paste the code in Code mode. For HTML made elsewhere, Replace relative paths swaps relative file paths for public URLs.
Limits worth knowing
- Custom Head HTML (Settings tab) accepts base, link, meta, style and title when the sanitiser is on.
- Jinja outside MJML elements is discarded in MJML templates.
- The visual editor's HTML element does not accept the <= operator; use its character code.
What Bloomreach Engagement calls things
Every platform has its own words for the same ideas. Bloomreach Engagement's, in plain English:
| The idea | Bloomreach Engagement calls it | Worth knowing |
|---|---|---|
| One-off send | Email campaign | A one-off email sent to a chosen audience at a set time, built outside any automated flow. “Campaigns” is also the whole menu section covering every channel. |
| Automated journey | Scenario | A drag-and-drop flowchart of nodes moving customers through automated messages and data actions. Not a “what-if” scenario, this is the journey builder itself. |
| Trigger / entry | Trigger node | The node that starts a scenario, firing on an event, a date, a schedule or an API call. Aggregates cannot be used inside an On event trigger. |
| Dynamic group | Segmentation | A saved rule set splitting customers into named segments, recalculated as data changes. One segmentation holds many segments, and each customer sits in only one. |
| Customer record | Customer | The profile holding one person’s identifiers, attributes and full event history. |
| Custom field | Customer attribute | A field stored on a customer profile, such as loyalty tier or an imported flag. Labelled “Properties” on the profile screen, not “Attributes”. |
| Behavioural event | Event | A timestamped action a customer took, carrying its own attributes. |
| Reusable block | HTML block | Reusable HTML saved in the Asset manager and dropped into many emails and weblayers. Docs also call these “dynamic blocks”; Snippets are a separate, smaller thing. |
| Template | Email template | A saved email layout kept in the Asset manager and reused as a starting point. Predefined templates are Bloomreach-managed and update centrally; only Project templates are yours. |
| Personalisation language | Jinja | The templating language used to personalise emails, weblayers and subject lines. Standard Jinja2, but several places in the product will not accept it. |
| Fallback value | Written by hand | There is no default-value setting, you write a Jinja if/else statement yourself. Omit the if/else and the text simply renders blank. |
| A/B test | A/B test | Splitting an audience across variants, with automatic or custom traffic distribution. Different from “Experiments”, which is the on-site personalisation tool. |
| Suppression | Custom suppression list | Your own list of addresses always excluded, alongside Bloomreach’s global list. The global suppression list is Bloomreach-managed and mainly blocks spam traps. |
| Frequency capping | Frequency policy | Rules limiting how many campaigns a customer receives in a period, set per sending node. Never called frequency capping, and it does not apply to transactional email. |
| Transactional | Transactional email | A one-to-one operational email triggered by an API call or scenario. Frequency policies don’t apply, so volume is uncapped. |
| Preference centre | Consent page | A hosted page where customers see and change the marketing consents they’ve given. Bloomreach never says “preference centre”; the unsubscribe page is separate. |
| Send-time optimisation | Optimal send time (OST) | A prediction of the best hour to email each individual customer. Requires the paid Loomi Audience Optimization package. |
| Reporting | Analyses | The reporting area holding dashboards, reports, funnels, trends and retentions. “Reports” is one tool inside Analyses, not the whole section. |
| Imported data table | Catalog | An imported lookup table of business data such as products or stores, keyed on item_id. Legacy catalog schemas cannot be changed after creation. |
| API-triggered send | API trigger | An inbound signal from an external system that starts one or more scenarios. The Webhook node runs the opposite way, Bloomreach calling out to you. |
| Draft vs live | Draft / Planned / Running / Finished | Campaign statuses showing whether something is unpublished, scheduled, live or stopped. Scenarios are Started and Stopped, not published. There is no publish button. |
What we couldn't confirm
We only list what Bloomreach Engagement's documentation says. These points weren't clear from it, so test them in your account:
- No default filter is documented; the fallback is a hand-written if/else (as in the glossary).
- The consent page doubles as the preference page; no separate preferences tag was found.
- No postal address tag, CSS inlining or size limit was found in the docs read.
Questions
What is the unsubscribe tag in Bloomreach Engagement?
{{ consent.page }} (or {{ email.unsubscribe }} if the consent framework is off).
How do I add a first name with a fallback in Bloomreach Engagement?
Bloomreach Engagement uses Jinja. A first name is {{ customer['first_name'] }}, and with a fallback: {% if customer['first_name'] %}{{ customer['first_name'] }}{% else %}there{% endif %}
How do I add a view-in-browser link in Bloomreach Engagement?
Use {{ email.view }}.
How do I get a custom HTML email into Bloomreach Engagement?
Build the email in the HTML builder and paste the code in Code mode. For HTML made elsewhere, Replace relative paths swaps relative file paths for public URLs.
Sources
- documentation.bloomreach.com/engagement/docs/personalization-using-jinja
- documentation.bloomreach.com/engagement/docs/email-editors
- documentation.bloomreach.com/engagement/docs/html-blocks
- documentation.bloomreach.com/engagement/docs/documentation-overview (terms)
Checked by Mailfois against Bloomreach Engagement's documentation on 27 October 2026. Platforms rename things often: spotted something out of date? Email [email protected].
Other platforms
Mailchimp · Klaviyo · HubSpot Marketing Hub · Salesforce Marketing Cloud Engagement · Braze · Adobe Marketo Engage · Brevo · Constant Contact · Campaign Monitor · Dotdigital · Iterable · Resend