Personalize your content add-personalization
Personalization of delivery content is a key feature that allows you to tailor messages to individual recipients, making communication more relevant and engaging.
In ÃÛ¶¹ÊÓƵ Campaign, by using profile data, such as the profile’s name, location, or past interactions, and specific variables of your delivery, you can dynamically customize elements like text, images and offers in your communication.
The delivery personalization not only enhances the user experience but also improves engagement rates, leading to higher conversion and customer satisfaction.
Using profile data for personalization data-personalization
You can personalize any delivery with profile data by using the expression editor, which is accessible in fields with the Open personalization dialog icon, such as the subject line, email links, and text/button content components. Learn how to access the expression editor
Personalization syntax syntax
Personalization tags follow a specific syntax: <%= table.field %>
. For example, to insert the recipient’s last name from the recipient table, use the <%= recipient.lastName %>
syntax.
During the delivery preparation process, ÃÛ¶¹ÊÓƵ Campaign automatically interprets these tags and replaces them with the corresponding field values for each recipient. You can view the actual replacement by simulating your content.
When uploading contacts from an external file for a standalone email delivery, all fields in the input file are available for personalization. The syntax is as follows: <%= dataSource.field %>
.
Add personalization tags add
To add personalization tags into a delivery, follow these steps:
-
Open the expression editor using the Open personalization dialog icon that is accessible from text-type editing fields, such as the subject line or the SMS body. Learn how to access the expression editor
{modal="regular"}
-
The expression editor opens. Personalization fields available in the ÃÛ¶¹ÊÓƵ Campaign database are organized into several menus on the left side of the screen:
{modal="regular"}
table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 Menu Description {modal="regular"} The Subscribers application menu lists fields related to the subscribers of an application, such as the used terminal or the operating system. This menu is available for push notifications only {modal="regular"} The Recipient menu lists fields defined in the recipients table, such as recipients’ names, ages, or addresses. When uploading contacts from an external file for a standalone email delivery, this menu lists all fields available in the input file. {modal="regular"} The Message menu lists fields related to the delivery logs, including all messages sent to recipients or devices across all channels, such as the date of the last event with a a given recipient {modal="regular"} The Delivery menu lists fields related to the parameters required for performing deliveries such as the delivery channel or label. note note NOTE By default, each menu lists all fields within the selected table (Recipients, / Message / Delivery). If you want to include fields from tables linked to the selected table, enable the Display advanced attributes option located below the list. -
To add a personalization field, position your cursor at the desired location within your content and click the
+
button to insert it. -
Once your content is ready, you can save it and test the rendering of the personalization by simulating your content. The example below shows the personalization of an SMS message with recipients’ first names.
{modal="regular"}
{modal="regular"}
Using variables for personalization variables-personalization
You can also use variables to personalize your delivery.
Learn more about adding variables to a delivery.
For example, we have the variable deliveryType
defined as below.
{modal="regular"}
This variable can be used in the content of the delivery, by using the Add Personalization icon and the expression <%= variables.deliveryType %>
for our example.
{modal="regular"}
You can check the use of your variable with Simulate Content button.
{modal="regular"}