Event Access Control
<< Features available when configuring codeREADr as your ticket scanning app. >>
One of the most popular use cases is event access control: validating & tracking tickets at venues and events. Today, hundreds of ticketing companies and event technology providers use codeREADr.
Best Practices for Event Access Control services
We have a document that outlines best practices to set up services for event access control. Moreover, you can see the workflow and features of the app through our video below.
<< Please use these step-by-step instructions to create your event access control services.>>
First, you can use our standard camera scan engine, SD PRO (video) upgrade, or a scanning accessory.
Validate tickets online or offline
First, scanning from different devices at multiple entrances requires connectivity to an online database. This is to catch duplicate scans. However, internet isn’t always stable. Thus, we offer both an online to offline fallback option and primary services in the offline validation mode. For example, you can use validation and sync to an ‘on-device’ database.
With an on-device database, you can instantly validate scans against a database on iOS or Android devices. This is because there is no connection latency. Also, the system auto-uploads the scans from all devices to a shared online database. Likewise, it will download the synced database to each device. The default setting for posting scans is every two (2) seconds. Also, the default setting for downloading databases is every two (2) minutes.
Here, the system completes both processes in the background. Thus, the users can keep scanning without interruption. Also, if there is no connectivity, the scans will queue and sync when it’s back.
Use our servers or yours
You can upload your ticket IDs to our servers via the Web UI or APIs. Also, you can use your own servers for validation (Direct Scan to URL or PostbackURL).
Validate ticket & photo for entry/re-entry
First, with photo postback, your users scan a patron’s ticket with an iOS or Android device. Then, they take their photos. Secondly, codeREADr will link the ticket ID and photo and store those in your Dropbox. Thirdly, when the attendant scans the ticket again, codeREADr validates it. Then, codeREADr displays the stored photo for visual verification.
Step-by-step instructions on how to set up photo viewing for entry or re-entry verification can be found here.
RFID/NFC wristbands and tags
For instance, you can use NFC-enabled Android devices to tap RFID/NFC wristbands and tags for issuing, tracking & validating. Also, use a USB-to-microUSB adapter to connect a discrete RFID/NFC reading pad to Android devices. Moreover, you can see below for a video of both in action with the codeREADr app. Issuing Wristbands- Instructions.
Extended Validation Options
To Valid, Invalid and Invalid Duplicate, we added secondary conditional validations in real time. For example, we can set min/max scan counts based on duration, start/end periods and day ranges. Examples include:
- First, tickets are good only on certain days of the week, repeating each week.
- Second, tickets are good only on certain dates or at certain times.
- Third, one ticket is good for defined number of scans, whether for entry, merchandise, transportation or other value.
No barcodes? No problem!
Scanning a barcode is fast. But, it’s certainly not the only way to use codeREADr. For example, many clients use RFID/NFC to capture ticket IDs or the Manual Entry or Lookup options. The Lookup option works by allowing the app-user to search for the attendee by name or other identifiers.
No ticket database? No need!
You can use ‘Pattern Validation’ with an empty database or a partial database. For instance, not all ticket IDs are in the database because of last-minute sales. Simply, create a database name and start scanning. Then, codeREADr will add each scan to the blank or partial database AFTER checking if it’s in the database. You can not only check the validity of a ticket, but also, catch duplicate tickets. SIMPLE for your event access control.
Exit & Re-Entry Validation with Adjusted Count of Checked-In Attendees
For instance, when an app user scans a ticket with a Check-In service, the database status changes from “1” (valid) to “0” (invalid). Then, when scanned with a Check-Out service, the database status changes from “0” (invalid) back to “1” (valid). Therefore, this toggling allows for multiple exits and re-entries.
A count is provided of the number of people checked-in at the event. Also, this count will subtract checked-out scans from checked-in scans to give a total. This is valuable for capacity monitoring. However, note that if attendees leave without completing check-out, the total will not be accurate.
For instructions, please read this Ticket exit and re-entry validation PDF.
Note: This is an advanced feature that requires a 25-Device Plan. If that’s not an option for you, please use our standard Database Builder service type.