What are sessions and how do they work?

Created by Ticketing Support, Modified on Mon, 26 Oct at 2:55 AM by Ticketing Support

A session is one date and time your event runs. Most events have one session. If your event runs more than once, such as a weekly show, add a session for each date and sell them all from one event page.

Add a session

  1. Open your event and go to the Details step.
  2. Under Event sessions, click Add Session.
  3. Enter a Session Title if you want one, for example "Saturday Matinee".
  4. Enter the Max Capacity.
  5. Choose the Session Start/End Date, Start Time and End Time.
  6. Click SAVE SESSION.
  7. Click Save & Close.

Session status

Each saved session has its own status:

  • LIVE: on sale.
  • DRAFT: set up, but not on sale yet.
  • INACTIVE: taken off sale.

To change it, open your event's Details step and choose the status from the menu next to the session. Then click Save & Close.

To change a session's title, capacity, date or times, click the pencil icon next to it, make your changes and click SAVE SESSION.

Sessions or a tour?

Sessions are the dates of one event at one venue. When an event has several sessions, buyers choose the one they want on that single event page.

A tour groups several events on one page. The events can be at the same venue or at different venues. Buyers choose an event on the tour page, then buy on that event's page.

A tour of events at the same venue is useful too. Buyers pick their day on the tour page instead of the event page. That can suit your marketing, the way you like to set things up, or a mix of same-venue and different-venue dates.

Some examples:

  • A weekly comedy night at one club: one event, with a session for each week.
  • A show visiting Sydney, Melbourne and Brisbane: a tour, with one event for each city.
  • A three-day festival at one site, where each day has its own line-up and marketing: a tour, with one event for each day at the same venue.
  • A theatre season with two weeks in Sydney and one in Perth: a tour with a Sydney event and a Perth event, each with a session for every performance.

For complex events and tours, you can combine both: a tour whose events each have several sessions.

How capacity works

Capacity is the most people who can attend a session, whatever tickets they buy. With a capacity of 100, you could sell 100 single tickets or 50 double passes. Sales stop when the session is full.

Ticket tiers across sessions

Your tiers are shared by all your sessions. Each session gets the tier's full Quantity. For example, a tier of 50 tickets on an event with two sessions gives you 50 for each session.

At the top of the Tickets step, choose which sessions you're working on:

  • All sessions: changes apply to every linked session. The Sold column shows the total across sessions.
  • One session: shows that session's sales. Tiers marked Linked follow your All sessions settings.

To give one session different settings, such as a different price, choose that session and click the unlink icon next to the tier. That tier can then be changed for that session alone. Unlinking can't be undone, so read How do I set up different tickets for each session? first.

Tiers that stop selling when the event ends stop at the end of each session, so every session stays on sale until it finishes.

What buyers see

  • Your event page shows the full date range, for example "21 - 22 Nov".
  • When buyers click BUY TICKETS, they choose a date on a calendar, then a session, then their tickets.
  • Past sessions disappear from your event page.

Sessions in your admin

  • Your Events list shows a row for each session.
  • Downloads and reports are for one session at a time. Use Event actions on the session's row.
  • Coupons work for one session each.

Still stuck?

Submit a support request.

Related articles

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article