There are different ways to set up your event dates and ticketing structure based on how you want to offer access to your event or how the event will run.
To help you choose the best setup consider asking yourself the following questions:
Does your event repeat over multiple occurrences or sessions?
Yes: Read on
No: Option A
Are the ticket prices, ticket options or locations the same for each occurrence?
Would a buyer purchase multiple occurrences or experiences in a single order?
Does purchasing one ticket give a buyer access to all occurrences:
Of course, there can be exceptions to the following, so if you are unsure, feel free to contact the Humanitix support team using the messenger.
Option A: Single event
A single event is the most common type of event and the default option when creating your event draft. In this case, this is a standalone event that runs on a particular day and time.
Your date & time should be set as the date/time that the event starts and ends. Then add your available ticket type options, e.g. "General Admission", "Concession", etc
Note: Ticket sales start, by default, when you publish your event and will run until the event's end date.
Examples of single events include:
Live music gig on a Saturday night
Seminar or talk
Food and drink festival happening all day Sunday
Gala, luncheon, or awards night
Option B: Create repeating occurrences with a recurring event
A recurring event is an event that repeats on multiple occurrences or sessions. In a recurring event the experience, location, and ticket options are always the same.
During your event's checkout, a buyer will first choose the date and/or time they want to attend before selecting the number and type of entry tickets, e.g. "Adult".
Recurring events are also a quick way to offer the exact same event in the future without having to recreate the entire event.
Examples of recurring events include:
Musical performance running every night for 4 days
Yoga classes that run at 7am on Monday every week
A workshop that runs every month
Santa photoshoot with time-based entries every 30 minutes
We do not recommend using a recurring event if each occurrence is at a different location/venue or if ticket options, prices, capacities, and assigned seating arrangements change.
You can create a single event page and date with multiple ticket types, or create multiple event pages and showcase them all on a single link using a collection.
For example, a performance is running 'special pricing' for its opening 3 performances, then 'standard pricing' for the remaining occurrences. The event hosts create 2 event pages: 1 event page with tickets set at the special pricing and all applicable event dates, and the second event page with standard pricing with all other event dates. They showcase both event pages in a collection.
Option C: Create occurrences with ticket types on a single event
If your event has several occurrences or experiences that are unique to specific days, avoid creating separate ticket types for each session to prevent buyer confusion. Instead, you can create a single event with a long-running event date that spans all occurrences while presenting clear session distinctions within the setup.
In this set-up, buyers can choose to purchase one, multiple, or all sessions in a single order by adding the respective ticket type(s) to their order.
For example:
Expo offers entry tickets and several opt-in experiences over the week
Wellbeing series offers multiple seminars and workshops over a month
Weekend festival that offers single-day entry tickets and weekend passes. Buyers may attend more than one day.
If your event has assigned seating, we do not recommend using multiple ticket types on a single event page. We would recommend you create/duplicate separate event pages for each date and showcase them in a collection.
Do not create a recurring event, as all ticket types apply to each event occurrence. Use a single, long-running event start and end time.
Option D: Create an event that spans multiple days or weeks
If your event runs over several occurrences but is bought as a single, all-inclusive option, we recommend you create your event as a single event page with a long-running event date that spans all occurrences.
In your event checkout, buyers will only need to register a single ticket that gives them access to all sessions. They should not be able to purchase individual sessions.
Alternatively, this also works for events where attendees can attend at any time over the entire event.
Multi-day events that span :
8-week educational course that includes courses running each week, but cannot be purchased separately
Expo runs from Friday to Sunday. Buyers may attend any day or multiple days
Option E: Create multiple event pages and showcase them on a single event page
If you are running a series of events, each with different experiences, and/or the number of ticket options, prices, and capacities changes between each occurrence or event, it may be better to simply create multiple event pages.
This gives you the greatest flexibility and control in your ticketing, date/time, location, and assigned seating options.
Once your event pages are completed, you can showcase all of them on a single landing page using a collection. In your checkout experience, buyers can visit the collection page, choose which event they want to attend and then complete their ticket purchase.