<aside>

A physical tag is a scannable ID (e.g. barcode, QR code, or NFC chip) that can be assigned to a visitor's profile for use at check-in or for identification purposes. They are often referred to as Membership Cards, keychain tag

<aside>

ATTENTION

1. When merging two profiles, BETA cannot determine which physical tag to keep. After merging, be sure to review and update the external ID to ensure the correct tag is associated with the profile.
2. We do not recommend using the BETA app as Kiosk mode, to scan physical tags with BARCODES (rather than QR CODES) for check-in - and definitely not the BETA app in browser mode. Most phone/tablet cameras struggle to reliably read 1D barcodes (single-line barcodes), which can lead to delays or errors. For best results, use the dashboard with a dedicated barcode scanner, especially when working with physical tags. See here how to Visitor QR code check in via Dashboard </aside>

<aside>

BETA recommends using the in-app QR codes instead—they’re more secure by using dynamic & expiring codes, and are more environmentally friendly by using no plastic.

</aside>

Note: These tags are tied directly to the visitor’s profile, not to a specific pass or entry product.

</aside>

<aside> Checking in climbers through their QR codes can be done in two ways in BETA. The first is through the dashboard, and secondly through using the app.

Looking to check in climbers from

• the BETAapp, see the following page: Visitor QR code check in via Kiosk Mode (App)
• the Dashboard, see the following page Visitor QR code check in via Dashboard </aside>

<aside> Be sure that the device has sound enabled as distinct sounds indicate check-in success or failure for climbers.

• Listen to check-in success and failure </aside>

<aside> <img src="/icons/arrow-northeast_blue.svg" alt="/icons/arrow-northeast_blue.svg" width="40px" /> Looking to Allow or Restricting QR Code Generation

Allow unverified auto check-in

</aside>

<aside> <img src="/icons/arrow-northeast_blue.svg" alt="/icons/arrow-northeast_blue.svg" width="40px" /> Looking to enable Static Code Entry

Enable/Disable Static Codes: Apple & Google wallet entry

</aside>

FAQs

• Can a visitor have more than one physical tag?
• Physical tags are not being scanned with the mobile phone app
• What are physical tags used for?
• Can I reuse a tag for another visitor?
• Does the physical tag automatically expire?
• Can I scan physical tags using any barcode scanner?
• Is the tag linked to a pass or just the profile?

⤷ Setup & Requirements

› Why BETA Recommends using the BETA App for check-in

<aside>

While physical tags are supported, they can be lost, traded, or shared, which may compromise check-in accuracy and security.

The BETA App generates a dynamic, expiring QR code tied to the visitor's active pass or entry. These codes cannot be reused or shared, making them a more secure and reliable option.

› Understand the BETA inbuilt Dynamic QR Code System

</aside>

› Settings: Enable Static Code Entry

<aside>

If you're using third-party tools like Apple Wallet or Google Wallet or Physical Visitor Tags, you may choose to enable static QR code entry.

These codes do not change or expire and function similarly to physical tags. They must still meet the character and uniqueness requirements mentioned above.

</aside>

› Requirements for Physical Tags

<aside>

BETA does not supply physical tags. You must source and manage them yourself.

Code Requirements:

• BETA highly recommends using a QR code over a single-line 1D barcode. Why? QR codes are considered easier to scan compared to 1D barcodes, as they can be scanned in any direction, whereas 1D barcodes have to be scanned from the proper angle, and can be hard for phone cameras to easily pick up.
• Must be unique to each visitor
• Between 6–36 characters
• No Special characters - only letters, number, _ underscores and - *(dash) *****are accepted
• Formats can include 1D barcodes, QR codes, NFC, etc. </aside>

⤷ Assigning External IDs to profiles

› Assign an External ID to a Profile