Ticket scanner
E-tickets
Tickets can be validated using a QR code scanner built into Campus Events or by manually entering the ticket number. In the event form, you can specify whether an e-ticket should be activated and whether re-entry is permitted. The event participant will then be sent a QR code (if they have successfully registered for the event) as a PDF attachment via email.
Please note: Activating the e-ticket retrospectively in the event form will not result in any QR code attachments being sent.
In addition, the ticket with the QR code in PDF format can be accessed in the user’s Campus Events profile (My Profile > My Events). This requires logging in with a user account.
Please note: This is not possible for guest bookings, as guests do not have an account. In this case, the ticket number must be taken from the participant overview.
Validating e-tickets
On this page, you select the scanner to be used for validating tickets. Once selected, the scan interface for the chosen event opens. Only events with e-tickets enabled are available for selection. Validating a ticket marks it as redeemed and prevents it from being used again.
The ‘Event’ drop-down menu lists the events for which e-tickets have been configured in the event form. The relevant event must be selected. The scanner view will then open. The scanner is initially switched off. Tap ‘Start’ to begin scanning and ‘Stop’ to end it. A camera is required for the QR code scanner. The scanner must capture the QR code via the camera in order to validate the ticket. The scanner has access (subject to browser permission) to the camera on your tablet, smartphone or laptop. The top bar displays an overview of tickets that have already been checked in, checked out and are still pending. You can also check this by entering the ticket number. From the ‘Tickets’ section, you can navigate to the event-specific participant list to search for ticket numbers if required. Below the scanner or the ticket number input field, you will see information regarding the scan or the ticket number entered (e.g. ‘Invalid’ or ‘Ticket not paid for’). The status of any ticket found is checked. If everything is in order, a dialogue box appears, allowing you to cancel the process or carry out a check-in. If a ticket does not meet the requirements – for example, because it has not yet been paid for – a check-in cannot be carried out and a corresponding status message is displayed.
Note: It can be configured at system-wide and client level whether unpaid tickets can be scanned. If the setting is set to “no”, the ticket cannot be validated without payment. If the setting is set to “yes”, the system first alerts the user that the ticket has not been paid for, but the user can still validate the ticket.