Let the platform do the work

Use Case: Multi-Session Event

Creating a Multiple-Session Event

Multiple Session Events in Sugar Market provide an all-encompassing event management platform that facilitates the creation, management, and tracking of all of your marketing events. Run live, face-to-face roadshows or webinar event sessions integrated with GoToWebinar. Multi-session events allow marketers to maximize efficiency by sending a single invite to a list of prospects and allowing them to register for multiple events at once through a single registration form. Dynamic confirmation emails will go out based on the event(s) the contact registered for, as well as dynamic reminders and dynamic follow-ups. All post-registration communication can be set up with a single email template pulling information from the registered event.

Multi-Session Use Case

  • Event Type: User Conference
  • Locations: Seattle, San Francisco, Austin, Chicago, Boston, and Atlanta.
  • Communication Plan Needed: Invitation, confirmation email with details specific to the location where they registered, reminder emails just days before the event with additional details such as venue directions, agenda, etc.
  1. Create the framework for a multiple-session event. 
    • Choose the number of sessions, 1 for each city
    • Enter session details for each location. Date, time, location, etc.
    • Set up the framework for your first invite, reminders, and follow-ups. Remember the invitations will all go at the same time, but your trigger emails will be dynamic based on which session the contact registers for.
    • The Landing Page framework should be established for your registration page - you can go back and add a second landing page later with a customer survey if you like.
  2. Now it's time to fine-tune your event. Remember you have a number of sessions in this event. Think of each session as a city and the overall Event is the User Conference.
  3. Open the Seattle session first, and review the following:
    • Beside each field in the session is a merge tag icon that you can click to copy the merge tag. Adding the merge tag to your trigger email will populate the value based on the specific session. For example, when you want your confirmation email to include "Thank you for registering for our Seattle User Conference" The text in your HTML for the trigger should actually read 'Thank you for registering for our ++Event.EventName++ ' (Where Seattle User Conference is the name of the Session).
    • Before testing, make sure the Status is set to 'active.' You will not be able to edit portions of the session once this status is set to active, but the value must be as such in order to test and for customers to register.
  4. Add and Adjust invitations leading up to your events. Remember, you cannot use session merge fields in an invitation. The contact must have registered for an event to use these, so we know which session to pull the data from.
  5. Once your invitations are set, open and review each of your trigger emails. Make sure the subject line is correct and the content is accurate. Remember, in the trigger emails you can leverage merge fields from the session to dynamically pull in content.
  6. Finally, let's review your landing page to make sure it's ready to go. As with any Landing Page, make sure you review the following:
    • Page names are set with unique and customer-facing names
    • Page content is updated & published highlighting the registration form. I also recommend including content on the registration page with information about the event. This will inform anyone who comes to the registration page through social media and never received the email with event information.
    • Adjust the questions on the first page. For live events where food will be served, I always ask for food allergies. This makes sure I have options for gluten free, dairy free, vegetarians, etc.

The basics are complete. All you have to do next is preview and test. Remember when testing your trigger emails, you will need to select the session for which you want the trigger to test.