Communications for Related Events

Most event structures that use Related Events only require a single master event template form with a single set of communications. There are two circumstances when this may change:

Internal Fields
If a Related Event requires additional administrative processing and complex communications based on these processes, create a form for that event template with Internal Only fields.


If communications should be sent with this information, build 'Upon Update' communications for the Related Event Template.


Do Not Delete!

By default, a number of standard fields are included on every event registration form. Do not delete these standard fields when editing the forms for Related Events.


If there is a strict registration limit for a certain Related Event, and an accurate guest count needs to be captured, ask how many guests will accompany the prospective student on the Master Campus Visit registration form using the special form field Guests.

By default, Guests are not registered in the Related Event registration. This prevents guests from being included in the registration count for events like Class Visit or Overnight Visit, where just the prospective student will attend that event.

To include the Guest count for a Related Event, that event template’s registration form must also include the special form field Guests.


Constituent events selected using Related Events Selectors are available as merge fields for event communications. Use these merge fields to list the registrants itinerary. For example:


  Best Practice

Keep it simple! If the 'Upon registration' communications require complex conditional logic, consider using Event Structure C instead.

If a follow-up communications require complex conditional logic based on which constituent events were selected, create a communications campaign for the constituent event templates.

Conditional Logic

Conditional logic may be added in event communications for the master template to convey information about the specific Related Events that the registrant selected. 

Use the 'not equal' comparison operator with the null string to determine if the registrant made a selection for that Related Events Selector:

{% if {{related_infosession}} != null %}
We are looking forward to seeing you at the Group Information Session!
{% endif %}

This condition statement will evaluate to true only if the registrant selected an event for the Related Events Selector with the export key related_infosession.

If there are special instructions for certain Related Events, use the contains comparison operator to determine which event was selected:

{% if {{related_infosession}} contains '03:00 PM' %}
Your Group Information Session will meet in room A210.
{% elsif {{related_infosession}} != null %}
Your Group Information Session will meet in room A100.
{% endif %}

This condition statement will evaluate to true if the selected event starts at 3:00 PM. For example, Tuesday, March 10 at 03:00 PM - Information Session.


Since the text stored for the Related Events Selector field changes based on the specific event selected, the 'equal' comparison operator cannot be used effectively. Use the 'contains' comparison operator instead.


If cancelling a Related Event, the event data will still pull through into an hours-out communication for the Master Event unless the registration status for the student is also set to cancelled.

Be sure to configure a cancellation email on the Related Event to communicate that this particular related event has been cancelled. That way, when the student sees an updated agenda from the main event, they won't be surprised to see that something they initially signed up for is no longer present.

Was this article helpful?
5 out of 10 found this helpful