Emarsys Scripting Language

The Emarsys Scripting Language (ESL) is a scripting language for creating dynamic content in your campaigns, based on predefined rules.

Introduction

ESL is a genuine scripting language. It lets you personalize your content based on external factors, opposed to the standard personalization options, which can populate email content based only on contact database fields.

ESL is specifically for people with a knowledge of HTML.

As a quick reminder, here is the onboarding video about Emarsys Scripting Language:

Where can you use ESL?

You can use ESL snippets for dynamic content creation or further personalization in your omni-channel campaigns:

Email campaigns (batch and transactional, external event emails: In email you can use ESL in the email body, header, preheader, subject, from name, basically anywhere in the email where personalization could work effectively.
SMS and Push messages
Personalizing content with Relational Data
Web channel campaigns: You can use ESL for personalization only.

Personalization can only be applied for identified visitors. Therefore, ESL does not work for Web Channel campaigns with Recipient source: All visitors and Unidentified visitors.

ESL as being used for templates, it can also handle more complex algorithms. ESL also offers a universal solution for handling personalization, conditional text, and block targeting, and it is simpler and more flexible than other methods.

Why should you use ESL?

Since it is a scripting language, it provides numerous functions for you. First of all, the personalizations you can create with it can be more complex than the standard personalization options in Emarsys. Secondly, you can adjust any rule based on the values of your personalization fields for a specific campaign.

Emarsys accounts come with around 50 standard fields for storing contact data.
For a list of all the available values for the single-choice system fields, click here.
The value for a given ID may vary by language!

Examples for using ESL

You can use ESL in the following cases:

Custom controls: You can display a button called Become a member to only those contacts who are not members of your loyalty scheme. Although this could be done via simple conditioning or section targeting as well, for those who know HTML, it makes campaign creation a lot easier.
Counters: You can place a counter into your campaign without having to put a URL into your HTML code.
Conversions: You can handle transformations from one contact field to another, for example, to display field values provided in kilometers in miles instead.
Loops: You can create a loop, and do not have to refer to each and every array element separately. As ESL is a scripting language, it can automatically go through the array and use all elements one by one.

All in all, customization of your contacts becomes easy and fully automatic with the Emarsys Scripting Language.

How is Twig compared to ESL?

Twig does share similarities with the Emarsys Scripting Language, but there are huge differences as well. Twig is a language used solely for email templates and uses functions only to substitute variables in the template (e.g. make all first names uppercase).

ESL does not support all Twig tags and filters, so you are advised to use this documentation and not include elements from the Twig documentation referenced above.

Using ESL variables at template level

Example A

In this example you can use ESL variables at email template level to check a contact's registration language field and show a text accordingly.

{% if contact.35==1 %} Welcome dear customer 
  {% elseif contact.35 == 2 %} Willkommen, lieber Kunde!
{% else %} Bienvenido, querido cliente! 
{% endif%}

Example B

For a contact's registration language field you can also create ESL variables at email template level with applying placeholder texts, instead of adding the whole ESL snippet in the email body.

Setting up a ctatext variable at email template level:

<!--
  {% if contact.35 == 1 %}
  {% set ctatext = 'SHOP NOW' %}
  {% elseif contact.35 == 2 %}
  {% set ctatext = 'ZUM PRODUKT' %}
  {% elseif contact.35 == 3 %}
  {% set ctatext = 'ACHETER MAINTENANT' %}
  {% elseif contact.35 == 4 %}
  {% set ctatext = 'ACQUISTA ORA' %}
  {% elseif contact.35 == 8 %}
  {% set ctatext = 'COMPRAR AHORA' %}
  {% else %}
  {% set ctatext = 'SHOP NOW' %}
  {% endif %}
-->

Editor-specific details

The Emarsys Scripting Language is supported only by custom HTML campaigns created in the Visual Content Editor. Old template-based campaigns do not support it.

Operators are case sensitive and they should always be in lower case: "and", "or".

Operators supported in ESL

The following operators are available for Twig and supported in any expression in the Emarsys Scripting Language:

Comparison operators: Compare values and return true or false state. The operators include: ==, !=, <, >, >=, <=
Logical operators: Combine multiple boolean expressions or values and provide a single boolean output. The operators include: and, or

Commenting in ESL

Commenting out lines works in ESL similarly to Twig.

Commenting out a single line:

{# rds.rds_reformation.prefix_color('1304632BFF','BFF')[0].item_sku_prefix|required#}

Commenting out multiple lines:

{# The following code will not be executed and nothing will be displayed
{% if category.posts %}
  This category has posts
{% endif %}
#}

For example, you can use this to test and troubleshoot HTML email campaigns.

Language reference

Terminology

{{ this is an expression }}
{% this is a statement %}
|this is a filter

Code nesting

ESL allows you to nest codes. For example, if is your opening condition. For every if, there must be a closing endif. It can be nested inside another if, but both must eventually be closed.

Example

{% if contact.35 == 2 %}
     {% if contact.5 == 2 %}
         German Language Female
     {% else %}
         German Language Male
     {% endif %}	
{% else %}
     {% if contact.5 == 2 %}
         Default Language Female
     {% else %}
         Default Language Male
     {% endif %}
{% endif %}

Filters

Using multiple filters within one placeholder is allowed. When using nested/multiple filtering, pay attention to the order of the filters, because certain filters need to be in a specific position to work as expected. One example for this is the raw filter.

even/odd

With the help of the even/odd Twig filter you can differentiate even and odd values.

{% if 'now' | localized_date('de','yy') is even %}
   Now: even years
{% elseif 'now' | localized_date('de','yy') is odd %}
   Now: odd years
{% else %}
   Now: nothing above
{% endif %}

Result

Now: even years

split

You can define a split character with the help of the split filter. It divides the string and creates an array from it, which can be used by foreach .

{% foreach item in 'one,two,three'|split(',') %}
    {{ item }} <br />
{% endforeach %}

In this example, the split character is , (comma). item loops through all elements from the array and lists them one by one. If you include the HTML <br> tag, every element will be displayed in a new row:

one
two
three

You can also include a limit argument. There is a difference between working with positive and negative numbers. An example for a positive number is 2, where the last 2 elements will become one string and the remaining elements will stay separately.

{% foreach item in "one,two,three,four,five"|split(',',2) %}
    {{ item }} <br />
{% endforeach %}

Result

one
two
three
four,five

On the other hand, if the limit is -1, the very last element will not be returned, all the other elements will be displayed.

{% foreach item in "one,two,three,four,five"|split(',',-1) %}
    {{ item }} <br />
{% endforeach %}

Result

one
two
three
four

If the limit is zero, one string will be created from all elements in the array.

{% foreach item in "one,two,three,four,five"|split(',',0) %}
    {{ item }} <br />
{% endforeach %}

Result

one,two,three,four,five

If you dont define a split character, instead you include an empty string, the array will be split at every character.

{% foreach item in "123"|split('') %}
    {{ item }} <br />
{% endforeach %}

Result

1
2
3

If you add a limit to the empty string delimiter, the array will be split at this specific number.

{% foreach item in "112233"|split('',2) %}
    {{ item }} <br />
{% endforeach %}

Result

11
22
33

slice

You can cut and display a part of an array or string with the slice filter. If it is an array, foreach is used with it. Its first parameter defines from which element it starts (note that the very first element is signed by 0), and the second parameter defines the number of elements to cut (note that it includes the starting element as well). In the next example, the starting element of an array is 1, so it will start from the second element, and the number of elements is 2, so it will cut 2 elements starting with the second element.

{% foreach item in [1, 2, 3, 4, 5]|slice(1, 2) %}
    {{ item }} <br />
{% endforeach %}

Result

2
3

An example for slicing a string is the following:

{{ '12345'|slice(2, 2) }}

Result

If the starting number is negative, counting starts from the end of the array or string (e.g. -4 will sign the second element, which is 2 in the above example). If no second parameter is provided, it means including all upcoming elements. Please note that zero cannot be a second parameter.

{{ '12345'|slice(-4) }}

Result

format

The values of string template placeholders can be defined with the format filter. These placeholders are %s (string) and %d (number). In the following example, the value 10 is set for the message number. The format parameter is added with this variable as a parameter. The result is having this number in the string.

{{ "You have %d messages."|format("10") }}

Result

You have 10 messages.

default

If there is no defined value, a default (fallback value) can be displayed with using the default filter. In the following example, contact field 7 has no provided value, it is replaced by 5 defined in the brackets.

{{ 30 + contact.7|default(5) }}

Result

url_encode

You can encode a URL or part of a URL which contains invalid URL characters. This means that the invalid URL characters will be replaced by their valid HTML character combinations. An example for a URL particle containing a * (asterisk):

{{ "seg*ment"|url_encode }}

Result

seg%2Ament

Another example is having one or more spaces in the URL:

{{ "one space"|url_encode }}

Result

one%20space

In the next example, a key-value pair is converted into valid URL parameters:

{{ {'key': 'value', 'foo': 'bar'}|url_encode }}

Result

key=value&amp;foo=bar

escape

The characters valid in HTML can be escaped with the escape filter. An example is when the First name field of the contacts is checked. If any contains an HTML character (e.g. <), it will be treated as a simple string.

{{ "< '"|escape }}

Please note that escape can be abbreviated to e.

{{ "< '"|e }}

raw

It marks an escaped character as being a normal character. This is useful if you dont want some characters to be escaped again.

{{ "&lt; '"|raw }}

Result

&lt;

Without using the filter, the output of this expression would be: &amplt;.

If nested filters are used, the raw filter needs to be the last to work properly.

{{ mysubject_line | required | raw }}

abs

The abs filter returns the absolute value. Note that it does not work for strings, only for integers.

{{ -6|abs }}

Result

capitalize

It capitalizes a string.

{{ 'hello sunshine!'|capitalize }}

Result

Hello sunshine!

first

The first filter returns either the first element of an array or the first value of a key-value pair or the first character of a string.

{{ [1, 2, 3, 4]|first }}

Result

{{ { a: 1, b: 2, c: 3, d: 4 }|first }}

Result

{{ '1234'|first }}

Result

join

It concatenates the elements of an array to form a single string.

{{ [1, 2, 3]|join }}

Result

The join parameter defines the separator between the elements along which the concatenation happens.

{{ [1, 2, 3]|join('|') }}

Result

1|2|3

json_encode

With the help of the json_encode filter you can include characters in the json snippets in your ESL content.

{{contact.1234 | json_encode}}

Result

If the contact field contains characters that would break a json format, the json_encode filter solves this problem.

keys

This returns the keys from an object.

{% foreach key in { a: 1, b: 2, c: 3, d: 4 }|keys %}
    {{key}} <br />
{% endforeach %}

Result

a
b
c
d

A separator is also possible to provide.

{% foreach key in { a: 1, b: 2, c: 3, d: 4 }|keys %}
    {{key}}, <br />
{% endforeach %}

Result

a,
b,
c,
d,

last

The last filter returns either the last element of an array or the last value of a key-value pair or the last character of a string.

{{ [1, 2, 3, 4]|last }}

Result

{{ { a: 1, b: 2, c: 3, d: 4 }|last }}

Result

{{ '1234'|last }}

Result

length

It displays the number of array elements or the string character number.

{{ [1, 2, 3, 4]|length }}

Result

{{ '1234'|length }}

Result

The length filter can have a parameter and it can be included within if tags. In the following example, the length parameter 10 defines that if the number of users is more than 10, the provided message is shown.

{% if users|length > 10 %}
    The number of users is more than 10.
{% endif %}

lower

It converts every string character to lowercase.

{{ 'WELCOME'|lower }}

Result

welcome

upper

It converts every string character to uppercase.

{{ 'welcome'|upper }}

Result

WELCOME

merge

It creates a union from two arrays or objects.

{% foreach item in [1, 2]|merge(['apple', 'orange']) %}
    {{item}} <br />
{% endforeach %}

Result

1
2
apple
orange

Please note here that if a value is provided for the same key again in the merge parameter, the original value is overwritten by this new one.

{% foreach item in { 'apple': 'fruit', 'potato': 'unknown' }|merge({ 'potato': 'vegetable'}) %}
    {{item}} <br />
{% endforeach %}

Result

fruit
vegetable

nl2br

It replaces the \ newline characters in the code to HTML line breaks (<br />) so these become new lines in HTML.

{{ "I like Emarsys Scripting Language.nYou will like it too."|nl2br }}

Result

I like Emarsys Scripting Language.<br />
You will like it too.

number_format

This formats decimal numbers. The first parameter of number_format determines how many numbers the decimal part contains. In the following example, it is 2, so 2 decimals will be displayed from the 3. The second parameter defines the decimal separator, which is , (comma) in this case. The third parameter stands for the thousands separator, which is . (period) here.

{{ 9800.333|number_format(2, ',', '.') }}

Result

9.800,33

Please note that if no parameter if given for the number_format filter, the decimals are not displayed at all and the thousands separator is , (comma).

{{ 2005.35|number_format }}

Result

2,005

replace

The replace filter replaces string parts.

{{ "I like this and that."|replace({'this': 'chocolate', 'that': 'candy'}) }}

Result

I like chocolate and candy.

Please note that if the very same string part is provided as a value first, then a key in the parameter, it will become overwritten. In this example, you can see that "cats" changes to "dogs" first, then both "dogs" change to "birds".

{{ "I like cats and dogs."|replace({'cats': 'dogs', 'dogs': 'birds'}) }}

Result

I like birds and birds.

The replace filter cannot handle ESL expressions without a result (the content before the pipeline character in the example). Message including these are not sent out and they increase the "No content" metric.

reverse

This filter reverses the order of array or string elements.

{% foreach item in [1, 2]|reverse %}
   {{item}} <br />
{% endforeach %}

Result

2
1

{{ '1234'|reverse }}

Result

round

The rounding conditions can be defined with the help of the round filter. Its first parameter defines the number of decimals, which is 1 in our example. As for the second parameter, two options exist. The first is floor, which rounds the numbers down regardless of the common rounding rules.

{{ 42.58|round(1, 'floor') }}

Result

42.5

The second is ceil, which rounds the numbers up in any case.

{{ 42.54|round(1, 'ceil') }}

Result

42.6

Please note that the default is having no decimals and using common rounding (rounding the value up from decimal 5 and rounding it down under it).

{{ 42.52|round }}

Result

title

It converts the string to titlecased (words will start with uppercase letters).

{{ 'my first car'|title }}

Result

My First Car

trim

Whitespaces can be cut with using this filter.

{{ '  I like Emarsys Scripting Language.  '|trim }}

Result

I like Emarsys Scripting Language.

Any other character can be defined to be cut if you include it as a parameter.

{{ '  I like Emarsys Scripting Language.'|trim('.') }}

Result

I like Emarsys Scripting Language

localized_date

Please note that date formatting follows the ICU convention and is case sensitive. For more information see the ICU Project details.

It is a date formatting function. It displays the date of the specified country and it can also translate this date (it can handle the PHP language translations). Please note that it displays only the date, even if the time is also provided. It can be overwritten, so the predefined date format becomes displayed (e.g. [{locale: en, format: yyyy mm}] means that the format YYYY MM will become visible for English people.) The localized_date filter can have 4 parameters. These are displayed in the order defined by their language settings, and contain the following:

full: year, month, date, day of the week
long: year, month, date
medium: year, abbreviated version of month, date
short: yyyy/MM/dd, the separator can be different.

The month can be displayed in the following ways:

Syntax	Displayed format
M	9
MM	09
MMM	Sep
MMMM	September
MMMMM	S

For further syntax of the date/time format, see here.

The input string can have the following formats:

'yyyy-MM-dd'
'now'
'+[number] hours'
'+[number] days'
'-[number] hours'
'-[number] days'

In this example, a full version is provided on the basis of the stored country+language value in contact field 12 for the specified date (e.g. it will become January 1 Friday, 1999).

{{ '1999-01-01'|localized_date(contact.12, 'full') }}

Ensure that all the fields have valid and relevant data values. The localized_date filter cannot format empty fields which may lead to an error in the Contact preview.

You can also use a database field placeholder to populate the date dynamically. If you do this, make sure to leave out the single quotes around the field placeholder, as the date value will be returned in quotes. In this example we use value of contact field 12345 to provide the date.

{{ contact.12345|localized_date(contact.12, 'full') }}

As another example, you can have "x days from now" date, too.

{{ '+7 days'|localized_date('de','dd.MM.yyyy') }}

localized_time

It is a time formatting function. It displays the time of the specified country and it can also translate this time (it can handle the PHP language translations). Please note that it displays only the time, even if the date is also provided. Here you can find what is displayed exactly if you provide parameters.

full: HH:MM:SS (AM/PM)
long: HH:MM:SS (AM/PM)
medium: HH:MM:SS (AM/PM)
short: HH:MM (AM/PM)

{{ '1999-01-01 13:13:13'|localized_time(contact.12, 'medium') }},

Please note here as well that the input string has a compulsory form (HH:MM:SS for time). In this example, a time is generated from a datetime with the localized_time filter on the basis of the stored country+language value in contact field 12 (13:13:13).

localized_datetime

It is a date and time formatting function. It displays the date and time of the specified country and it can also translate this (it can handle the PHP language translations). Regarding its parameters, it puts the values of the above two filters together (e.g. if its parameter is full, the date and time will be displayed as full as well).

{{ '1999-01-01 13:13:13'|localized_datetime(contact.12, 'long') }},

A possible result of the above example is 1999 01 January, 13:13:13.

required

If the evaluation of the ESL expression does not have a result and this filter is added, the message will not be sent. It will be displayed on the Analysis page in Emarsys though. The default invalid values for this filter are "" (empty string), and the value null.

{{ contact.2|required(['-']) }}

The parameter of this filter (the string - in this case) overwrites the default invalid empty string, so this string will become the new invalid one. You can still include the empty string later as well as it is possible to define more than one invalid values. For example, ([x], [y], [ ]) means that there are 3 invalid elements, the last one is the empty value.

Emails prevented from being sent with the required filter increase the "No content" metric. For more information on these metrics, see Email response metrics explained.

Personalization

Do not use the old personalization variable $ and/or % together with the new variable {{ }} in ESL expressions because your email might be cancelled. For more information, please contact Emarsys Support.
Placeholders, variables and scripts used in other platforms (for example, SFMC, Shopify, Magento, etc.) will break ESL and your mail will be cancelled. To prevent such issues, you must remove ALL of these instances from your campaigns.

Contact data is pulled from the Emarsys database. Here you can find the list of the possible email personalization placeholders:

General Information

Parameter	Description
{{ contact.1 }}	First Name
{{ contact.2 }}	Last Name
{{ contact.3 }}	Email
{{ contact.9 }}	Title
{{ contact.26 }}	Preferred email format
{{ contact.46 }}	Salutation

Personal Information

Parameter	Description
{{ contact.4 }}	Date of Birth
{{ contact.5 }}	Gender
{{ contact.6 }}	Marital Status
{{ contact.7 }}	Children
{{ contact.8 }}	Education
{{ contact.10 }}	Address
{{ contact.11 }}	City
{{ contact.12 }}	State
{{ contact.13 }}	ZIP Code
{{ contact.14 }}	Country
{{ contact.15 }}	Phone
{{ contact.16 }}	Fax
{{ contact.37 }}	Mobile
{{ contact.38 }}	First Name of Partner
{{ contact.39 }}	Birthdate of Partner
{{ contact.40 }}	Anniversary

Other Information

Parameter	Description
{{ contact.27 }}	Avg. length of visit (minutes)
{{ contact.28 }}	Page views per day
{{ contact.29 }}	Days since last email sent
{{ contact.31 }}	Opt-In
{{ contact.32 }}	User status
{{ contact.33 }}	Contact source
{{ contact.34 }}	Contact form
{{ contact.35 }}	Registration Language
{{ contact.36 }}	Newsletter
{{ contact.47 }}	Email valid
{{ contact.48 }}	Date of first registration

The data here comes from the Relational Data Service (RDS). Product-recommendation is a view which relates RDS data from different tables. Its parameter is a field on the basis of which you identify the contact (it is the email address here).

Note:

An RDS parameter can only be a constant (a field or a string), it must remain the same.
An RDS expression is valid only with a defined index and field name in it.

Example with foreach

{% foreach product in rds.product_recommendation(contact.3) limit 4 %}
    {{ product.title }} <br />
{% endforeach %}

Result

T-shirt
Shirt
Trousers
Jeans

Example without applying foreach

{{ rds.product_recommendation(contact.3)[0].title }}
{{ rds.product_recommendation(contact.3)[0].price }}

Result

T-shirt
59.99

Link Tracking

You can use ESL for link tracking purposes, too, by embedding the link in an ESL expression.

{% if event.payload.example == 'EXAMPLE' %} https://example.com {% endif %}

Please make sure that in the text version of the email, the link and the ESL expression is separated by a space or a line break. Otherwise, link tracking will not work and the campaign may become invalid.

Useful Tools

Twig testing is possible with TwigFiddle, where the result of any twig can be checked. Note here that we have some unique tags, parameters and filters, for which you cannot use this testing method easily. If you wish to test code with the foreach tag, we suggest that you replace it with a simple for tag, so that you can check your code. Other elements which cannot be tested here are the limit parameter and the .rds-related codes. From filters, the four unique ones are:

localized_date
localized_time
localized_datetime
required

For editing your script, Atom and Notepad++ can be useful with a twig-specific add-on.

ESL Validation

When adding an ESL snippet to your content, the ESL script is validated on a campaign level. Unless the script is valid, you cannot save the token. While adding the snippet, the editor automatically checks if your code is valid or not:

Samples

External Data for Transactional Emails

For an example, see Triggering external data for transactional emails.

Parameter	Description
{{ contact.17 }}	Job Position
{{ contact.18 }}	Company
{{ contact.19 }}	Department
{{ contact.20 }}	Industry
{{ contact.21 }}	Phone (office)
{{ contact.22 }}	Fax (office)
{{ contact.23 }}	Number of Employees
{{ contact.24 }}	Annual Revenue (in 000 EUR)
{{ contact.25 }}	URL
{{ contact.41 }}	Company Address
{{ contact.42 }}	ZIP code (office)
{{ contact.43 }}	City (office)
{{ contact.44 }}	State (office)
{{ contact.45 }}	Country (office)

Need assistance with your Emarsys product? We'll get you the help you need!

Introduction

Where can you use ESL?

Why should you use ESL?

Examples for using ESL

How is Twig compared to ESL?

Using ESL variables at template level

Editor-specific details

Operators supported in ESL

Commenting in ESL

Language reference

Terminology

Tags

if and elseif

elseif

foreach

Code nesting

Filters

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Result

Personalization

{{ contact. }}

General Information

Personal Information

Company Information

Other Information

{{ rds. }}

Result

Result

Link Tracking

Useful Tools

ESL Validation

Samples

External Data for Transactional Emails

Need assistance with your Emarsys product?
We'll get you the help you need!