| Table of Contents |
|---|
Event overview
This page gives organizers the overview of all the events that they have on TIXNGO system with statistic numbers related to its ticket status (Injected/Downloaded/Pending/Deleted/Activated/Controlled)
- By default, the event list is filtered from the current date towards and ordered by event start time (earlier event first)
- Every new ticket with a new unique event ID is injected into TIXNGO, which will create a new event on this page
- Under the action column, TIXNGO provides functionalities to edit event details, create a questionnaire, or check codes for activation purposes.
- Beacon information is useful in the case of using Bluetooth activation (via beacon) instead of time-activation.
Ticket statistics
Tickets injected = Total ticket injected per events (including deleted tickets – All)
...
Tickets controlled = Tickets have been controlled at access controlled and data are synced with TIXNGO
Search and filter
- The organizer can search for any specific event by their master event id, master event name, event name, event Id or filter by event start time or end time.
Manual Activation Code
- In order to support a quick operation in case of time-based or bluetooth activation do not work, organizer can use manual activation as a alternative method.
- A code must be entered to activate the ticket and is different per event.
- Event list => Click on shield icon => See Manual Activation ID
Edit event details
- The organizer can edit and update event details after the event is created on TIXNGO (via injection)
Event list => Click Pencil icon => Make changes => Click Apply
- Event group, event information, address modifying will be applied to all existing ticket of the event.
- Activation group, transfer rules, design ID will be applied to all tickets belonging to that groupID
- Resale Ticket Shop (S-360), prohibited items, sponsor, and seat map will be changed accordingly if under ticketDetails.hidden, there’s no value yet for that.
More details on Event Page
| 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" | ||||||||
| string | 128 char | Display name on following view: My Tickets - Event Group Name | |||||||||
| Master Event Name | string | 256 char | Master event is used for filtering purposes in Events and Ticket List screen | ||||||||
| 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 everyticket | . Organizer might want to choseto | have differentresale | 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:
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:
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 |
Multilingual for events
TIXNGO's events information is stored in a flexible format, the data can be displayed in single language or in multilingual mode, it based on type of an event. Although you can edit the translation directly on TIXNGO backoffice, but you need to provide the translated text at injection time. There are two ways to inject a multilingual event to TIXNGO systems:
Injected by CSV and API:
Please read the TIXNGO injection documentation in step 1 (mentioned in CSV Injection screen), and follow the format listed in TIXNGO injection documentation if you use API call to inject your tickets and events to TIXNGO, OR download the CSV Full Template for Multilingual from step 2 and use that file to define your tickets and events information in multilingual (keep the naming of this file "<your free text>multilingual.csv") if you want to inject by CSV.
Injected from S-360:
Please follow the below steps:
...
Support multilingual fields:
...
Organisation > Initialisation > Organisation parameters > Teams
...
Institution > Venue > Venue parameters > Space
...
Institution > Venue > Venue parameters > Sites (General)
...
Institution > Venue > Venue parameters > Sites (Address)
not yet support multilingual
...
Organisation > Catalogue > Ordinary admissions > Competition
...
ticketDetails.main.<sequence>.key
...
any custom value
...
based on used variable
...
ticketDetails.main.<sequence>.value
...
*sequence: the order of information will be displayed on TIXNGO, the sequence is started from 0 and is independent in each section.
And then a report of the multilingual can be exported at Events screen by clicking on "Export Multilingual" button.
CSV format as below:
...
For more detail, please go to this guideline: Multilingual ticket detail labels