Skip to main content
Skip table of contents

Ticket Setup

Pop-up Header and Button Differences

Depending on the action taken, the pop-up header and button labels will vary:

  • Edit Ticket: Header shows Edit Ticket, and the bottom button is labeled Save.

  • New Ticket: Header displays New Ticket, and the bottom button is labeled Create Ticket.

  • Clone Ticket: Header displays Clone Ticket, and the button is labeled Save.

When cloning an event, the ticket will automatically be named in the format Copy of [original ticket name]. If an already copied ticket is cloned again, the format becomes Copy of Copy of [original ticket name].

Note: The pop-up’s height is capped at 90% of the screen, with a responsive layout for mobile devices to ensure all elements align well.

Ticket Details and Requirements

Ticket Name

  • Required Field: Yes

  • Character Limit: 50 characters maximum

  • UI Features: Character counter displayed at the bottom right corner of the field.

Description

  • Required Field: No

  • Character Limit: 400 characters maximum

  • UI Features: Character counter at the bottom right corner of the field.

  • Tooltip: “This info appears on the ticket to give customers more details about what’s included.”

Category

Selection Options:

  • Available for All: Default setting that makes tickets accessible to all participant categories.

  • Specific Category: Allows the ticket to be designated for one specific category only.

  • Behavior on Category Deletion: If a specific category assigned to a ticket is deleted, this ticket’s label is switched to Available for all and therefore this ticket is visible for all users.

  • Integration with Registration Form: If the Category field is not added to the registration form, the category selector in the ticket creation module is disabled. There is a tooltip for such a case: Category was not added to the Registration form. Ticket allowed for all categories.

Location

  • Admins can set up multiple check-in zones (e.g., Halls or Conference Rooms). The All locations option is available by default, but it cannot be selected alongside specific check-in zones.

  • Ticket holders are required to proceed to the specific event check-in zone indicated on their tickets.

  • If there is only hall as the check-in zone, for example Hall I check-in zone, it will be written as Hall 1. If only one stand is the check-in zone, the format will be is Hall 1; Check-in stand.

Ticket Quantity

Admins can select from:

  1. Unlimited Number of Tickets: Allows an unlimited ticket count.

  2. Limited Number of Tickets: Allows setting a specific ticket limit, though 0 cannot be set as a valid number.

Validity

The Validity section allows admins to set ticket usage dates.

  1. Specific Dates:

  • Selection Type: Multi-select enabled for selecting either consecutive or non-consecutive dates.

  • Requirement: This field is mandatory for Specific Dates. If no dates are selected, the message “This field is required” will appear.

  • Time Zone Adherence: Tickets follow the event’s time zone settings. Any updates to the event’s time zone apply to both existing and new tickets. For example, if the event’s time zone in the admin panel is set to New York and the ticket allows entry only on January 1st, this date should correspond exclusively to the New York time zone.

  1. Non-specific Dates:

  • Allows the ticket holder flexibility in choosing attendance days. If the ticket is set to allow attendance on a limited number of days (e.g., 2 days within a 4-day event), once the days are used, the ticket expires.

  • The admin can adjust the number of days using up and down arrows or by directly typing the number into the field.

  • Admin can’t set a number lower than 1 or higher than the maximum days of the event. Clicking on arrow up-down doesn’t let him doing that and clicking will be without any response.

  • If a number greater than the event duration is entered, it automatically adjusts to the maximum allowable days. This means if the admin types a number bigger than 5 directly, it automatically changes to 5.

Note: The Specific Dates picker resembles a calendar. Only event dates are selectable; others are disabled.

Header Background

If the image is already uploaded and the admin decides to switch back to gradient, the image doesn’t disappear but remains in the respective field so the admin will be able to quickly switch back to it if needed.

Gradient Background

  • By default, the ticket header background is a linear gradient based on the organization’s brand colors (Brand 1 and Brand 2).

  • Gradient angles vary randomly for each ticket.

Custom Image Background

  • Admins can upload an image as the ticket header background.

  • A cropper allows admins to adjust the image to fit the required aspect ratio of 2.6, with a recommended size of 434x167px.

  • The image scales proportionally when resizing the ticket.

  • If an image is uploaded and the admin later switches back to a gradient, the uploaded image remains accessible for future use.

Upon making any changes to the gradient, there is a reset button in order to revert to the previous gradient settings.

There is a preview that shows how the ticket will look with the gradient that has been set up or with the uploaded picture. All elements of the preview are static, except for the header background.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.