Here you can see a complete list of all substitution codes that can be used in the Event module:

• [eventHeadline] The event headline
• Event description:
  • [eventDescriptionShort] Short description
  • [eventDescription] Long description (top)
  • [eventDescriptionBottom] Description at the bottom
• Event with online payment and an item linked directly
  • If the event has an item linked directly, information from the item can be merged into the event list with the following:
  • [eventHasItemShow_begin] and [eventHasItemShow_end] can be used to surround the following substitution codes:
    • [eventItemNo] is replaced by the item number
    • [eventItemName] is replaced by the item name
    • [eventItemPrice] is replaced by the content of the price field on the item
• Event location:
  • [eventLocationName] inserts the name of the location
  • [eventLocationAddress] inserts the address of the location
  • [eventLocationPostalcode] inserts the postal code of the location
  • [eventLocationCity] inserts the city of the location
  • [eventLocationShow_begin] the event takes place here [eventLocationShow_end] - used to include information about the location of an event, if any.
• Event image:
  • [eventImageUrl] inserts the url of the image.
  • [eventImageShow] : inserts 'hidden' if the event has no image (used to hide via css)
  • [noEventImageShow] inserts 'hidden' if the event has an image (used to hide via css)
  • [eventImageShow_begin] text in between [eventImageShow_end] If the event has no image, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
• Sign up several:
  • [signupMoreAtOnce] : inserts 'hidden' if signing up several at once is not enabled on the event (used to hide via css)
  • [nosignupMoreAtOnce] inserts 'hidden' if signing up several at once is enabled on the event (used to hide via css)
  • [signupMoreAtOnce_begin] text in between [signupMoreAtOnce_end] If signing up several at once is not enabled on the event, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
  • [signupNumSeats] is replaced by the number of seats chosen in a registration.
• Signup fields:
  • Specific field:
    [ef1234Show_begin] start code for the signup field with ID ef1234
    • [ef1234] is replaced by the content of the signup field with ID ef1234
  • [ef1234Show_end] end code for the signup field with ID ef1234
  • Example: [ef1234Show_begin] name : [ef1234]<br /> [ef1234Show_end]
  • All signup fields:
    [EACH_EVENTFIELD_BEGIN]
    <b>[eventFieldName]</b> : [eventFieldValue] <br>
    [EACH_EVENTFIELD_END]
• Seats:
  • [seatsLeft] Number of seats left
  • [seatsTotal] Total number of seats
  • [seatLimitationShow] : inserts 'hidden' if there is no seat limit (used to hide via css)
  • [noSeatLimitationShow] inserts 'hidden' if there is a seat limit (used to hide via css)
  • [seatLimitationShow_begin] text in between [seatLimitationShow_end] If there is no seat limit, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
• Date and time:
  • [eventWeekdayLong] Weekday - e.g. Monday
  • [eventWeekdayShort] Weekday - short - e.g. Mon
  • [eventDateStart],[eventDate] inserts the date of the event. E.g. 17/09/20
  • [eventTimeTo] Time to, e.g. 23:00
  • [eventTimeFrom] Time from, e.g. 17:00
  • [eventDateShow] : inserts 'hidden' if the event has no date (used to hide via css)
  • [noEventDateShow] inserts 'hidden' if the event has a date (used to hide via css)
  • [eventDateShow_begin] text in between [eventDateShow_end] If the event has no date, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
  • [eventOverSeveralDaysShow_begin][eventDateTo][eventOverSeveralDaysShow_end] used for events that last several days.
• Signup deadline:
  • [signupDeadlineShow] : inserts 'hidden' if the event has no signup deadline (used to hide via css)
  • [nosignupDeadlineShow] inserts 'hidden' if the event has a signup deadline (used to hide via css)
  • [signupDeadlineShow_begin] text in between [signupDeadlineShow_end] If the event has no signup deadline, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
  • [signupDeadlineDatetime] Date and time of the signup deadline. E.g. 17/09/20 12:00
• 'Show from date':
  • [openForSignupShow] : inserts 'hidden' if the event is not open for registration (used to hide via css)
  • [noopenForSignupShow] inserts 'hidden' if the event is open for registration (used to hide via css)
  • [openForSignupShow_begin] text in between [openForSignupShow_end] If the event is not open for registration, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
  • [openForSignupDatetime] Date and time when the event is open for registration. E.g. 17/09/20 12:00
• Open for registration:
  • [openForSignupDatetime] Date and time when registration opens. E.g. 17/09/20 12:00
  • [openForSignupShow] : inserts 'hidden' if the event is not open for registration (used to hide via css)
  • [noopenForSignupShow] inserts 'hidden' if the event is open for registration (used to hide via css)
  • [openForSignupShow_begin] text in between [openForSignupShow_end] If the event is not open for registration, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
• Unsubscribing from a registration:
  • [unsubscribeShow_begin] text in between [unsubscribeShow_end] If unsubscribing is not enabled on the event, everything between begin and end is removed (used to hide blocks in e-mails where css cannot be used)
  • [unsubscribeEventLink]&dTpl=1 inserts the link to the unsubscribe page. (&dTpl=1 makes the template for direct links be used)
  • [unsubscribedatetime] is replaced by the date and time of the unsubscribe deadline, e.g. 16/09/20 12:00
• Customers
  • [newCustomerBegin] and [newCustomerEnd] can be used to insert information when new customers are created.
  • [noNewCustomerBegin] and [noNewCustomerEnd] can be used to insert information for existing customers.
• Video meetings
  • [VideoMeetingShow_Begin] and [VideoMeetingShow_End] this substitution code pair can be used together with the substitution codes for video meetings if a video meeting is linked to a specific booking or service, and you want the confirmation and reminder to contain the video link [VideoMeetingUrl] and any other text for the video meeting.