Overview
Sometimes it can be useful to communicate to guests the contents of custom fields held against their guest record. For example, you may have populated custom fields regarding travel and accommodation options that you now wish to communicate to guests.
If you have custom guest fields enabled for an event, a list of custom guest email tags will be created automatically.
How custom guest email tags work
When creating or editing guest email templates, there are two sets of tags:
- Standard guest email tags - such as ${firstname} and ${lastname}
- Custom guest email tags - in the format ${#customfieldname}
You can place as many custom email tags in your emails as required. If a field's data is blank then no data will be populated in the final guest email.
If you see a tag in the final email because it has not been replaced by a data value, that means the tag is not supported in the current email. In this case, check for typos and which fields are enabled for the event (Edit Event > Guest Fields tab).
Viewing available tags for an event
When you are editing a guest email template or sending a custom guest email, if you have custom guest fields enabled, you will see a list of "Custom guest tags" appear on the right hand side of the email.
Email templates which support custom guest email tags
The following guest email templates support custom guest email tags:
- Guest Invitation
- Guest Invitation Reminder
- Guest Invitation Accepted
- Guest Custom Email
- Guest Pre-event Email
You should beard in mind that any fields with a guest visibility setting of "View & Edit" will only populated during the registration process, so data will not be populated in the Guest Invitation or Guest Invitation Reminder process.
Naming convention for custom guest email tags
The name format for custom email tags is the field name with any spaces and special character removed. Long fields will have their tag truncated after the first 20 characters.
For example:
- A "Hotel Room" field would have a tag of ${#hotelroom}
- A "Flight Booking Arrangements" (25 chars without spaces) would have a truncated tag of ${#flightbookingarrange}
Comments
0 comments
Article is closed for comments.