In the past couple of weeks, we have been discussing the different options in the Email Template Editor. In this post, we will briefly go over the inclusion of recipient-based content that couples the CRM database to the emails that are being sent to these recipients.
Sending emails in this day and age is both a very personal and a very unpersonal thing to do. You may send an email to a mass of clients, but simply heading that email with ‘dear client’ may not be enough for you. You may wish to include other personal data in the email so that they can check it and, if necessary, send a correction to you with a linked Jotform, or you may encounter any one of thousands of reasons to send data specific for the recipient in your email blasts.
When setting up an email template, you will want to insert placeholders into the template that tell the system that you want to insert recipient-based content at that point in the email. These placeholders are inserted easily by surrounding them with double curly brackets, like so:
This placeholder can be inserted anywhere in the body of the email, including in url’s and href links hidden behind images, so custom url’s are created in those links. When they are simply inserted into the body of the email, it can look like this:
With this, the system now knows that it needs to insert some data into the email, but it doesn’t know what kind of data yet. This will need to be mapped when the email is being configured to be sent, which is something that we will discuss next week in the Email Node discussion as we will return to the Workflow, and even later on as we discuss the sending of mass marketing Campaigns.