Form and Event Communications Merge Fields
  • 04 Apr 2024
  • 5 minute read
  • Dark
    Light
  • PDF

Form and Event Communications Merge Fields

  • Dark
    Light
  • PDF

Article summary

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

Explanation

Form-Link

Adds a link to edit the registration

Form-Internal-Link

Adds a link to edit the registration administratively (use this link only if the recipient is a Slate user)

Form-Share-Link

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.

Form-Share-Recording-Link

Adds a link to the webinar recording.

Form-Mobile-Pass

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.

Form-Mobile-Checkin

Adds a link so registrants can self check-in. 

Form-Title

Event Title (Page Title)

Form-Date-Time

Date and time that the event begins (for example, Monday, March 16, 2024 at 11:00 AM)

Form-Date

Date that the event begins (for example, Monday, March 16, 2024)

Form-Time

Time that the event begins (for example, 11:00 AM)

Form-End-Date-Time

Date and time that the event ends (for example, Monday, March 16, 2024 at 1:00 PM)

Form-End-Date

Date that the event ends (for example, Monday, March 16, 2024)

Form-End-Time

Time that the event ends (for example, 1:00 PM)

Form-Deadline

Deadline for registration/updates (for example, 3/15/2024)

Form-Location

Form-Street

Form-City

Form-Region

Form-Postal

Form-County

Event Location information entered on the Location tab

Form-Person-ID

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)

Form-Payment

Link to pay for the event (applicable only if you charge an event registration fee)

Form-User-ID

Form-User-Name

Form-User-First

Form-User-Title

Form-User-Email

Form-User-Phone

Form-User-Mobile

Details about the Slate user that is associated with the form/event

Form-Submitted

Date the registration form was submitted (for example, Tuesday, February 24, 2024)

Form-Survey-Link

Generates a unique survey link for each registration. 

Form-Related-Events

Lists all related events selected on a form in chronological order. The merge field includes:

  • Folder - such as "On-Campus Events / Open House Admissions Presentations"

  • Summary - such as "Admissions Presentation"

  • Datetime - such as "Friday, July 16, 2024 at 03:15 PM"

For Person and Application-Scoped Forms

Standard Merge Field

Explanation

sys-email

Slate will return a value in the following order of consideration:

  1. If an email address is collected on the form, this merge field returns that value

  2. This merge field returns the record's rank 1/active email address

sys-preferred

Slate will return a value in the following order of consideration:

  1. If a preferred name is collected on the form, this merge field returns that value

  2. If a first name is collected on the form, this merge field returns that value

  3. If the record already has a preferred name, this merge field returns that value

  4. This merge field returns the record's first name

sys-first

Slate will return a value in the following order of consideration:

  1. If a first name is collected on the form, this merge field returns that value

  2. This merge field returns the record's first name

sys-last

Slate will return a value in the following order of consideration:

  1. If a last name is collected on the form, this merge field returns that value

  2. This merge field returns the record's last name

Slate supports formatting standard date and time values for use in exports and merges. 

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"

 {{Form-Date | date: 'MMMM d, yyyy'}}

December 1, 2023

"1/31/2024 09:30 AM"

 {{Form-Date | date: 'h:mm tt'}}

9:30 AM

"2/15/2024 07:00 AM"

{{Form-Date | date: 'dddd, MMMM d'}} at {{Form-Date | date: 'h:mm tt'}}

Thursday, February 15 at 7:00 AM

For Exports in Queries

Selecting either the "DateTime" or "Date" Format Type for an export enables the designation of a Format Mask. This Format Mask uses the same syntax as Liquid markup.

datetimeformatmask.png

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 discussed in the previous discussion.

Date Formatting

Days

Format Specifier

Description

Example

d

Day of the month (1 to 31)

"12/01/2023 08:01 PM" → 1
"1/31/2024 09:30 AM" → 31

dd

Day of the month with a leading zero (01 to 31)

"12/01/2023 08:01 PM" → 01
"1/31/2024 09:30 AM" → 31

ddd

Abbreviated name of the day of the week

"12/01/2023 08:01 PM" → Fri
"1/31/2024 09:30 AM" → Wed

dddd

Full name of the day of the week

"12/01/2023 08:01 PM" → Friday
"1/31/2024 09:30 AM" → Wednesday

Months

Format Specifier

Description

Example

M

Month (1 to 12)

"12/01/2023 08:01 PM" → 12
"1/31/2024 09:30 AM" → 1

MM

Month with a leading zero (01 to 12)

"12/01/2023 08:01 PM" → 12
"1/31/2024 09:30 AM" → 01

MMM

Abbreviated name of the month

"12/01/2023 08:01 PM" → Dec
"1/31/2024 09:30 AM" → Jan

MMMM

Full name of the month

"12/01/2023 08:01 PM" → December
"1/31/2024 09:30 AM" → January

Years

Format Specifier

Description

Example

yyyy

Year

"12/01/2023 08:01 PM" → 2023
"1/31/2024 09:30 AM" → 2024

Time Formatting

Minutes

Format Specifier

Description

Example

m

The minute (0 to 59)

"12/01/2023 08:01 PM" → 1
"1/31/2024 09:30 AM" → 30

mm

The minute with a leading zero (00 to 59)

"12/01/2023 08:01PM" → 01
"1/31/2024 09:30 AM" → 30

Hours

Format Specifier

Description

Example

h

The hour, using 12-hour time (1 to 12)

"12/01/2023 08:01 PM" → 8
"1/31/2024 09:30 AM" → 9

hh

The hour, using 12-hour time, with a leading zero (01 to 12)

"12/01/2023 08:01PM" → 08
"1/31/2024 09:30 AM" → 09

H

The hour, using 24-hour time (0 to 23)

"12/01/2023 08:01PM" → 20
"1/31/2024 09:30 AM" → 9

HH

The hour, using 24-hour time, with a leading zero (0 to 23)

"12/01/2023 08:01PM" → 20
"1/31/2024 09:30 AM" → 09

AM / PM Designation

Format Specifier

Description

Example

tt

The AM/PM designator

"12/01/2023 08:01 PM" → PM
"1/31/2024 09:30 AM" → AM


Was this article helpful?