What You'll Learn

  • How to personalize messages with tokens
  • The different tokens you can use

Related

Event451 is all about customization and personalization and this is especially true when sending messages to your attendees. We want you to be able to address each attendee by name and reference details about their registration that make your communication useful and unique — even when that communication is going out to many people at once! Tokens are a great way to do this.

Tokens are essentially a small bit of code that works like a placeholder. When you're writing a message, you see the token as something like [event:event_name] in your text. When the person receiving the message sees the message, the token is replaced with real content. For example, if the name of the event they registered for is called "Fall Open House," "[event:event_name]" would appear as "Fall Open House."

On this page, we'll explain how to use tokens, and provide a list of tokens you can insert into messages. 

How to Use Tokens

Including a token in your email and SMS messages is simple. All you need to do is enter the token text enclosed in brackets [ ] in the content of your message. 

Where to use them:

  • Subject line of an email
  • Body of an email or SMS message

Example

The following images show you what tokens look like in the editor of an event message, and then in the email that an attendee receives. Notice that all of the tokens are inside of brackets in the message editor. You can see that tokens were used for the attendee's name, event name, event date, and the personal registration URL for the attendee. The personal registration URL is where people can manage their registration, e.g. change date, cancel.

Token List

The following is a complete list of available tokens in Event451. We update this list as more tokens are added.

Remember to enclose the tokens in brackets [ ] when using them.

  • user:user-first-name | First name of user
  • user:user-middle-name | Middle name of user
  • user:user-last-name | Last name of user
  • event:event_site_url | URL (web address) of event website homepage
  • event:event_url | URL (web address) of the specific event page (e.g. myuniversity.edu/event/451)
  • event:event_name | Name of the event
  • event:event_image | URL (web address) of the event image
  • event:event_type | Type of the event
  • event:event_categories | All of the event categories separated by commas
  • event:event_start_date | First date this event occurs (Recurring Events)
  • event:event_end_date | Last date this event occurs (Recurring Events)
  • event:event_start_time | Start time of the event
  • event:event_end_time | End time of the event
  • event:event_venue_name | Name of the event location
  • event:event_venue_address | Street address of the location (does not include building name or room number)
  • event:event_venue_building I Building name of the event location
  • event:event_venue_room | Room number of the event location
  • event:event_venue_city | City of the event location
  • event:event_venue_state | State of event location
  • event:event_venue_country | Country of event location
  • event:registration_guid | User's unique registration ID
  • event:registration_update_url | User's unique registration URL. Can be used to update the registration information.
  • event:registration_date | Date of the event that the attendee registered for including time. "Mon March 15 at 11:00am"
  • event:registration_create_date | Date that the user's registration record for this event was first created
Did this answer your question?