PERSONALIZATION

Within emails and LinkedIn tasks you can personalize them automatically as well as add some conditional logic. Below we will explain all your options.

Adding to Email

To add information like the Contact’s or Lead’s first name, type the @ symbol and you will see your choices. These are fields from the Contact or Lead record and the CRM User record.

Anything that starts with “to.” is from the Contact’s or Lead’s record and anything starting with “from.” is from the User record (most likely your User record).

Example of personalization added into an email message.

In the actual email that goes to the recipient, those slugs will be filled with the data from your records (see the preview down below in this article).

If you are using this in a LinkedIn Task, the area where you can copy to the clipboard will be populated with that data.

Comments and Conditional Logic

For more options, type the { symbol. You will see a list of options you can scroll through. See below to understand what they do. These are based on the coding language Handlebars.

Comment/Prompt

Add this to make a note for yourself to manually update this area of the email when the Manual Email Activity is due. You can type whatever you want between the {{ }} to remind yourself of what type of information you want there. You should only use this type in a Manual Email (not in Auto Email).

logic.if

This will input:

{{#if _field_}} {{/if}}

The idea is if some field contains data put this text into the email/LinkedIn task. For example:

{{#if to.company}}I see that you are working at to.company and I think you'd really benefit from our product.{{/if}.

In this example, if there was a company name in the company field of the Contact or Lead, this whole sentence would be in the email/LinkedIn task with the company name in the middle of the sentence where to.company is. If the field was blank on the Contact or Lead, none of this will show up in the email/LinkedIn task.

logic.if/else

Very similar to the logic.if, except you can also put a fallback option if the field doesn’t contain data. This is what you will see when you add this:

{{#if expression}} {{else}} {{/if}}

The idea on this one is if a field contains data output X and if it does not contain data output Y.

Hi {{#if to.firstname}}to.firstname{{else}}Friend{{/if}},

If there is a first name on the contact this would turn out to be something like “Hi Jane,” and if it did not contain data, it would be “Hi Friend,”.

format.number

Use this to format a number – remove decimals and add commas. For example:

{{format_number 1.00}}

This would change to 1 in the email.

Or:

{{format_number 100000}}

would change to 100,000.

date.weekdays_from_now

Change the number at the end of this one to change which weekday from the day it sends will populate. If today is Monday, and you send an email with:

{{weekdays_from_now 3}}

It will output “Thursday”. It will not include Saturday or Sunday. So if it is Friday and you have:

{{weekdays_from_now 1}}

It will output “Monday”.

date.days_from_now

Like the above, except it will include Saturday and Sunday.

date.today

{{today}} will give the current day. If today is Monday it will show “Monday”.

date.tomorrow

This will give tomorrow’s day. If today is Monday {{tomorrow}} will print “Tuesday”.

date.is_monday

All of the date.is day items will give (but the name of the day would be the one you chose):

{{#if (is_monday)}} {{/if}} 

This allows you to put some text in between the start and end ifs. For example,

{{#if (is_monday)}} Happy Monday! I hope you had a great weekend. {{/if}}

This would print “Happy Monday! I hope you had a great weekend.” only if the current day was Monday.

Previewing Personalization

Once you add personalization to the left-hand email message, you can see a rendering of it in the right-hand preview via data from an example Contact record. So in the preview below, "Hello to.FirstName" renders to "Hello Andrew" and so on.

You can toggle between 10 example Contact records to see different data rendered in the preview.

If the Contact selected (via the "To") in the preview example does not have data in one of the fields, the email preview will produce an error to let you know which email personalization field has the issue.