You turn on Tickets in Event settings with the Tickets toggle. The system then handles online card payments (including Apple Pay and Google Pay), proforma invoices with automatic due dates, discount codes, and ticket groups for different attendee types. This article covers how to create a ticket and what to set up before you publish it.
Decide on the pricing model — one ticket type, multiple types (early bird / standard / VIP), bundles, or individual free invitations.
Decide whether you want Registration with additional information (after payment, the attendee still goes through the form) or Automatic registration after ticket purchase (the ticket arrives immediately, no form). See Setting the registration type and additional questions for details.
Prepare your billing data, invoice items, VAT, and currency.
For paid events, you cannot combine Tickets with Approved registration. Required contact fields are governed by the Registration form.
For GTM tracking codes, contact customer support.
In the event menu, open Event settings → the Tickets section and switch on the toggle. A new Tickets item appears in the left menu, along with the required follow-up steps:
Choose the currency — CZK or EUR (other currencies on request).
Choose the registration type after purchase — Automatic registration after ticket purchase or Registration with additional information.
If you use Registration with additional information, the system reminds you to set the required contact fields in the Registration form.
When Tickets are active, you must create at least one ticket. Otherwise registration for the event is closed.
In Tickets, click + New ticket. Fill in:
Ticket name — the name the attendee sees (for example, Standard, VIP, Early Bird).
Invoice item — the item name on the tax document (can differ from the ticket name).
VAT — the tax rate.
Price excl. VAT — the calculator computes the total price.
Description — an optional description for the attendee in the purchase view.
In the open ticket on the Attendee details tab, you set which contact fields are required:
For Registration with additional information, the required fields are governed by the Contact details in the Registration form. In the ticket panel they are shown as required automatically and cannot be changed here. You can also choose whether to hide or show the phone number or any custom contact field on the ticket.
For Automatic registration after ticket purchase, you set the required fields directly on the ticket — the Registration form is not used.
For Registration with additional information, you can switch on the Option to buy a ticket without attendee details toggle. The buyer can then purchase a ticket without filling in the attendee's e-mail address. The ticket is generated later — either when the buyer adds the details, or when the attendee registers through the link they receive.
This is useful when a company buys tickets in advance and does not yet know who exactly will attend.
In the ticket settings, you can set:
Limit the maximum number of tickets — the total number of tickets that can be sold. Once sold out, the attendee sees Sold out in the purchase view.
Limit the sale period — the date and time from–to when the ticket is on sale.
Buy ticket in a bundle — the minimum order. With a step of 5, the buyer can purchase only 5, 10, 15 tickets, and so on. Useful for bulk partner purchases or discount bundles.
The Assign to group field — after the attendee registers (not after the order is paid), the attendee is automatically added to the selected group. You can use the group for targeted communication, content and engagement feature visibility, or push notifications in the attendee app.
Published — the ticket is publicly visible in the purchase overview.
Unlisted — the ticket is active but does not appear in the overview. It has its own direct link that you can share only with selected people (for example, partners).
Unpublished — the ticket is not visible or available for purchase anywhere.
A ticket cannot be deleted once it has been used. An unused ticket can be deleted.
In Ticket settings (at the event level, not on a specific ticket) you set:
Payment methods — card (including Apple Pay and Google Pay), bank transfer (with a proforma invoice), or both. With card-only, the attendee receives a tax document immediately.
Main price display — incl. VAT or excl. VAT.
Proforma invoice due date — 3, 7, 14, or 30 days from issue.
Reminder for upcoming due date — a system e-mail with a reminder.
The maximum due date is always at the latest two days before the event starts. If the chosen due date would fall later, it is automatically shortened. If less than two days remain before the event, the due date is set to the issue date of the invoice.
In the Discount codes section, click + New discount code. You set:
Discount type — percentage or value.
Discount amount.
Code validity — date from–to.
Maximum number of uses — if you leave it unlimited, the code applies without a cap.
Limit ticket validity — the code can apply to all tickets, or only to selected ones.
Assign group after using the code — the attendee who comes through with the code is automatically added to the group.
You can share codes with partners, selected attendees, or in marketing campaigns.
Individual registration link — a one-time link that grants free entry to one specific person. The attendee goes through the Registration form and pays nothing. Use cases: guest list, editorial invitations, VIP guests.
Bulk registration link — the same idea, but with a configurable maximum number of uses. One link for several people. Use case: partner invitations with a limit (a partner has 6 free invitations, gets one link, and shares it as they see fit).
For both link types, you can set assignment to a group after registration.
Ticket groups let you create a set of tickets visible only for a specific kind of purchase. You create a group, add selected tickets to it (including unpublished ones), and share the group through a unique link. Through that link, the attendee sees only the tickets in the group.
Use cases: partner pricing, special offers, VIP bundles with a custom set of tickets.
In the Ticket statistics section you see:
Sold, paid, unpaid, free, cancelled.
How many of the buyers are already registered (for Registration with additional information).
A monthly overview.
An Excel export by orders or by tickets.
Right after you turn on Tickets, create at least one. Until you do, registration does not work.
Automatic registration after ticket purchase does not use the Registration form or extended consents on a paid event. Choose Registration with additional information instead. See Choosing the right registration type for details.
The system automatically shortens the due date so that it falls at the latest two days before the event starts. Check in the settings how high the due date will actually be set for events that are close.
Unlisted tickets have their own direct link, which you find in the ticket detail. The ticket can be purchased through that link. It does not appear in the public purchase overview — that is intentional.
For a one-off free invitation, use an Individual registration link — the attendee goes through registration without the purchase flow. A 100% discount code makes sense for marketing campaigns where you want to track how many people redeemed the code.
A bundle setting enforces multiples — a step of 5 allows only 5, 10, 15, and so on. If you want a more flexible offer, create two tickets: a base Standard (without a bundle) and Standard — bundle of 5 (with a bundle and a discount).
