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. You create and edit an individual ticket in a side panel with three tabs — Details, Attendee details, and Ticket settings.
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 and invoice items, VAT rates (added by customer support), 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.
You add a new ticket on the Tickets tab with the + New ticket button, and you open an existing one with the edit icon in its row. A side panel opens with three tabs — Details, Attendee details, and Ticket settings. The Ticket name field sits above the tabs and is required — it is the name the attendee sees (for example, Standard, VIP, Early Bird). Save your changes with Save.
On the Details tab, you set the ticket's price and how it looks:
Different ticket name on invoice — by default, the invoice uses the ticket name. When you switch this on, an Invoice item field appears for a different name on the tax document (useful when accounting needs a different label than the marketing name).
VAT — the tax rate. If the VAT rate you need is missing, customer support adds it (contact them). The VAT calculator button helps you convert between the price with and without tax.
Price excl. VAT — the amount without tax, in the event's currency (the field carries the currency, for example Price excl. VAT CZK).
Ticket description — an optional text the attendee sees with the ticket in the purchase view.
The last choice on the Details tab sets the ticket's visibility:
Published — the ticket is publicly displayed in the ticket overview and is available for purchase.
Private — the ticket is not shown in the overview but is available for purchase via a separate link or in a ticket group. Useful for partner or VIP tickets you do not want to show everyone.
Unpublished — the ticket is not visible anywhere on the platform and is not available for purchase.
A ticket cannot be deleted once it has been used. An unused ticket can be deleted.
On the Attendee details tab, you decide which contact fields the attendee fills in and which are required. The fields First name, Last name, Company, Job title, and Phone number offer Required, Optional, and Hide; E-mail is always required. Below them are Custom contact fields with the same options — these are created and managed in Workspace settings; here you only decide whether to use them on this ticket.
How the fields behave depends on the registration type after purchase (see Turning on Tickets):
Registration with additional information — after payment, the attendee goes through the Registration form, so the required fields are governed by the contact-details settings in the Registration form. Fields the form marks as required are locked to Required here (kept in sync with the form); for the other fields you set Required, Optional, or Hide as this ticket needs.
Automatic registration after ticket purchase — the Registration form is not used and the ticket arrives right after purchase. You therefore set which fields are required directly on the ticket, and the buyer fills them in during purchase.
On the Ticket settings tab inside the ticket panel, you turn on optional sales rules. Each is a toggle (Active / Inactive); switching it on reveals its field:
Option to buy a ticket without providing attendee details — the buyer can 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. Useful when a company buys tickets in advance and does not yet know who will attend.
Limit the maximum number of tickets — sets the total number of tickets available for purchase. Once sold out, the attendee sees a Sold out message in the purchase view.
Limit sales period — start and end dates that define when the ticket is on sale.
Purchase in a bundle — a minimum order in multiples. 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.
Assign to group — after the attendee registers (not after the order is paid), the attendee is automatically added to the selected group. Use the group for targeted communication, content and engagement feature visibility, or push notifications in the attendee app.
On the event-level Ticket settings tab — which applies to the whole event, not a single ticket — you configure payments:
Payment options — Card payment and bank transfer, Card payment only, or Only by bank transfer. With card payment (including Apple Pay and Google Pay), the buyer receives a tax document immediately; with bank transfer, the system issues a proforma invoice and the tax document follows once it is paid.
Price display — the Show main price with VAT toggle controls whether the main price shown with the ticket and in the order summary on the microsite includes VAT.
Setting up bank transfer payments (pro-forma invoices) — the Advance invoice due date (for example, 7 days from issue) and the Send reminder for unpaid proforma invoice toggle (a system e-mail reminding the buyer of the upcoming due date).
Tracking codes — for GTM tracking codes, contact customer support.
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.
On the Import tab, you bulk-upload data through an Excel template. Import is available for E-mail links (individual registration links), Bulk links, and Discount codes. For each type, you download the template (Download template), fill it in, upload it (Upload completed template), and run Import. After importing, you see a Created / Skipped / Errors summary with a per-row description of any errors.
The templates reference groups by name. If a row points to a group that does not exist in the workspace, that row is not imported and fails. Create the groups before you import.
On the Ticket statistics tab, you see sales per ticket and overall. Columns: Sold, Paid, Unpaid, Free, Cancelled, and Registered (how many buyers have already completed registration for Registration with additional information), most of them broken down into Quantity / Amount. Below the table is a Monthly overview. Export the data with the Exports button — to Excel 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 what the due date will actually be set to for events that are close.
A private ticket is intentionally hidden from the purchase overview. You get its direct link from the link icon in its row in the ticket list; through that link — or by adding it to a ticket group — the ticket can be purchased.
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).
Import templates (E-mail links, Bulk links, Discount codes) reference groups by name. If a group does not exist, the row is not imported and fails (for example, Unknown group: VIP). Create the groups before importing and match the names in the template.
