Contact data
The Emarsys Contact database is where all your contacts' details are stored and pulled from when you are using a Contact Data token. The Contact database is a single layer data structure in which every data has a field. Here you can find a list of all the 50 standard contact data fields in the Emarsys Contact database and you can also create Custom Fields.
General Information
You can find the list of possible email personalization placeholders. The number refers to the field string ID, which can be found under Management > Field Editor.
Parameter | Description |
{{ contact.1 }} | First Name |
{{ contact.2 }} | Last Name |
{{ contact.3 }} | |
{{ contact.9 }} | Title |
{{ contact.26 }} | Preferred Email Format |
{{ contact.46 }} | Salutation |
{{ contact.4 }} | Date of Birth |
{{ contact.5 }} | Gender |
{{ contact.11 }} | Marital Status |
{{ contact.12 }} | Children |
{{ contact.14 }} | Education |
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 }} | Birth date of Partner |
{{ contact.40 }} | Anniversary |
Company Information
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) |
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 |
Single-choice data fields
Single-choice contact fields are data fields with multiple options from which you can choose only a single value. For example, the salutation field (contact.46
) provides you with the following options: Mr/Ms/Mrs, from these you can only pick one. For more information on the available values of the single-choice system fields, click here.
Another single-choice contact field is gender (contact.5
). If you insert the field {{ contact.5 }}
into a campaign, only the choice ID of the field will appear, in this case, 1
, 2
or 3
(Male/Female/Prefer not to say).
If you would like to see the actual choice instead of the ID of the choice, the following code works:
{{ contact.label.x }}
{{ contact.5 }}
1
(i.e. the choice ID of the value male).- When you are referring to the value ID in an
if
statement, for example:
{% if contact.5 == 2 %} Check out our vast selection of skirts and shorts. {% elseif contact.5 == 1 %} Check out our vast selection of jackets and ties.
{% endif %}
- If gender options are not in English but in another language, then it's easier to refer to the value ID of the options.
{{ contact.label.5 }}
male
.Multi-choice data fields
Multi-choice contact fields can contain more than one value, so contacts can select multiple values. For example: Interests {{ contact.0 }}
.
Note: Currently, displaying multi-choice field values is not supported in ESL.
$pers_1$
- First name
This is how the same code looks like in Twig:
{{ contact.1 }}
- First name
The old personalization variable $
can work together with the new variable {{ }}
in ESL expressions.
Placeholders, variables and scripts used in other platforms (for example, SFMC, Shopify, Magento, etc.) could break ESL and as a result, your mail might be canceled. To prevent such issues, you must remove ALL of these instances from your campaigns.