Merge fields are used in form and event communications. Any form field that has an export key is available for merging. The standard merge fields are provided in the following list:
Standard merge field | Description |
|---|---|
| Adds a link to edit the registration |
| Adds a link to edit the registration administratively (use this link only if the recipient is a Slate user) |
| Adds a link to the online event page in Slate. If the event is hosted through an external service, registrants are redirected to the external URL after visiting the online event page in Slate. |
| Adds a link to the webinar recording. |
| Adds a QR code that is unique to each registration/registrant. The Slate Mobile application can scan this QR code and mark registrants as attended. |
| Adds a link so registrants can self check-in. |
| Event Title (Page Title) |
| Date and time that the event begins (for example, Monday, March 16, 2024 at 11:00 AM) |
| Date that the event begins (for example, Monday, March 16, 2024) |
| Time that the event begins (for example, 11:00 AM) |
| Date and time that the event ends (for example, Monday, March 16, 2024 at 1:00 PM) |
| Date that the event ends (for example, Monday, March 16, 2024) |
| Time that the event ends (for example, 1:00 PM) |
| Deadline for registration/updates (for example, 3/15/2024) |
| Event Location information entered on the Location tab |
| GUID of the person record associated with the form response (can be used to send a pre-populated registration form for an additional event or to send a link to the person record to a Slate user) |
| Link to pay for the event (applicable only if you charge an event registration fee) |
| Details about the Slate user that is associated with the form/event |
| Date the registration form was submitted (for example, Tuesday, February 24, 2024) |
| Generates a unique survey link for each registration. |
| Lists all related events selected on a form in chronological order. The merge field includes:
|
Formatting Date / Time Merge Fields
When merging in/exporting date/time information such as "Form-Date" for an event mailing, it's possible to control both:
Which date and time information to show, and
How the date and time information is shown
For Mailings and Confirmation Pages
The date filter in Liquid markup can be used to modify how Slate displays date/times. There are several merge fields that automatically include the date filter and a predefined format, such as: "Form-Date-Time", "Form-Date", and "Form-Time".
Below are some examples of how the date filter works in Liquid markup:
Input | Merge Field | Result |
|---|---|---|
"12/01/2023 08:01 PM" |
| December 1, 2023 |
"1/31/2024 09:30 AM" |
| 9:30 AM |
"2/15/2024 07:00 AM" |
| Thursday, February 15 at 7:00 AM |
Related Event Dates and Times
Slate will generate merge fields for related event selectors that have an export key, such as info_session. These merge fields will carry the export key of the corresponding related events selector, and there are two variations:
Simple, such as
{{info_session}}Advanced, such as
{{info_session-data}}. Slate will suffix the merge field with-data
Simple Merge Field
The simple merge field, like {{info_session}}, will output the related event's date (in dddd, MMMM d format) and title. For instance, an info session occurring on 1/31/2024 09:30 AM would display as Wednesday, January 1: Info Session.
Advanced merge Field
The advanced merge field, such as {{info_session-data}}, will add the following to a mailing confirmation page:
{% for event in info_session-Data %}
{{event.datetime | date:"dddd, MMMM d \a\t h:mm tt"}}: {{event.summary}}
{% endfor %}Please note the following merge fields to retain/remove/manipulate:
{{event.datetime}}{{event.summary}}
Multiple Related Events
If you want to display all Related Events selected on a form in chronological order, you can use the {{Form-Related-Events}} merge field. This merge field can also be edited in a similar manner as discussed in the previous discussion.