Personalize with variables

A variable is a placeholder between double curly brackets, such as {{ firstname }}, that Sweescape replaces when sending with each recipient’s information. “Hi {{ firstname }}!” becomes “Hi Léa!” for Léa Martin and “Hi Hugo!” for Hugo Bernard.

Write a variable

A variable is written {{ name }}, where name is exactly the name of the column or piece of information, with its upper case and accents.
Insert it with the editor’s tools, shown below, rather than typing it: they write the exact name for you.
If the information is empty for a recipient, the variable is replaced by nothing. Write sentences that still read correctly in that case, or target the contacts who have this information with an “is filled in” segment.

In a campaign

A campaign’s variables are the columns of its audience. An audience imported with the columns firstname, email and city offers the variables {{ firstname }}, {{ email }} and {{ city }}. An audience created from an event with ticketing offers at least {{ firstname }}, {{ lastname }} and {{ email }}, plus your custom fields.

Email campaign. In the editor:

in a Text block, choose the column in the { } menu of the text toolbar;
below a title’s Text, a button’s Label or Link, an image’s Link (optional) and the Preview text, choose it in the Insert a variable… list.

A campaign’s Email object field does not offer variables.

SMS campaign. Click the Variables button above the Sms message field and choose a column: it is inserted where your cursor is. The cost of a personalized SMS is calculated for each recipient, once the variables are replaced. A long first name, or one containing a special character such as ç, can turn that recipient’s message into two SMS. The help text below the field then shows an estimate.

In an automation

An automation’s variables come from the event’s attendees.

Variable in the menu	Inserted code	Replaced by
Email	`{{ email }}`	The attendee’s email. Events with ticketing only.
First name	`{{ firstname }}`	Their first name. Events with ticketing only.
Last name	`{{ lastname }}`	Their last name. Events with ticketing only.
The name of each of your fields	`{{ field name }}`	The attendee’s answer to this custom field, or the value of this column for an event created by import.
Event name	`{{ eventName }}`	The name of the event.
Ticket name	`{{ ticketName }}`	See the warning below.
Feedback form link	`{{ feedbackFormUrl }}`	The personal link to the questionnaire. Only offered in the Email Builder of an Email Feedback automation.

Where to find them:

in Email Builder mode, with the { } menu of Text blocks and the Insert a variable… lists, as in a campaign;
in Simple Email Message mode, with the Variables button of the text toolbar;
in the Email object, by typing the variable yourself: it is replaced there too.

Automation SMS. Variables are not accepted: an automation SMS is sent as is and costs one credit per recipient. If you type a variable, saving is refused with the message “Variables are not supported here, the recipient would see them as text”.

In an invitation

The invitation email has its own list of variables, which includes the links to the Apple Wallet and Google Wallet cards. See Customize the invitation email and Wallet cards.

Check the result

A campaign’s test sends use no contact’s data: variables are not replaced in them. A test SMS shows, for example, {{ firstname }} as is. To check the real result, add yourself as a contact in the audience with your own information, create a segment that contains only you, then send it a separate campaign.