To assist with the email creation process, several pre-configured email templates have been created for you to choose from. If you prefer to create your own email, and not use the templates, please read this article.
The pre-configured email templates are generically branded and contain placeholder text for you to input your own event-specific text in. For more information about updating pre-configured email templates, please refer to this article.
Pre-configured email templates include:
- Attendee - app details - personal login credentials
- Attendee - app details - generic (no login)
- Attendee - app details & digital passport competition
- Attendee - lead capture
- Exhibitor - lead capture details - personal login
What each template includes is outlined below.
TIP:
Information in the { } brackets will auto-populate with this information. For example, {FIRST NAME} will populate with the attendee’s first name from their profile in the CMS. {AUTH LINE ONE NAME} will populate with the name of the first line of authentication you have chosen (e.g. Username) etc. A full list of the available merge tags can be found here.
Attendee - app details - personal login credentials
This email template is perfect for launching your event app to attendees. Update the text to introduce your event and provide important event information. This template also contains download and personal login instructions for attendees to access the app.
The following information is required to populate this template:
- Attendee first name
- Email introduction / event introduction
- Event details (date, start time and location)
- Event app (standalone or embedded)
- Project event code (for an embedded app)
- 2-line profile authentication (e.g. Username and Password)
Attendee - app details - generic (no login)
This email template is great for launching your app to attendees who aren’t required to log into the event app. Update the text to introduce your event and provide important event information. This template also contains download instructions for attendees to access the app.
The following information is required to populate this template:
- Attendee first name
- Email introduction / event introduction
- Event details (date, start time and location)
- Event app (standalone or embedded)
- Project event code (for an embedded app)
Attendee - app details & digital passport competition
This email template is perfect for launching your event app and passport competition to attendees. Update the text to introduce your event and provide important event information. This template also contains download and personal login instructions for attendees to access the app.
The following information is required to populate this template:
- Attendee first name
- Email introduction / event introduction
- Event details (date, start time and location)
- Information about the passport competition (e.g. prizes, how to participate etc.)
- Event app (standalone or embedded)
- Project event code (for an embedded app)
- 2-line profile authentication (e.g. Username and Password)
Attendee - lead capture
This email template works great as a followup email. It contains information about Lead Capture, and how attendees can share their personal information through scanning. Update the text to introduce your event and provide additional information about the exhibition.
The following information is required to populate this template:
- Attendee first name
- Email introduction / event introduction
Exhibitor - lead capture details - personal login
This email template is great for communicating important Lead Capture information with exhibitors. Update the text to introduce your event and provide additional information about the exhibition. This template also contains download and personal login instructions for exhibitors to access the Capture app.
The following information is required to populate this template:
- Exhibitor first name
- Email introduction / event introduction
- Capture app (standalone or embedded)
- Project event code (for an embedded app)
- 2-line profile authentication (e.g. Username and Password)