Page Comparison

The TIXNGO Backoffice is a management console for every organizer. It allows to inject, monitor , and edit tickets, events, transactions, spectators and custom app settings. It is accessible at https://backoffice.tixngo.io where organizers can sign in with their account, or create a new one.
This documentation is here to help support teams get a hold of this console.

...

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.

...

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

...

• Update the event's information

  Variable Name	Variable Type	Value length	Variable usage/description
  Event Name	string	128 char	Name of the match
  Website URL	string	128 char	If specified then clickable URL displayed at the Ticket Detailed View
  Event Group Image URL	string	256 char	Display image as per URL on following ticket views: My Tickets - "Group Image"
  Event Group Name	string	128 char	Display name on following view: My Tickets - Event Group Name
  Ribbon Display Time	string	must follow RFC 3339 date format	Time at which a ribbon is displayed on the mobile app to notify spectator to turn on Bluetooth. This Ribbon Display Time is not converted in local browser time as we must set here the Time Zone
  Start Time	string	must follow RFC 3339 date format	Displays Match date and kick-off time at the Ticket View and Ticket Detailed View. This Start Time is not converted in local browser time as we must set here the Time Zone
  Expiration date	string	must follow RFC 3339 date format	Not displayed, this is the Time at which the Event Expires. This Expiration Time is not converted in local browser time as we must set here the Time Zone
  Time Zone	offset	must follow RFC 3339 date format	Time Zone offset for Start Time, Expiration Time & Activation Time of the Event
  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
  Line 1	string	200 char	line 1 of the address
  Line 2	string	200 char	line 2 of the address
  Line 3	string	200 char	line 3 of the address
  Country Code	string	200 char	country code for the address
  Region	string	200 char	region of the event
  Zip	string	200 char	zip code for the address
  Longitude	number	float	longitude of the event's location
  Latitude	number	float	latitude of the event's location
  Mobile App Id	string	256 char	Used as a key to display tickets only for the particular Event
  Ticket Image URL	string	256 char	Display image as per URL on following ticket views: Ticket View, Ticket Detailed View
  Remove Ticket Image URL	Boolean	Boolean	Enable the deletion of all tickets image URLs in that event.
  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. It is editable or used only if organizer resale setting is enabled
  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. (More Details)
  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
  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
  Resale Options	string	100 char	Support organizer define the resale price with three options A, B and C per Transfer Group Id: "Option A: Price range" [the resale price of this ticket is allowed by the event organizer to be resold between a minimum and a maximum] "Option B: Fixed price" [the resale price of this ticket is set by the event organizer] "Option C: Unlimited price" [the resale price of this ticket is allowed by the event organizer to be resold at any price] 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
  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
  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: Value > 0: Increase Value < 0: Decrease 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	must follow RFC 3339 date format	Timestamp at which the tickets in the activation ID will be activated (following the given Activation Method). This Start Time is not converted in local browser time as we must set here the Time Zone
  Activation Method	string	online/offline	Define ticket activation method for this activation ID, can be online or offline. (Used only if a timestamp is given in Activation Time
  Barcode Size	string	key = 128 char; value = 128 char	Used to adjust QR code size in mm. Reflects both width and height. The value must between 10 and 32 (10 <= barcode size <= 32).
  Barcode Position	string	key = 128 char; value = 128 char	Used to adjust QR code position in case if QR code size smaller that smartphone screen width (center, left, right)
  Event Number	number	0 <= number <= 99	Display Event Number on mobile ticket if required
  Enable Covid Check	Boolean	Boolean	Enables or Disable COVID check functionality for given event
  TicketShop Resale URL	string	key = 128 char; value = 128 char	The URL of TicketShop resale
  Prohibited Items Image URL	string	key = 128 char; value = 128 char	Display Prohibited items image from this URL
  Prohibited Items Link	string	key = 128 char; value = 128 char	Makes Prohibited Items Image clickable when redirecting to this link (must provide Image URL)
  Sponsors Image URL	string	key = 128 char; value = 128 char	Display Sponsor image from this URL
  Sponsors Link	string	key = 128 char; value = 128 char	Makes Sponsors Image clickable redirecting to this link (must provide Image URL)
  Seat Map Image URL	string	key = 128 char; value = 128 char	Display Seat Map image from this URL
  Seat Map Link	string	key = 128 char; value = 128 char	Make Seat Map Image clickable redirecting to this link (must provide Image URL)
  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 corresponding Design Id (Example: #bbccdd). If the background color is updated, all the tickets with the corresponding Design Id will be affected
  Ticket Resale Fixed Fee	number	float	For organizer could set amount fee for ticket of P2P resale It is editable or used only if organizer resale setting is enabled
  Ticket Resale Percent Fee	number	float	For organizer could set fee percent for ticket (calculating on resale price) of P2P resale It is editable or used only if organizer resale setting is enabled
  Fee Currency	string	3 char	For organizer could set currency of fee for ticket of P2P resale It is editable or used only if organizer resale setting is enabled

  
  

• See the security information (manual activation pin & Bluetooth instance ID for all activation groups)
• Create/Delete/Edit Questionnaires that can be send to every spectator attending the event.

...

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.

...

...

...

...

...

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.

...