Tickets

Tickets belong to one event. To add one, open the event from Events → All Events, open Tickets in the event editor, and choose Add Ticket. Events saves a free, unlimited ticket called General Admission straight away and opens it in Edit ticket.

• Ticket name: required. Events won't save the ticket without one.
• Price: what one ticket costs. At 0 the ticket is free, and buyers register without paying.
• Quantity: how many you sell. 0 means unlimited.
• Description: a line shown under the ticket's name.
• Group: the tier group the ticket sits in, once the event has groups. Tickets start as Ungrouped.
• Apply ticket type: optional, a reusable ticket type from Tickets → Ticket Types. It starts as No type.
• Discount codes: tick the codes buyers can use on this ticket. A code works only on the tickets where it's ticked. You create codes under Tickets → Discounts & Codes (see Discounts & ticket rules).

Choose Save. Cancel keeps the ticket as Events first saved it, so delete it if you don't want it.

By default, Tickets appears in the sidebar for the Owner, Admin and Manager roles. To change who sees it, see Roles and permissions. The event editor's Tickets group isn't limited by role: anyone who can open an event can change its tickets.

A ticket is what buyers pick on the event page. It lives on one event and has its own name, price, quantity and description. Two reusable records in the Tickets sidebar area add to it:

• A ticket type (Tickets → Ticket Types) is a set of rules and attendee questions you apply to tickets on any event. It has no price of its own.
• A tier (Tickets → Ticket Tiers) is a level such as General, VIP or Platinum. Adding a tier to an event creates a group, and the event page lists that group's tickets under the tier's name.

The rest of selling is set per event, in the event editor's Tickets group: assigned seats (Seating), held tickets (Reserved Seating), extras (Offerings and Purchasables), time slots (Slots), the tickets card's buttons (Call to action and Ticket Selection), Express Lane and the Purchase Disclaimer.

Discount codes, bundles, early-bird prices, access codes and the other ticket rules are covered in Discounts & ticket rules. Payment methods, currencies, refunds and invoices are covered in Payments & policies.

The Tickets section of the event editor shows each ticket with its price (or Free), how many are available (or Unlimited), its waves from Batched Releases, its ticket type and that type's visibility, and the discount codes it accepts. A ticket with no type shows No Rules Applied.

• Click a ticket, or choose Edit in its ⋯ menu, to change it in Edit ticket. Changes save when you choose Save.
• Move up and Move down change the ticket's place within its group. The event page lists tickets in the same order.
• Delete removes the ticket straight away, without asking. Orders already placed keep the ticket's name.

Add at least one ticket before you publish. An event with no tickets shows a stand-in ticket on its event page (General Admission, or Free registration for an online event), and buyers can buy it.

Under the tickets, Attach Dietary & Accessibility inquiry adds the project's dietary and accessibility questions to this event's checkout. It saves straight away when you switch it. You write the questions under Registrations → Dietary & Accessibility (see Registrations).

A ticket type is a reusable set of rules and questions for tickets. To create one, choose Tickets → Ticket Types in the sidebar, then New ticket. Type a Name (required) and choose Create. The type opens on its edit page, where Save keeps your changes. To use it, pick it in a ticket's Apply ticket type field in the event editor.

Checkout applies two parts of a ticket type:

• Visibility, on the Visibility & access tab: Public (the default) or Hidden. Hidden tickets don't appear on the event page or in Express Lane.
• Questions: asked of each attendee at checkout.

The other settings save with the type and show in its summary, but checkout doesn't enforce them: the Sales window and Order limits on Availability, the Refund policy tab, the Scheduled visibility option, Access-code gating and Reserved seating. Buyers can request a refund of any paid order from the members portal, whatever the type says. To hide tickets behind a code, use Access Codes in Discounts & ticket rules. To hold tickets back or sell assigned seats, use the event's Reserved Seating and Seating sections.

The list shows each type's name, a summary such as Refundable · Public · 2 questions, and its status. Active and Inactive are for your own sorting: an inactive type still applies to its tickets. Filter by status, search by name, and use each row's ⋯ menu to Edit, Deactivate or Activate, or Delete. Events asks you to confirm a delete, and a deleted type stops applying to the tickets that used it.

A ticket type's Questions tab holds what checkout asks each attendee before they pay. To add one, open the type in Tickets → Ticket Types, choose Add question, and fill it in:

• Question label: the question. Questions start as Untitled question.
• Response type: Short text (the default), Paragraph, Number, Email, Dropdown or Checkbox. For a dropdown, type its Options separated by commas, like Small, Medium, Large.
• Required: buyers can't continue until it's answered.

Each question's wording, response type and Required switch save as you edit them. Adding questions and reordering them with the ▲ and ▼ arrows take effect when you choose Save. The trash icon deletes a question straight away, without asking.

Checkout asks the questions once per ticket in the order, headed Attendee 1 of 3, Attendee 2 of 3 and so on. Events stores the answers, but no screen in Events shows them.

To create a tier, choose Tickets → Ticket Tiers in the sidebar, then New tier. Type a Name (required) and choose Create. The tier opens on its edit page:

• Rank: where the tier sits, from 1. Lower ranks show first, and tiers with the same rank sort by name.
• Accent: the dot that marks the tier: Slate (the default), Emerald, Amber, Violet or Rose.
• Description: what the tier includes. It shows under the group's name in the event editor.

Choose Save to keep your changes. The list, its filters and its ⋯ menu work the same way as for ticket types.

To use a tier on an event, open the event's Tickets section, choose Add Group and pick the tier. Add tickets with the group's own Add Ticket, or move a ticket in with its Group field. The event page lists each group that has tickets under its name and accent, by rank, then the ungrouped tickets.

The trash icon on a group removes it straight away, and its tickets become ungrouped. The event page keeps a tier's name, accent and rank as they were when you added the group, so after changing a tier, remove the group, add it again and move its tickets back. Deleting a tier doesn't remove its groups from events.

To sell assigned seats, the event needs a venue with a seat map. Set the venue in the event editor's Location & Time section. Seat maps are built on the venue (see Venues & sourcing). Then open Seating:

1. In Seat map, pick one of the venue's maps. No seating (general admission) is the default.
2. In How buyers choose, pick Map first (the default), where the section sets the price, or Ticket and quantity first, then pick seats.
3. In Section pricing, map each section to one of the event's tickets. The section sells at that ticket's price. A section left as Not sellable can't be bought.
4. Optional: change Hold seats for, the minutes a buyer's chosen seats stay held while they check out: 1 to 60, 10 by default.

Each choice saves as you make it, and Hold seats for saves when you leave the field. With Map first, buyers pick seats on the map before anything else, all from one section, and the quantity follows the seats. With the other option, buyers choose a ticket and quantity, then pick that many seats in the sections mapped to that ticket. Once a buyer goes to pay, Events holds their seats for 30 minutes.

Box office shows every seat as sold, held off sale or open, with counts. Click an open seat to hold it off sale, or a held seat to release it. Sold seats can't be changed there. Refresh reloads the map.

Reserved Seating holds back part of each ticket's quantity from public sale, for guest lists, press or sales you handle yourself. It doesn't use a seat map. To turn it on for an event, open Ticket Rules in the event editor and turn on Reserved seating (see Discounts & ticket rules). A Reserved Seating section then appears in the event editor's Tickets group.

The section lists each ticket with its quantity and how many are sold, reserved and available. Type how many to hold in Reserved: it saves as you type and can't go over the ticket's quantity. Note is optional and saves when you leave the field. Held tickets come off what buyers can buy online, and they count against the event's capacity too. To release them, lower the number.

In the sidebar, Tickets → Reserved Seating lists your events on its Events tab, marked Reserved seating or General admission by whether the rule is on. Its other settings (Enable reserved seating, Pick-your-seat, Seat hold and Default seat map) save with Save Changes but don't change how any event sells. Seat holds and seat maps are set per event in Seating.

The tickets card on the event page has a main button whose wording changes on its own: Get Tickets, Register when the selected ticket is free, and Sold out when nothing's left. To change the buttons, open Call to action in the event editor. Nothing changes on the page until you choose Save buttons.

• Label, under Get Tickets button: your own wording for the main button. Leave it blank for the automatic wording. A sold-out event still shows Sold out.
• Add button: a button under the main one, with a Label, a Links to address (a web address, a #section of the page, mailto: or tel:) and a style: Primary, Outline (the default) or Text. A button with no label or an unusable link doesn't show. Web addresses open in a new tab, and these buttons stay clickable when the event sells out. The grip moves a button up one place, and the trash icon removes it.

Ticket Selection replaces the main button with two routes: one opens the seating plan, the other lets buyers pick a ticket by price. Open it, turn on Enable selection modes, and choose Save.

• Routes shown: Seating plan and by price (the default), Seating plan only, or By price only. The seating-plan route needs a seat map in Seating.
• Seat-plan button label and By-price button label: the buttons' wording.
• Feature highlights: chips for Selection based on plan, Cancellation insurance and Digital ticket. They're labels only: Events doesn't add insurance to orders.
• Booking notes: numbered footnotes. Sold out shows only when the event is sold out.

With Map first seating, the by-price route sells a ticket without a seat, and Events doesn't assign one. The default Automatic seat assignment note says otherwise, so rewrite or clear it.

Offerings are choices or extras buyers pick on the checkout's details step, such as a meal preference. To add one, open Offerings in the event editor and choose Add offering:

• Name: required. Description is optional.
• Selection: Single choice (radio), the default, or Multiple choice (checkbox). Turn on Require a choice to make buyers pick one of a single choice's options.
• Offered with: All tickets (the default) or the tickets you pick. Tickets are matched by name, so after renaming a ticket, pick it again.
• Options: at least one, each with a label and a price. Leave the price at 0 for a free option.

Choose Add offering to save it. On each offering, the switch turns it off and on, the arrows reorder it, the pencil edits it, and the trash icon deletes it after you confirm. Each change saves straight away.

An option's price is charged once per ticket in the order. While the event has any purchasable turned on, checkout shows purchasables instead of offerings.

Purchasables are add-ons checkout offers on an Add-ons step after the buyer's details, each shown only when its conditions match. To add one, open Purchasables in the event editor and choose Add purchasable. Only Name is required, and Price starts at 0, which makes it free.

• Allow buying multiple: gives buyers a quantity stepper, up to Max quantity per item (blank for no limit). Off, buyers tick it once.
• Required to check out: buyers can't continue without it when it's shown.
• Available: turn it off to hide the add-on without deleting it.
• Conditions: with none on, everyone sees it. Turn on any of Time band, Specific slots, Ticket types (the event's tickets), Tickets in cart (a minimum and maximum), Cut-off before the slot, Requires another add-on and Excludes another add-on, then choose Match all (the default) or Match any.

Choose Add purchasable to save it. The switch, arrows, pencil and trash icon on each one work as they do for offerings. Prices are charged once per ticket in the order: two tickets with a $10 add-on add $20. Time band, slot and cut-off conditions match only once the buyer picks a slot. Checkout doesn't recognize members, so an add-on with Members only on never shows.

Slots let buyers book a time, such as an evening seating, as part of checkout. To set them up, open Slots in the event editor and turn on Allow slot booking, which saves straight away. Picker label is the heading buyers see (Choose your time to start with), and Require a slot to check out is on by default.

Choose Add slot. A Name and a start time are required.

• Starts and Ends: the date and time. The end is optional.
• Time band: Morning, Afternoon, Evening or Night, set from the start time unless you pick one. Purchasables can use it as a condition.
• Capacity: how many tickets the slot takes. 0 means unlimited.
• Price adjustment: added to each ticket's price for this slot.
• Location: an optional room or area.
• Booking cutoff: how many hours before the start booking closes. Blank means it doesn't close.
• Bookable with: All tickets, or the tickets you pick.
• Slot available: turn it off to hide the slot.

Choose Add slot to save it. Each slot shows its time, location, time band and how many are booked against its capacity, and its switch, arrows, pencil and trash icon work as they do for offerings. At checkout, a slot shows how many places are left once 10 or fewer remain, and Full or Closed when it can't be booked.

Leave Offer a waitlist when full off: it keeps a full slot selectable, but Events can't complete an order for a full slot. Max per order isn't applied at checkout.

Express Lane is a two-click checkout: buyers pick a ticket, choose Pay, and give their email and card to Stripe. To turn it on, open Express Lane in the event editor, turn on Enable Express Lane, and choose Save.

Express Lane runs only when checkout needs nothing typed in. Readiness lists anything in the way, with Fix to open the section concerned: online payments turned off, a seat map in Seating, an exhibitor floor, registrations that need approval, a required slot, a required offering or purchasable, or a required registration question. Only paid tickets that aren't sold out go express. If the chosen ticket has required attendee questions, choosing Pay moves the buyer to the full checkout.

• Placement: Extra button under Get Tickets (the default), labeled with Button label, or Get Tickets opens Express Lane.
• Tagline: the line at the top of the express screen.
• Pre-selected ticket: Whichever is selected on the page (the default), or a ticket you pick.
• Let buyers switch ticket, Let buyers change quantity, Ask for the buyer's name on Stripe, Pre-fill signed-in buyers and Offer the full checkout: all on by default. Most tickets per order starts at 6.

A purchase disclaimer with a tick-box adds a third click. Preview shows the express screen as buyers see it.

A purchase disclaimer is text buyers accept before they pay, such as your terms of sale. To add one, open Purchase Disclaimer in the event editor, turn on Ask buyers to acknowledge before buying, write the Disclaimer, and choose Save Disclaimer. An empty disclaimer never shows.

• Require a tick-box: on by default. Buyers tick the box, worded by Tick-box label, to continue. Off, choosing the Pay button (Agree & continue) counts as acceptance.
• Applies to: every order (the default), including free orders and approval requests, or Paid orders only.
• Heading: Before you buy, unless you change it. Each line of the disclaimer becomes its own paragraph.

The disclaimer shows on a final Review step next to the order summary, and the button that finishes the order stays off until it's accepted. In Express Lane it shows over Pay. Preview shows what buyers see. For fine print that doesn't need accepting, use the event editor's Disclaimer section instead (see Event page).

Buyers pick a ticket on the event page's tickets card and choose its main button, which opens checkout. The card lists each ticket with its price (or Free), grouped by tier, and how many tickets remain unless Show tickets remaining is off in the event's Registration Settings.

Checkout runs in steps, each one only when the event needs it:

1. Seats: with Map first seating, buyers pick seats before anything else. With an exhibitor floor, they pick a booth instead (see Sponsors & Expo).
2. Details: the quantity, a time slot, offerings, a donation and a discount code, then the buyer's name and email, registration questions, the dietary and accessibility inquiry, and the ticket type's questions for each attendee.
3. Seats: with Ticket and quantity first seating, buyers pick that many seats.
4. Add-ons: the purchasables whose conditions match.
5. Review: the order summary and your purchase disclaimer.
6. Payment: paid orders go to Stripe. A free order ends with Complete registration, and an event that needs approval ends with Request to register.

A buyer can take up to 10 tickets in one order, or fewer when fewer are left. Group orders can go higher (see Discounts & ticket rules).

Paid orders are charged on Stripe's checkout page, in the currency set in the event's payment settings (see Payments & policies). If online payments are turned off for the event, buyers can't complete a paid order. A buyer who backs out of Stripe returns to the event page and isn't charged.

Once Stripe confirms the payment, Events records the order (see Orders) and emails the buyer their tickets: the order number, an entry QR code, the ticket and the total paid. The QR code holds the order number, which check-in scans (see Check-in).

The confirmation screen shows whether the email went out. Buyers can choose Resend once a minute, and Events stops after five sends. The email is the Purchase confirmation notification under Settings → Notifications (see Settings). With it off, the confirmation screen tells buyers the event doesn't email tickets.

Free orders and approval requests get no ticket email. Attendees see every order made with their email in the members portal (see Signing in).

You add or change tickets, and then another section of the event editor (Seating, Reserved Seating, Offerings, Slots, Purchasables, Batched Releases or Express Lane) doesn't list them, or Tickets shows the old list when you come back to it.

The event editor works from the copy of the event it loaded when you opened the event, and changes in the Tickets section don't update that copy. Your changes are saved, but changing tickets from the old list saves that list over them.

1. After you change tickets, reload the page in your browser.
2. The event editor opens on the same section, with your saved tickets.