Overview

Open

🔍Simple search bar

At the top of the screen, you can search for a spectator using their email address. The search uses an exact match—partial entries will not return results.

You can either:

• Type the email manually, or

• Scan the QR code available in the "Support Spectator" section of the mobile app, using a hand-held scanner (strongly recommended for speed and accuracy).

This ensures quick and precise access to spectator profiles during live operations.

👤 Spectator Header

At the top of the screen, you'll find a quick-access identity panel displaying key information about the spec

• Email address and full name

• Gender and birth date

• Nationality and country of residence

• Passport number (if collected)

• ID number, phone number (if collected)

• PIN code (visible only for the PINCODE authentication method AND when the PIN was requested)

• App language (used in the app interface)

This summary provides immediate context for support teams when handling identity-related requests or ticket ownership concerns.

📋Tabbed Navigation

Tired of endless V3 vertical scrolling? We’ve introduced tabbed navigation to bring clarity and focus—starting with what matters most.

From this navigation bar, you’ll be able to target different aspects of the ticket via four tabs:

• Tickets: Displays all tickets associated with the spectator, grouped and filterable by status.

  • Now in wallet

  • Pending transfers

  • Valid

  • Deleted

• Past transfers: show all the tickets has been transferred success in both incoming and outgoing of a spectator

• Communication Logs: Logs related to the Communications sent to the spectator (Emails, Push Campaigns)

• Mobiles Logs : Logs from the mobile app related to this spectator (e.g., app launch, download, logout, …).

• Devices : Displays the list of devices used by the spectator to interact with the mobile wallet. This information is useful for debugging technical issues (e.g. repeated logouts, downloads) and for fraud detection (e.g. ticket accessed from multiple devices). Previously, this information was only accessible from the Spectators list screen in the back-office.

• Other Information: This section centralizes additional spectator-level data, including:

  • Status with milestone dates (e.g., registration, last activity)

  • Opt-in preferences (e.g., for campaigns or communications)

  • Legacy "Other Information" fields, migrated from previous spectator management screens

• It provides a more complete profile for back-office teams when handling edge cases or performing advanced user validation.

Walkthrough the Tabs

‘Tickets’ tab

Open

Displays all tickets associated with the spectator, grouped and filterable by status.

• All: Displays all the tickets owned by the spectator, regardless of their status

• Now in wallet : Displays all tickets currently marked as DOWNLOADED on any of the spectator’s devices. These are tickets that are active and available for use in the spectator’s mobile wallet.

• Pending transfers : Displays all tickets that are in transit—either being sent from or received into the spectator’s wallet.

  • This view also includes a Spectator email filter, allowing organizers to search by sender or recipient email address.

  • Open

    

    Filter in the “Pending transfer” status

     

• Valid : Displays all tickets currently owned by the spectator that are considered valid for entry.
  This includes all statuses except DELETED, meaning the tickets are eligible to be used at the venue.

• Deleted: Displays all tickets currently owned by the spectator that have been deleted, and are therefore no longer valid for entry.

‘Past transfers’ tab

Open

Past transfer tab overview

A new list that shows all the tickets has been transferred success in both incoming and outgoing of a spectator with this following information:

• Ticket number

• Barcode

• Event

• Sender

• Recipient

• Transfer date

This view provides several filters to help organizers efficiently review spectators with a large number of tickets:

• Event filter – Narrow results by specific events.

• Contingent filter – Filter tickets by their assigned contingent.

• Sender/Recipient email filter – Search by the sender or recipient’s email address.

Open

Filter

‘Communications’ tab

Logs related to the Communications sent to the spectator (Emails, Push Campaigns)

Open

Each log entry includes the following information:

• Type – Type of the communication (e.g., Email or Push Notification or Campaign)

• Template – Displays the name of the template used for the communication.

• Language – Language of the communication

• Delivery Date – Exact date and time when the communication was sent.

• Delivery Status – Shows the current status of the communication, like Delivered, or Failed.

• Actions – View, Resend

‘Mobile logs’ tab

The Mobile Logs tab provides a detailed, chronological view of the spectator’s activity within the mobile app.

Open

Each log entry includes the following information:

• Action – Type of interaction (e.g., spectator.login, spectator.logout, spectator.screen.screenshot)

• Message – Human-readable description of the action

• Log Level – Currently INFO level logs

• Platform – OS type (Android or iOS)

• OS Version – Mobile OS version at the time of the action

• App Version – App build used by the spectator

• Device Model – Device on which the action occurred

• System Date – Server-side timestamp

• Mobile Date – Device-side timestamp

This data helps contextualize support requests and detect patterns such as repeated logins, app errors, or unusual behavior (e.g., excessive screenshots).

‘Devices’ tab

Open

The Devices tab provides a list of all devices that have been used by the spectator to access the TIXNGO mobile app.

Each entry includes the foll

• Device Name – Reported name of the device (e.g., google pixel 8)

• App Version – Version of the TIXNGO app installed on the device

• Platform – Mobile operating system (e.g., Android, iOS)

• Actions - Reset or remove device

• Device ID – Unique device identifier (used internally for linking actions and tickets)

• Last Synced Time – Timestamp of the last successful sync between the app and the server

This tab replaces legacy device access information, previously only available from the Spectators List.

‘Other information’ tab

The Other Information tab consolidates key metadata about the spectator.
As of now, it includes the following sections:

• Status milestones

• Opt-in preferences

• Extra info fields

In upcoming releases—particularly with the V4-ization of the spectator model—this tab will be further enriched to support deeper insights and operational use cases.

Open

Status

Tracks spectator activity milestones, including:

• Creation Date – When the spectator profile was created

• Status – (Reserved for future use)

• First Login Date – Timestamp of the spectator’s first login to the app

• Last Active Time – Timestamp of the most recent activity

Opt-ins

Displays the spectator’s privacy and marketing preferences:

• Promo Email – Consent to receive promotional content

• Third Party Promo Email – Consent to receive third-party promotional content

• Tracking – Consent for usage tracking and analytics

These values are key for GDPR compliance and campaign eligibility.

Extra Info

Legacy V3 custom fields used for additional spectator-level metadata.