...
The purpose of the Tickets page is to monitor every tickets that has been injected in the TIXnGO TIXNGO system in real-time. This view displays the Ticket ID, it's taxation number, barcode, current owner name / email, initial owner name / email and status, as well as the related event's name, start time and file ID and it can be exported to an excel sheet, using the excel button.
One can search for a specific ticket(s) using the search field at the top of the page (black rectangle in the screenshot example).
Clicking on a Ticket ID will redirect you to the Support → Ticket screen, showing much more information about one particular ticket (see Support section).
Clicking on the Event name will redirect you to the Event page for that specific Event.
Clicking on the Owner email will redirect you to the Support → Spectator screen, showing information about that specific spectator (see Support section).
The Action column is used to display information about the ticket such as Transfer rules, Main and Extra data (Ticket button) and allows Main and Extra data edition (Pencil button). Organizers can also delete ticket, deleted reason and deleted ticket visibility are required (Wastebasket button).
Clicking on Export Ticket Details to export ticket details data.
...
- INJECTED
Organizer: Ticket can be seen in the AdminTool as it was injected in TIXnGO TIXNGO system.
Spectator: Does not have Ticket in his wallet yet, - DOWNLOADED
Organizer: Ticket can be seen in the AdminTool as DOWNLOADED.
Spectator: Sees Ticket in his wallet yet. - ACTIVATE
Organizer: Ticket can be seen in the AdminTool as ACTIVATED.
Spectator: Sees Ticket in his wallet and sees the QR code. - ONLINE ACTIVATE
Organizer: Ticket can be seen in the AdminTool as ONLINE ACTIVATED.
Spectator: Sees Ticket in his wallet and sees the QR code. - OFFLINE ACTIVATE
Organizer: Ticket can be seen in the AdminTool as OFFLINE ACTIVATED.
Spectator: Sees Ticket in his wallet and sees the QR code. - MANUAL ACTIVATE
Organizer: Ticket can be seen in the AdminTool as MANUAL ACTIVATED.
Spectator: Sees Ticket in his wallet and sees the QR code. - BLUETOOTH ACTIVATE
Organizer: Ticket can be seen in the AdminTool as Bluetooth ACTIVATED.
Spectator: Sees Ticket in his wallet and sees the QR code. - DEACTIVATED
Organizer: Ticket can be seen in the AdminTool as DEACTIVATED.
Spectator: Sees Ticket in his wallet and do not the QR code. - ASSIGNED
Organizer: Ticket can be seen in the AdminTool as ASSIGNED.
Spectator: Sees Ticket in his wallet and sees the assigned name on the ticket. - PENDING
Organizer: Ticket can be seen in the AdminTool as PENDING.
Spectator: Transferrer sees Ticket in his wallet in the transfer screen. Transferre still does not see the ticket in his wallet
...
For the complete list of injection variable, please take a look at the official documentation: https://developer.TIXnGOtixngo.io/pdf/TIXnGOTIXNGO-Injection-Doc.pdf
WARNING: All Dates must follow the RFC3339 standard for date & time.
| Variable Name | Variable Type | Value length | Variable usage/description |
| Gender | string | 1 char | M (male), F (female), U (unknown), X (other) |
| First Name | string | 50 char | Spectator's first name |
| Last Name | string | 100 char | Spectator's last name |
| string | 256 char | Spectator's email address | |
| Main Applicant | string | Boolean | Indicates if the spectator is the main applicant (SecuTix) for this ticket (default false). |
| Ticket ID | string | 256 char | Ticket ID in the TIXnGO TIXNGO system (a-z|A-Z / numbers / spaces / some special characters: *.-_+/()) |
| Barcode | string | 512 char | Plain text ticket barcode |
| Sorting Key | string | 256 char | Key used to order the tickets for the spectator following the alphabetical order. |
| Price | number | float | Price of the ticket |
| Currency | string | 20 char | Currency of the ticket's price |
| Category | string | 512 char | Purchase category (e.g. ADULT, CHILD, VIP, etc...) |
| Tax. Number | string | 256 char | Purchase taxation number |
| Ticket Image URL | string | 256 char | Display image as per URL on following ticket views: Ticket View, Ticket Detailed View |
| File ID | string | 256 char | SecuTix File ID (or any file ID that would list groups of ticket, e.g. injection file) |
| Event ID | string | 256 char | Event ID in the TIXnGO TIXNGO system |
| Event Name | string | 128 char | Name of the match |
| Site | string | 200 char | Site name displayed at the Ticket View and Ticket Detailed View under Address title |
| City | city | 200 char | City where the event takes place |
| Country Code | string | 200 char | country code for the address |
| Zip | string | 200 char | zip code for the address |
| Event Image URL | string | 256 char | Display image as per URL on following ticket views: My Tickets - "Group Image" |
| Start Time | string | must follow RFC 3339 date format | Displays Match date and kick-off time at the Ticket View and Ticket Detailed View |
| Ribbon Display Time | string | must follow RFC 3339 date format | Time at which a ribbon is displayed on the mobile app to notify spectator turn on Bluetooth |
| Transfer Group Id | string | 256 char | Transfer rules can technically be different for every ticket. Organizer might want to chose to have different transfer rules for different types of ticket (ex: Adult, child, VIP, etc…). This GroupID is the Transfer rules group ID representing a group of transfer rules applied to certain tickets. If Organizers want to apply the same rules to every tickets, by default this groupID is set to the EventID and every ticket will be in this group. |
| Max number of Ticket per receiver's Phone | integer | integer | Maximum amount of tickets per phone for this Transfer rules group id |
| Max Resell Price increase (in %) | integer | smallint | Maximum profit (price increase in %) of the original ticket price for a resell between spectator. |
| Max number transfer per Phone | integer | integer | Total amount of transfers per Phone (-1 feature is disabled). Counter is increased for every new transfer, but decrease on a Return. |
| Max number transfer per Ticket | integer | integer | Total amount of transfers per Ticket (-1 feature is disabled). Counter is increased for every new transfer, but decrease on a Return. |
| Assign Limit | integer | integer | Upper bound amount of transfer before the Assign function is disable (-1 means unlimited) |
| Allow Transfer | Boolean | Boolean | Enables or Disables transfer functionality for given match (Send menu item in the ticket view hidden or displayed) |
| Allow Transfer after Activation | Boolean | Boolean | Enables or Disables transfer functionality for given match for Activated Tickets (Send menu item in the ticket view hidden or displayed) |
| Allow Transfer after Control | Boolean | Boolean | Enables or Disables transfer functionality for given match for Controlled Tickets (Send menu item in the ticket view hidden or displayed) |
| Allow Return To Organizer | Boolean | Boolean | Enables or Disable allow everyone to release ticket to resale. |
| Allow Return To Organizer For Initial Spectator | Boolean | Boolean | Enables or Disable only Initial Spectator can release ticket to resale. |
| Resale Group Id | string | 256 char | Resale rules can technically be different for every ticket. Organizer might want to chose to have different resale rules for different types of ticket (ex: Adult, child, VIP, etc…). This GroupID is the Resale rules group ID representing a group of resale rules applied to certain tickets. If Organizers want to apply the same rules to every tickets, by default this groupID is set to the EventID and every ticket will be in this group. It is editable or used only if organizer resale setting is enabled |
| Allow Resell | Boolean | Boolean | Enables or Disables resale functionality for given match for all Tickets (Send menu item in the ticket view hidden or displayed) It is editable or used only if organizer resale setting is enabled |
| Allow Resell after Activation | Boolean | Boolean | Enables or Disables resale functionality for given match for ActivatedTickets (Send menu item in the ticket view hidden or displayed) It is editable or used only if organizer resale setting is enabled |
| Keep one Ticket Overall | Boolean | Boolean | Force ALL ticket wallet holders to keep at least 1 ticket per given Match |
| Keep one Ticket at Injection | Boolean | Boolean | Force ticket wallet holder to whom tickets were originally injected to keep at least 1 ticket per given Match. E.g. all his transfer guests will be able to forward all the tickets they received |
| string | 100 char | Support organizer define the resale price with three options A, B and C per Transfer Group Id:
It is editable or used only if organizer resale setting is enabled | |
| Min resale price decrease | number | float | Enable when Resale option A is selected. Min resale price decrease (in % of the initial price) of the ticket to be resold It is editable or used only if organizer resale setting is enabled |
| Min resale price amount | number | float | Enable when Resale option A is selected. Min resale price amount of the ticket to be resold It is editable or used only if organizer resale setting is enabled |
| Max resale price increase | number | float | Enable when Resale option A is selected. Max resale price Increase (in % of the initial price) of the ticket to be resold It is editable or used only if organizer resale setting is enabled |
| Max resale price amount | number | float | Enable when Resale option A is selected. Max resale price amount of the ticket to be resold |
| Specific resale price decrease/increase | number | float | Enable when Resale option B is selected. Specific resale price decrease/increase (in % of the initial price) of the ticket to be resold
It is editable or used only if organizer resale setting is enabled |
| Specific resale price amount | number | float | Enable when Resale option B is selected. Specific resale price amount of the ticket to be resold
It is editable or used only if organizer resale setting is enabled |
| The Resale & Purchase Agreement URL | string | 512 char | The Resale & Purchase Agreement URL in P2P resale It is editable or used only if organizer resale setting is enabled |
| Ticket Terms & Conditions URL | string | 512 char | Ticket Terms & Conditions URL in P2P resale It is editable or used only if organizer resale setting is enabled |
| Activation Id | string | 50 char | Activation group ID. Different tickets could have different activation method, this group ID make the distinction between them. |
| Activation Time | string | Date Time RFC3339 standard | Activation time at which the system will activate the ticket (display barcode) |
| Activation Method | string | "online"/"offline" | The method using to activate the ticket. online : when activationTime is reached (backend clock), the backend activates the tickets and sends push notifications to trigger a GET /spectator/tickets on the app. offline: the mobile application activates the tickets when time is reaches (mobile clock). Online requires the user to be online, Offline does not. More on Ticket activation: 5-Understanding TIXnGO TIXNGO Activation flow |
| Purchase Date | string | Date Time RFC3339 standard | Date & time at which the ticket was bought |
| Main Ticket Details | string | key (32 char) - value (4096 char) | Ticket details shown on the ticket's front (usually used to set entrance & seat details) |
| Extra Ticket Details | string | key (32 char) - value (4096 char) | Ticket extra details shown on the back of the ticket (usually used to set extra information about the ticket or the event) |
| Hidden Ticket Details | string | key (32 char) - value (4096 char) | Ticket hidden details (not displayed), used for different technical or business purposes, i.e. reserved key such as Seat Map, Sponsors details, etc... |
| Hold (only CSV injection for now) | Boolean | Boolean | Activate ticket holder (ticket is hold for someone else) |
| Holder email (only CSV injection for now) | string | 256 char | Ticket holder email |
| Holder date of birth (only CSV injection for now) | string | rfc3339 standard | Ticket holder date of birth |
| Holder first name (only CSV injection for now) | string | 50 char | Ticket holder first name |
| Holder last name (only CSV injection for now) | string | 100 char | Ticket holder last name |
| Holder gender (only CSV injection for now) | string | 1 char | Ticket holder gender (M, F or U) |
| Holder card number | string | 200 char | Ticket holder ID card number |
| Holder nationality | string | 2 char | Ticket holder nationality |
| Holder passport number | string | 200 char | Ticket holder passport number |
| mobileAppId | string | 256 char | Optional Mobile Application App Id to use associated invitation email template (used by organizer using their own app or branded apps). |
| lang | string | 5 char ISO 639‑1 format | The default language for the Ticket. Injection communications will be sent in this language. Example: fr, en, de, it, es |
| Design Id | string | 256 char | This Design Id representing a design applied to certain tickets in an Event |
| Background Color | string | 7 char hexadecimal color | The background color of the Ticket and the corresponding Design Id (If the Design Id is set). Example: #bbccdd |
...
The CSV file injection tab allows the organizer to inject up to 20'000 tickets at a time.
This page list the jobs that were sent by the organizer and its status for all of them. The uploaded CSV is downloadable as well as the output, explaining which ticket where injected and which were refused (with the error associated with it).
Failed jobs are also downloadable and the error provided on each format error that would be in the injection CSV.
Two templates are available, a minimal required fields template and a complete templates with all possible ticket fields to help with the CSV setup.
The CSV file must be UTF-8 encoded.
A full documentation is available here: https://developer.TIXnGOtixngo.io/pdf/TIXnGOTIXNGO-Injection-Doc.pdf
1.4. Tickets Bulk Update
...
The Communications page allows organizers to view all communication logged in the TIXnGO TIXNGO system. Comm. logs can be search using the email address or phone number of the spectator, the type (email or push) the status (delivered or failed) and the transmission date.
This page displays the spectator's email (recipient of the communication), the reason of this communication, the transmission date, as well as the type and status of this communication.
Clicking on the reason title will show the communication content.
This page also contains a Resend button that lets Organizers resend all filtered communications. This action will trigger a prompt, asking the user to confirm before sending X notifications. This had to be used carefully has one can easily spam someone or even get blacklisted by Amazon Web Services.
...
The Transactions page allows organizers to view all ticket's transactions logged in the TIXnGO TIXNGO system. Transactions can be search using their transaction hash, their date, type or status.
This page displays information about the transaction such the date, the ticket ID, the sender and receiver if it exists, the transaction type, status and hash, as well as the reason if it exists (only for transfers).
Clicking on the ticket ID will redirect to the Support→Ticket screen for this ticket.
Clicking on the sender or recipient email will redirect to the Support→Spectator screen for this spectator.
...
The Pendings page allows organizers to view all "Pendings Tickets" (tickets where the transfer was initiated but the recipient did not yet sing-in to the app and loaded the tickets). Pendings can be search using the ticket ID, the date or the recipient registration source (account was created in TIXnGO TIXNGO system and user has the Mobile application or not yet: "Mobile App" or "External").
This page displays information about the Pendings Tickets, such as the ID, the taxation number, the event ID and name, the sender and recipient emails, the registration source and the date and time of the initiation of transfer.
Clicking on the Ticket ID will redirect to the Support→Ticket screen.
Clicking on the event ID or name will redirect to the Event screen.
Clicking on the sender or recipient will redirect to the Support→Spectator screen.
...
The Mobile Logs page lets the organizer see all logs from the mobile app (for the tickets injected on their mobile app). The logs can be searched by spectator's email, message content, app name (e.g. io.TIXnGOTIXNGO.app is the generic TIXnGO TIXNGO app), log level (i = info, e = error, w = warn), by platform (operating system), or by date.
The information displayed on this page contains the following: Log level, Spectator's email, action that was logged (e.g. authentication, ticket activation, etc...), the content of the logged message, the app name and version, the spectator's devise model, the platform (OS) and the date and time. All this information is mostly useful for debugging purposes.
Clicking on the spectator's email will redirect to Support→Spectator screen.
...
| Variable Name | Variable Description | Backend Key |
| Burger Menu: Item 1 Visibility | Values: ACTIVE, INACTIVE; control whether the link to external website is shown in the menu. Order of the link in the burger menu is fixed. | promo.external.menu.displayed |
| Burger Menu: Item 2 Visibility | Values: ACTIVE, INACTIVE; control whether the link to another app is shown in the menu. Order of the link in the burger menu is fixed. | promo.otherapp.menu.displayed |
| Event List: Promo 1 Position | Values: INACTIVE, TOP, AFTER_FIRST, BOTTOM; controls where the External Portal/Website link box is shown in the event list view of the app. | promo.external.event.position |
| Event List: Promo 2 Position | Values: INACTIVE, TOP, AFTER_FIRST, BOTTOM; controls where the other app link box is shown in the event list view of the app. | promo.otherapp.event.position |
| Event List: Promo 1 Image URL | Link of the image that will be displayed in the box related to the external website | promo.external.image |
| Event List: Promo 2 Image URL | Link of the image that will be displayed in the box related to the otherapp | promo.otherapp.image |
| Relative position between Events List Promo 1 and Promo 2 | Values: OTHERAPP_FIRST, WEBSITE_FIRST; controls the order when both are put in the same location | promo.external.other.prioritized.position |
| Ticket detail key that displayed on activation screen | Values: ticket details main or extra key which define by organizer (eg. Gate, Block, Row, Seat,...) which is used to display on activation screen | design.activation.ticket-details-key |
| Number of minutes before sending a non-transferred reminder in the app | Values: Integer > 0 , | ticket.non-transferred.reminder |
| Number of minutes before sending a non-assigned reminder in the app | Values: Integer > 0 Pop-up message in app for assigning ticket reminder (FIFA). Value indicates the interval between 2 pop-ups. | ticket.non-assigned.reminder |
| Ticket Owner Transfer Alert Keys | Values: List of ticket details main or extra key which define by organizer (eg. Gate, Block, Row, Seat,...) which is used to notify ticket owner transfer tickets (Dependent with ticket.owner.transfer.alerts feature and ticket.owner.transfer.alert.hour ) | ticket.owner.transfer.alerts-keys |
| Enable max amount of active devices security | Values: FALSE, TRUE; disable or enable the max active phones security. | security.session.use-max-active-phone |
| Max number of active devices at once (only if security is enabled) | Values: Integer >0 (For login restriction security purpose) | security.session.max-active-phone |
| Only one active wallet session is allowed | Values: FALSE, TRUE; disable or enable the allowing only one session. (For login restriction security purpose) There are no differences between “Only one active wallet session is allowed” and “Max number of active devices at once (only if security is enabled)” = 1. | security.session.only-allow-one |
| Disable online/offline check if device reached max active sessions | Values: FALSE, TRUE; disable or enable the online check if device readed max active sesssions. (For login restriction security purpose) | security.session.disable-online-check |
| Minimal supported version of mobile application | Values: (with X, Y, Z are Integers and X is required) Oldest version of the app that requires user to install. Using for force update purpose: the organizer can decide to request to have a minimal version of the TIXnGO TIXNGO wallet to be used. So the app will show you a informative screen to ask you to update the app (cannot do anything else in the app). | mobile.version.minimal |
| Latest version of mobile application | Values: (with X, Y, Z are Integers and X is required) Latest version of the app that requires user to install. (Should always same or later than minimal one) There are no features implemented yet related to this one. An example of a potential feature, you might be interested and asked us to develop, would be a new feature to display a pop-up in the app informing a new version is available | mobile.version.latest |
| Number of hours before event start time sending different-gates/blocks first message in the app | Values: Integer > 0 Pop-up message in app for transferring ticket reminder. (Dependent with ticket.owner.transfer.alerts and ticket.owner.transfer.alerts-keys ) In case you have tickets for different block/gates. This is for pop-up message. Organizer need to enable and define these keys to be able to use this feature:
| ticket.owner.transfer.alert.hour |
| Number of minutes before sending different-gates/blocks reminder in the app | Values: Integer > 0 Pop-up message in app for different-gates/blocks reminder , value indicates the interval between 2 pop-ups. Number of minutes before sending different-gates/blocks reminder in the app
| ticket.owner.transfer.alert.interval |
| Amount of days after which the unregistered personal information got anonymized (Set 0 to disable) | Values: Integer > 0 Unregistered emails will be anonymized after this amount of day since the ticket's event expired. | personal.information.anonymize.delay |
...
| Variable Name | Variable Description | Backend Key |
| Burger Menu: Item 1 Title | Title of the menu item for the external website | promo.external.menu.title |
| Burger Menu: Item 1 Description | Sub-text of the menu item for the external website | promo.external.menu.description |
| Event List: Promo 1 Title | Title of the box in the event list for the external website | promo.external.event.title |
| Event List: Promo 1 Description | Sub-text of the event list for the external website | promo.external.event.description |
| Event List: Promo 1 URL | Multilingual link to an external website | promo.external.link |
| Burger Menu: Item 2 Title | Title of the menu item for the other app | promo.otherapp.menu.title |
| Burger Menu: Item 2 Description | Sub-text of the menu item for the other app | promo.otherapp.menu.description |
| Event List: Promo 2 Title | Title of the box in the event list for the other app | promo.otherapp.event.title |
| Event List: Promo 2 Description | Sub-text of the event list for the other app | promo.otherapp.event.description |
| Event List: Promo 2 URL | Multilingual link to an other app | promo.otherapp.link |
| App download link in Emails | Multilingual link to branded app | app.dl.link |
| App name in Emails | Multilingual app name | app.name |
| Push Notifications at ticket injection: content | Content of the push notification recieved at injection | notification.inject.content |
| Push Notifications at ticket injection: title | Title of the push notification recieved at injection | notification.inject.title |
| Push Notifications transfer recipient: content | Content of the push notification recieved by recipient of transfer | notification.received.content |
| Push Notifications transfer recipient: title | Title of the push notification recieved by recipient of transfer | notification.received.title |
| Push Notifications transfer sender: content | Content of the push notification recieved by sender of transfer | notification.sent.content |
| Push Notifications transfer sender: title | Title of the push notification recieved by sender of transfer | notification.sent.title |
| Push Notifications at ticket deletion: content | Content of the push notification recieved when a ticket is deleted | notification.deleted.content |
| Push Notificationsat ticket deletion: title | Title of the push notification recieved when a ticket is deleted | notification.deleted.title |
| Push Notifications at ticket activation: content | Content of the push notification recieved when a ticket is activated | notification.activated.content |
| Push Notificationsat ticket activation: title | Title of the push notification recieved when a ticket is activated | notification.activated.title |
| Push Notifications at transfer cancelation: content | Content of the push notification recieved when a transfer is canceled by sender | notification.cancel.content |
| Push Notifications at transfer cancelation: title | Title of the push notification recieved when a transfer is canceled by sender | notification.cancel.title |
| Push Notifications at transfer accept title | Title of the push notification received by sender when transfer is accepted by the receiver | notification.acknowledge.accepted.title |
| Push Notifications at transfer accept content | Content of the push notification received by sender when transfer is accepted by the receiver | notification.acknowledge.accepted.content |
| Push Notifications at transfer reject title | Title of the push notification received by sender when transfer is rejected by the receiver | notification.acknowledge.rejected.title |
| Push Notifications at transfer reject content | Content of the push notification received by sender when transfer is rejected by the receiver | notification.acknowledge.rejected.content |
| Push Notification at session logout title | Title of the push notification received by a user at session logout | notification.logout.title |
| Push Notification at session logout content | Content of the push notification received by a user at session logout | notification.logout.content |
| Push Notifications at ticket update: content | Content of the push notification received when a ticket's information is updated by organizer | notification.update.ticket.content |
| Push Notifications at ticket update: title | Title of the push notification received when a ticket's information is updated by organizer | notification.update.ticket.title |
| Email subject at ticket injection | Email subject received by initial spectator when a ticket is injected | email.invitation.inject.subject |
| Email body at ticket injection | Email body received by initial spectator when a ticket is injected | email.invitation.inject.body |
| Email subject at ticket transfer to unknown account | Email subject received by recipient of transfer when account is not in TIXnGO TIXNGO system | email.invitation.approval.subject |
| Email body at ticket transfer to unknown account | Email body received by recipient of transfer when account is not in TIXnGO TIXNGO system | email.invitation.approval.body |
| Email subject at ticket transfer to known account | Email subject received by recipient of transfer when account is already in TIXnGO TIXNGO system | email.information.approval.subject |
| Email body at ticket transfer to known account | Email body received by recipient of transfer when account is already in TIXnGO TIXNGO system | email.information.approval.body |
| Email subject at ticket transfer cancellation | Email subject received by recipient of transfer when transfer is cancelled | email.information.cancel.subject |
| Email body at ticket transfer cancellation | Email body received by recipient of transfer when transfer is cancelled | email.information.cancel.body |
| Email subject for reminders | Email subject received when spectator gets a reminder (has not downloaded his ticket yet) | email.reminder.subject |
| Email body for reminders | Email body received when spectator gets a reminder (has not downloaded his ticket yet) | email.reminder.body |
| Email subject at ticket deletion | Email subject received by spectator when a ticket is deleted | email.delete.subject |
| Email body at ticket deletion | Email body received by spectator when a ticket is deleted | email.delete.body |
| Email subject at transfer has been auto_canceled successfully | Email subject received by spectator(transfer receiver) when a ticket is auto_canceled | email.information.automaticallycancel.subject |
| Email body at transfer has been auto_canceled successfully | Email body received by spectator(transfer receiver) when a ticket is auto_canceled | email.information.automaticallycancel.body |
...
The Charts page is a new feature in the TIXnGO TIXNGO system (currently still under development), that shows organizer a graphical representation of the life cycle of their tickets, per event. This feature makes use of our Machine Learning algorithm to give trust scores to each user and detect fraudulent behavior.
What is the Spectators Behavior Analysis?
TIXnGO TIXNGO works everyday to improve security and reduce fraud in your events. The spectator behavior analysis is a Machine Learning tool developed by TIXnGO TIXNGO that classifies the actions of spectators during an event. Its purpose is to provide organizers with a deeper understanding of tickets life within their events and to help detecting users that might need monitoring.
...