Personalisation
Create personalised content in emails by merging data stored in User Profile and Custom Fields.
User data can be merged into:
- Subject Line
- Email Content (HTML & Text)
- Email Links
- Email Images Source
- Email Profile "From Name", "Reply Name", "Reply Email Address" and "To Name"
- Email Profile Opt-out Content
- Email Profile Custom Link Tracking
Personalised email messages are proven to give greater response rates and an improved User experience, provided the data stored in Lists is recent and of good quality.
Insert merge tags at the point in your Email Template you want the data to appear.
Missing Data
An easy way to handle missing data is to use the fallback feature of merge tags.
For example, if you're using {?$contacts_first_name?} but there could be people that don't have a first name set then you could do something like this...
Hi {?$contacts_first_name|default:"there"?}
For anyone that has a first name the merge tag will display that data, for anyone without a first name it will fallback to the default specified so in this case would display "Hi there".
For more info on using the fallback feature, click here.
Sender & Campaign Details
Campaign ID and Campaign Code merge tags are only valid within Campaigns and are NOT relevant to Workflows.
| Description | Merge Tag |
|---|---|
| Campaign ID | {?$campaign_id?} |
| Campaign Code | {?$campaign_code?} |
| Subject Line | {?$subject_line?} |
| Delivery Date | {?$date|date_format:"%e %B %Y"?} |
| From Email Address | {?$from_email_address?} |
| From Email Domain | {?$from_domain?} |
| From Email Root Domain | {?$from_domain_root?} |
| Reply Email Address | {?$reply_email_address?} |
| Opt-out Link | {?$optout_link?} |
| Opt-out Link (Global Suppression) | {?$optout_link_global?} |
| Email Address Confirmation / Double Opt-in | {?$double_optin_link?} |
| View in Web Browser | {?$view_online?} |
| Feedback Form | {?$abuse_report_link?} |
| Template ID | {?$template_id?} |
| Template API Identifier | {?$template_api_identifier?} |
| Template Description | {?$template_description?} |
Date masks need to adhere to the PHP date format.
There is a simplified 'View in Web Browser' tag that is intended for merging onto direct link parameters such as Google Translate URLs e.g. http://translate.google.com/translate?sl=en&langpair=en%7Cnl&u={?$view_raw_online?}
User Profile Fields
| Description | Merge Tag |
|---|---|
| User ID | {?$contacts_id?} |
| Secure User ID | {?$secure_id?} |
| Reference code | {?$contacts_reference_code?} |
| Title | {?$contacts_title?} |
| First name | {?$contacts_first_name?} |
| Last name | {?$contacts_last_name?} |
| Email address | {?$contacts_email_address?} |
| User's Email Domain | {?$email_domain?} |
| Mobile number | {?$contacts_mobile_number?} |
| Telephone number | {?$contacts_telephone_number?} |
| Address line 1 | {?$contacts_address_line_1?} |
| Address line 2 | {?$contacts_address_line_2?} |
| Address line 3 | {?$contacts_address_line_3?} |
| Address line 4 | {?$contacts_address_line_4?} |
| City | {?$contacts_city?} |
| Post code | {?$contacts_post_code?} |
| Country | {?$contacts_country?} |
| Date of birth | {?$contacts_dob?} |
| Gender | {?$contacts_gender?} |
| Company | {?$contacts_company_name?} |
| Date Created | {?$contacts_date_created?} |
| Date Last Modified | {?$contacts_last_modified?} |
Custom Fields
Always use the standard field names below when merging Custom Fields regardless of any Field Name Label customisation that may be set.
| Description | Merge Tag |
|---|---|
| Custom Field #1 | {?$contacts_data_1?} |
| Custom Field #2 | {?$contacts_data_2?} |
| Custom Field #3 | {?$contacts_data_3?} |
| Custom Field #4 | {?$contacts_data_4?} |
| Custom Field #5 | {?$contacts_data_5?} |
| Custom Field #6 | {?$contacts_data_6?} |
| Custom Field #7 | {?$contacts_data_7?} |
| Custom Field #8 | {?$contacts_data_8?} |
| Custom Field #9 | {?$contacts_data_9?} |
| Custom Field #10 | {?$contacts_data_10?} |
| Custom Field #11 | {?$contacts_data_11?} |
| Custom Field #12 | {?$contacts_data_12?} |
| Custom Field #13 | {?$contacts_data_13?} |
| Custom Field #14 | {?$contacts_data_14?} |
| Custom Field #15 | {?$contacts_data_15?} |
| Custom Field #16 | {?$contacts_data_16?} |
| Custom Field #17 | {?$contacts_data_17?} |
| Custom Field #18 | {?$contacts_data_18?} |
| Custom Field #19 | {?$contacts_data_19?} |
| Custom Field #20 | {?$contacts_data_20?} |
| Custom Field #21 | {?$contacts_data_21?} |
| Custom Field #22 | {?$contacts_data_22?} |
| Custom Field #23 | {?$contacts_data_23?} |
| Custom Field #24 | {?$contacts_data_24?} |
| Custom Field #25 | {?$contacts_data_25?} |
| Custom Field #26 | {?$contacts_data_26?} |
| Custom Field #27 | {?$contacts_data_27?} |
| Custom Field #28 | {?$contacts_data_28?} |
| Custom Field #29 | {?$contacts_data_29?} |
| Custom Field #30 | {?$contacts_data_30?} |
Example Usage
Email Template
To {?$contacts_title?} {?$contacts_first_name?} {?$contacts_last_name?}
Following your recent purchase of {?$contacts_data_1?} on {?$contacts_data_2?} we would love to hear your feedback on the product.
Click here to share your views with others here.
User Details
contacts_title: Miss
contacts_first_name: Sarah
contacts_last_name: Brown
contacts_data_1: Red/Black Neoprene Netbook Sleeve
contacts_data_2: 17th October
Merged Output
To Miss Sarah Brown
Following your recent purchase of Red/Black Neoprene Netbook Sleeve on 17th October we would love to hear your feedback on the product.
Click here to share your views with others here.
Using Fallback / Default Values
Email Template
To {?$contacts_first_name|default:'Customer'?}
Thank you, for your recent query regarding delivery within {?$contacts_city|default:'your city'?}
We will get back in touch within the next 2 working days
Merged Output (when User data is missing)
To Customer
Thank you, for your recent query regarding delivery within your city.
We will get back in touch within the next 2 working days.
Common Questions
Can the output be capitalised, made uppercase or lowercase?
Yes, this can easily be achieved using the Template Langauge.