Personalisation

The content and the subject take variables between double braces, and a small language of conditions and loops. No code is run: the engine understands only what is described here. The Variables button of each editor lists the ones available; one click copies a variable.

Variables

In campaigns and automations

Variable	Value
`{{ subscriber.first_name }}`	First name
`{{ subscriber.last_name }}`	Last name
`{{ subscriber.email }}`	E-mail address
`{{ subscriber.attributes.city }}`	A custom attribute (replace `city`)
`{{ list.name }}`	The list’s name
`{{ unsubscribe_url }}`	The unsubscribe link
`{{ preferences_url }}`	The link to the preferences page
`{{ organisation.address }}`	The organisation’s postal address (Settings → General)
`{{ webview_url }}`	The link to the web version
`{{ campaign.name }}`, `{{ campaign.subject }}`	Campaigns: name and subject
`{{ mail.name }}`, `{{ mail.subject }}`	Automation e-mails: name and subject

In the confirmation and welcome e-mails

The same subscriber and list variables, plus {{ confirm_url }}, the confirmation link.

In transactional e-mails

The variables are the ones your application sends. With:

{ "customer": { "name": "Ada" }, "order": { "number": "A-1024", "paid": true } }

you write {{ customer.name }} and {{ order.number }}. See Transactional e-mails through the API.

A variable that is unknown or empty is replaced with an empty string. Values are escaped in the HTML: a first name holding <script> is shown as it is, and does not run.

Conditions

The language is Liquid, the one Shopify and many others use: what you know from there works here.

{% if subscriber.first_name %}
  Hello {{ subscriber.first_name }},
{% else %}
  Hello,
{% endif %}

Form	True when
`{% if name %}`	the value is set (not empty)
`{% if name == "value" %}`, `!=`	equal, different — capitals count
`{% if orders > 3 %}`, `<`, `>=`, `<=`	numbers compare as numbers
`{% if name contains "value" %}`	the text, or the list, contains it
`{% if a and b %}`, `{% if a or b %}`	both, either
`{% elsif … %}`	another case, before `{% else %}`
`{% unless name %}`	the opposite of `if`
`{% case plan %}{% when "pro" %}…{% endcase %}`	one case among several

{% if subscriber.attributes.plan == "pro" %}
  Thank you for being a Pro customer: delivery is on us.
{% elsif subscriber.attributes.orders > 0 %}
  Welcome back.
{% else %}
  Your first order ships free.
{% endif %}

A contact field is read by its key, under attributes: {{ subscriber.attributes.plan }}. A field of type number compares as a number, a date can be written with date.

Filters

A filter changes a value on its way out. They chain, left to right.

Hello {{ subscriber.first_name | default: "there" | capitalize }},
your order of {{ event.value | money: event.currency }} left on {{ event.shipped_at | date: "%d/%m/%Y" }}.

Filter	Gives
`default: "there"`	the value, or the words given when it is empty
`capitalize`, `upcase`, `downcase`	capitals
`truncate: 60`	at most sixty characters
`date: "%d/%m/%Y"`	a date, in the shape asked
`plus`, `minus`, `times`, `round`	arithmetic
`size`, `first`, `last`, `join: ", "`	about a list
`money: "XAF"`	an amount kept in the smallest unit, written as the reader’s language writes money: `1250` gives `€12.50` in English, `12,50 €` in French

A filter that does not exist stops the e-mail from being rendered, and the preview says which one: better an e-mail not sent than one sent broken. A variable that does not exist is simply empty.

Loops

<ul>
{% for item in event.items %}
  <li>{{ item.name }} × {{ item.quantity }}{% if item.price %} — {{ item.price }}{% endif %}</li>
{% endfor %}
</ul>

A loop runs over a list of plain values (["Sourdough bread", "Brioche"]) or over a list of objects ([{"name": "Bread", "quantity": 2}]), whose fields are read with a dot. forloop.first, forloop.last and forloop.index say where the loop is; {% for item in items limit: 3 %} stops early.

What an event brings

In an automation started by something the person did, the e-mails read that event: {{ event.name }}, {{ event.value }}, {{ event.currency }}, and every property it was sent with, directly under event — {{ event.url }}, {{ event.total }}, {% for item in event.items %}. See Events.

Two variables you cannot leave out

A campaign does not go out without:

{{ unsubscribe_url }}: a visible unsubscribe link;
{{ organisation.address }} (or the address written out in full): the sender’s postal address.

Both are legal requirements for any marketing e-mail. The simplest thing is to put them in your template.

Getting started

Contacts

Content

Campaigns

Automations

Transactional e-mails

Deliverability

Account and team

Help

Personalisation

Variables

In campaigns and automations

In the confirmation and welcome e-mails

In transactional e-mails

Conditions

Filters

Loops

What an event brings

Two variables you cannot leave out

​Variables

​In campaigns and automations

​In the confirmation and welcome e-mails

​In transactional e-mails

​Conditions

​Filters

​Loops

​What an event brings

​Two variables you cannot leave out

Variables

In campaigns and automations

In the confirmation and welcome e-mails

In transactional e-mails

Conditions

Filters

Loops

What an event brings

Two variables you cannot leave out