Event attendance

Attendance tracking records who actually showed up at an event. Staff mark participants from the participants list, and customers can check themselves in from Thril if you allow it.

Attendance is part of the Events feature. Turn it on at venue level first, then per event.

---

⚙️ Turning on attendance tracking

Venue-level settings are under Settings > Events > Attendance tracking.

• Enable attendance tracking: each event gets an attendance setting, and staff can mark confirmed participants as present or absent. Existing events keep attendance tracking off until you turn it on for them.

Saved changes apply across the platform immediately.

Per event

When the venue setting is on, step 2 of the event form shows a Track attendance switch. Turn it on to get the attendance controls for that event.

---

✅ Marking attendance as staff

Open the event and go to the Participants tab. Events with Track attendance on have an Attendance column.

• Click the checkmark to Mark as present, or the cross to Mark as absent.
• Click the active mark again to clear it. The value goes back to Not marked.
• Only confirmed participants can be marked. Other statuses show a dash.
• Mark all as present marks every confirmed participant who has no mark yet. Marks you or the customer already made stay as they are.

A mark a customer made themselves carries a Self badge. Hover it to see the check-in time, and the distance from the event when the check-in was location-verified.

---

📱 Customer self check-in

Turn on Allow customers to mark their own attendance under Settings > Events > Attendance tracking.

Customers then see a Check in button on events they are confirmed for, and Undo check-in afterwards. Customers can only mark themselves as present, never as absent, and your staff can change any mark afterwards.

Check-in window

• Self check-in opens (minutes before start)
• Self check-in closes (minutes after end)

Both are set to 30 minutes when you first allow customer marking, and both accept up to 24 hours. Leave a field empty for no limit on that side.

When check-in is refused

A customer cannot check in when:

• the event is cancelled, or not published yet
• attendance tracking is off for the venue or for the event
• customer marking is off
• they are not a confirmed participant of the event
• the current time is outside the check-in window
• staff already marked their attendance

A customer can only undo a mark they made themselves.

---

📍 Location-verified check-in

Maximum distance from the venue requires the customer to be at the event before their check-in counts. Choose No distance specified (No GPS required), 300, 600 or 1000 meters.

The field needs the venue's address coordinates. Set them on the venue's address first, otherwise the field stays disabled.

The distance is measured against the event's own map coordinates. If the event has none, the linked external venue is used, and otherwise the venue's own address.

When a distance is set, Check in opens a Check in with your location step that names the place the customer must be at. The device location is read once and is not tracked.

The check-in is refused when:

• the customer denies the location permission, or the device produces no position
• the position is too imprecise to answer the question — a fix must be at least as accurate as the chosen radius, and never coarser than 500 metres
• the customer is further from the event than the chosen radius

Each of these tells the customer that venue staff can check them in instead. Checking in works best in the Thril app on a phone, because a desktop browser derives its position from the network and is often accurate only to kilometres.

The verified distance is stored with the mark and shown in the Self badge tooltip.

---

👥 Confirming participation for a customer

Open the event, go to the Participants tab, open the actions menu on the participant's row and choose Confirm participation.

This works on an event that is not published yet, and on a venue that requires payment to confirm participation. In the second case staff collect the payment themselves, onsite or later, or the customer pays in the app once the event is confirmed and the payment falls due.

Confirming a participant on an event that is not published yet sends them no confirmation message. Publishing the event sends its own notification. On a published event, confirming a participant emails them as usual.

Cancelled events, events that have already started, the participant limits and the queue setting apply to staff exactly as they apply to a customer.