Data is stored in Azure Data Lakes in Parquet files.

...

Tickets

Information related to tickets is stored in queue-positions-{env}-*.parquet files. The data includes, among others, customer information, bookings details, creation dates as well as identifiers that allow correlating the information with ticket events and queues.

...

binary id (STRING) - ticket identifier
binary notificationType (STRING) - type of notification, possible values: applePass, webPush, email, phoneNumber, depending on customer choice
binary notificationStatus (STRING) - extra status related to notification, can be null
binary to (STRING) - customer phone number, can be null
binary from (STRING) - not relevant / not used
binary recipient (STRING) - customer email, can be null
int96 start - present on tickets that are bookings, timeslot start datetime
int96 end - present on tickets that bookings, timeslot end datetime
binary virtualAppointmentisEnabled (boolean) - presents if it’s an online booking or not
binary type (STRING) - ticket type, possible values: anonymous (walk-in ticket), booking (pre-booking), manual (tickets issued by staff)
binary status (STRING) - ticket status, possible values: draft (pre-booking created but not active), pending (ticket is inside queue), notified (ticket called out by staff), fulfilled (ticket checked in by the staff), completed (ticket has been served), rejected (ticket was cancelled either by customer or staff)
binary label (STRING) - assigned ticket number (A1, B2 and such)
binary queue (STRING) - queue identifier, can be used to correlate data
int96 createdAt - ticket creation datetime
int96 fulfilledAt - customer checked-in datetime
int32 retryCount - customer call out retry by staff count
binary locale (STRING) - used lanugage
int32 numberOfPeople - number of people for ticket
binary organization (STRING) - organization name, internal identifier (not presented to customers)
binary registrationPhoneValue (string) - phone number used during registration
binary servedById (string) - id of staff person who served the ticket
binary servedByEmail (string) - email of staff person who served the ticket
int32 feedbackRating - rating value
binary feedbackMessage (string) - message attached to rating
binary organizationTitle (STRING) - organization name. Could be null
binary locationName (STRING) - queue name. Could be null
binary extraStatus (STRING) - extra status for the ticket, for more details please check Position model . rejectedByCustomer might be used for understanding if ticket was rejected by customer or not. Could be null

Queues

Information related to queues (which reflect physical locations like departments in stores) is stored in queues-{env}-*.parquet files.

...

Occupancy over time data is stored in occupancy-*.parquet files. Each event contains timestamp and occupancy value for the queue / location.

Data schema

binary environment (STRING) - not relevant/not used
binary organization (STRING) - name of organization this event belongs to
binary session (STRING) - ticket identifier for position-related events, guid for other eventsnot relevant/not used
binary app (STRING) - not relevant/not used
binary queueId (STRING) - queue identifier
int32 count - occupancy count at the time of event
binary type (STRING) - constant , value is positions_inside(positions_inside_store)
int96 date - event date
binary id (STRING) - internal event id, not relevant/not used
int64 timestamp - event timestamp

Enter/exit events

These events are related to occupancy in physical location and reflect people going in and out at the location. Data is stored in exit-*.parquet and enter-*.parquet files.

Data schema:

binary environment (STRING) - not relevant/not used
binary organization (STRING) - name of organization this event belongs to
binary session (STRING) - not relevant/not used
binary app (STRING) - not relevant/not used
binary queueId (STRING) - queue identifier
int32 count - people going in/out count (depending on event type)
binary isManual (STRING) - indicates whether this occupancy change has been triggered manually by the staff using +/- buttons in staff UI
binary type (STRING) - position_exited_store or position_entered_store
int96 date - event date
binary id (STRING) - internal event id, not relevant/not used
int64 timestamp - event timestamp