Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Give the event a Name

  • Give the event a Event Url Suffix to create the event url, for example http://events.gomeddo.com/hollanduniversity/openday
    The event url suffix is “openday”

  • Enter the Contact Email, if visitors will reply to the ticket email, they will be sent to this emailadress

  • Enter the Email signature, this will be the signature in the email of the tickets.

  • Privacy statement, will provide a link to the privacy statement applicable to this event (url field)

  • Terms & Conditions, will provide a link to the terms and conditions applicable to this event (url field)

  • Description, here you can enter the description of the main event.

  • Location, here you can add the location of the event.

  • Capacity, this will be the capacity of the main event, it’s not possible to book more tickets then this number

  • Visitor fieldset, the visitor object can be extended with more fields, putting the name of the visitor fieldset will extent the “visitor form” when booking a ticket. Extending the visitor information and form

  • Use custom email template, this settings allows you to disable the standard email and pdf creation.

Event dates

  • Start: This is the date & time when the event actually takes place

  • End: This is the date & time when the event actually ends

  • Visible from: This is the date & time when the event is visible to book (empty is always visible)

  • Visible untill: This is the date & time when the event is visible to book (empty is always visible)

Styling

Frontend-view, here you can determine if your visitors will select tickets or events.

Ticket view

...

  1. Image, here you can add a url to an image specific for this main-event. This will be shown on the website and tickets to visualize the main event

  2. Icon, here you can add a url to an icon for this event, this will be shown on top of the page and will be your main events “branding

  3. Completed State Color, here you can specify a hex code which will determine the color of the “allready completed” steps.

  4. Selection Color, here you can specify a hex code which will determine the color of the “selected events” on the website

  5. Background color, here you can specify a hex code which will determine the background of the website.

  6. Call to action color, here you can specify a hex code which will determine the color of the “action buttons”

...

Create sub-event (session)

...

  • Image, here you can add a url to an image specific for this sub-event. This will be shown on the website and tickets to visualize the subevent as a card