| Table of Contents | ||
|---|---|---|
|
June 25, 2024
Exact match search for Email in Spectators list
Searching the Spectators list is now configured to perform an 'EXACT Match' for 'Spectator email', thereby improving the accuracy and performances of the search.
Standardizing mobile logs about Spectator
A new naming convention has been applied to "Spectator" mobile logs action and message.
| Previous Action | NEW Action | NEW Message |
|
|---|---|---|---|
| user.authenticated | spectator.authenticated | Spectator authenticated | |
| user.signed-in | spectator.login | Spectator successfully logged in | |
| user.signed.out | spectator.logout | Spectator successfully logged out | |
| system.force-log-out | spectator.logout.forced | Spectator has been automatically logged out from the device (expired session or maximum number of session reached) | |
| user.password.reminder | spectator.password.reminder | Spectator requested password reset | |
| user.max-active-session.reached | spectator.devices.maximum.active.reached | Spectator reached the maximum number of active devices | |
| user.max-devices.reached | spectator.devices.maximum.allowed.reached | Spectator reached the maximum number of allowed devices | |
| spectator.screen.recording | spectator.screen.recording | Spectator recorded a video | |
| user.screenshot.taken | spectator.screen.screenshot | Spectator took a screenshot |
Collecting & categorizing Spectators origin
TIXNGO now collects and categorizes the origin of each spectator. The possible origins include:
- REGISTRATION: Spectator registered independently.
- TICKET_INJECTION or PRIVILEGE_INJECTION: Spectator was acquired through injection.
- TICKET_TRANSFER: Spectator was acquired through a ticket transfer.
Additionally, for spectators acquired through TICKET_TRANSFER, TIXNGO will also store the referring spectator's information.
Spectator origin and referral data are available in the Spectators export.
Changes to the Spectators List screen:
- The creation date field is now replaced by the first login date. The creation date is still available in the export file.
- The first login date will be null if the spectator has never logged into the ticket app.
- Once a spectator logs into the ticket app, the first login date will be recorded and remain unchanged regardless of subsequent operations such as logout, forced logout, or account locking.
May 14, 2024
Transaction Logs screen removal
In our ongoing efforts to tidy up the back-office, we've removed the transaction logs menu entry and screen, following the successful removal of the blockchain earlier this year.
April 23, 2024
New Spectators export using Downloads screen
It's now possible to benefit from the enhanced Downloads experience for Spectators export.
Spectators export contains the following fields:
| Code Block | ||
|---|---|---|
| ||
EMAIL, FIRST NAME, LAST NAME, GENDER, BIRTH DATE, BIRTH CITY, BIRTH COUNTRY, PASSPORT N., ID CARD N., NAT., ADDRESS LINE 1, ADDRESS LINE 2, ADDRESS LINE 3, ADDRESS ZIP, ADDRESS CITY, ADDRESS COUNTRY, PHONE, APP LANGUAGE, APP VERSION, CREATION DATE, ACQUIRED BY, REFERRED BY, FIRST LOGIN DATE, PROMO EMAIL, T.P.PROMO EMAIL, TRACKING, PIN CODE, ACTIVE SESSIONS, N.B DEVICES, EXTRA INFO 1, EXTRA INFO 2, EXTRA INFO 3, EXTRA INFO 4, LOCKED, STATUS, LAST UPDATED DATE |
Event Ticket Ownership report includes Spectator's address
Event Ticket Ownership report has been updated in order to contain spectator's address, and now returns the following fields:
| Code Block | ||
|---|---|---|
| ||
EVENT_NAME, EVENT_CODE, START_DATE, TAX_NUMBER, BARCODE, OWNER_EMAIL, FIRST_NAME, LAST_NAME, GENDER, PHONE, BIRTH_DATE, PASSPORT_ID, COUNTRY_OF_RESIDENCE, ADDRESS LINE 1, ADDRESS LINE 2, ADDRESS LINE 3, ADDRESS ZIP, ADDRESS CITY, ADDRESS COUNTRY, ALLOW_PROMO_EMAIL, ALLOW_PROMO_THIRD_PARTY_EMAIL, ALLOW_TRACKING, CHECK |
Mobile logs for beacon activations message update
Mobile logs for beacon activations now contains beacon name in the message:
| Log type | New message format |
|---|---|
| ticket.activation.bluetooth | Ticket <organizer_website@ticket_id> activated by bluetooth beacon <beacon_name> |
| ticket.secondary-activation.bluetooth | Ticket <organizer_website@ticket_id> checked by bluetooth beacon <beacon_name> |