This page includes all setting keys available on TIXNGO Backoffice which allow organizers to configure on their own.
Where will you see it?
- Go to Settings Page > Select the correct Mobile App ID
Detailed setting keys
Application Settings
Variable Name | Variable Description | Backend Key |
| Account deletion mode | Standard TIXNGO proccess (STP) or Manage by Organizer (MBO) If STP, then the deletion is applied with TIXNGO normal process If MBO, users is redirected to organizer's URL (configured on Crowdin) | account.deletion.mode |
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 | 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 | 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 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.alerts (enable the feature on mobile) · ticket.owner.transfer.alerts-keys (Define the key to compare) | 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 · In case you have tickets for different block/gates. This is pop-up message. Indicates the interval between 2 pop-ups. · Same as above, organizer need to enable and define these keys to be able to use the feature: · ticket.owner.transfer.alerts (enable the feature on mobile) · ticket.owner.transfer.alerts-keys (Define the key to compare) · ticket.owner.transfer.alert.hour (Define the first pop-up time) | 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 |
Application Features
Variable Name | Variable Description | Backend Key |
Assign Holder Feature | Enable / Disable assign-holder feature, allowing spectator to assign a ticket to a Holder | assign-holder |
Bluetooth Feature | Enable / Disable Bluetooth feature, allowing preparation beacon behavior (Only allow ribbon (what is ribbon? How to see colored information ribbons) and reminder "activate Bluetooth" to be showed, Bluetooth Scanner always enable to scan tickets even this feature is enable or not, even on match day or not) | use-bluetooth |
Display Ticket Owner Feature | Enable / Disable display-owner feature, allowing Owner name to be displayed on the ticket | design.display-owner |
Assign Reason Feature | Enable / Disable assign-reason feature, allowing spectator to give a reason when assigning a ticket to a Holder | use-assign-reason |
Transfer Reason Feature | Enable / Disable trasnfer-reason feature, forcing spectator to give a reason when transferring a ticket | transfer-reason |
Mandatory Assign Reason | Enable / Disable assign-reason feature, forcing spectator to give a reason when assigning a ticket to a Holder | mandatory-assign-reason |
Select language when transferring ticket | Enable / Disable transfer-language feature, allowing spectator to select language of email template when transferring ticket | transfer-language |
Deleted Tickets Visibility | Enable / Disable deleted-tickets-visibility feature, displaying deleted tickets on mobile application | deleted-tickets-visibility |
Wristband Activation Feature | Enable / Disable wristband-activation feature, allowing organizer to activate tickets have wristband option (e.g. hospitability room) | wristband-activation |
Transfer alert for ticket owner has multiple tickets in different locations | Enable / Disable ticket.owner.transfer.alerts feature, allowing organizer to notify for ticket owner has multiple tickets in different locations to transfer tickets. (Dependent with ticket.owner.transfer.alerts-keys and ticket.owner.transfer.alert.hour) | ticket.owner.transfer.alerts |
Organizer Settings
Variable Name | Variable Description | Backend Key |
Max number of reminder emails that can be sent | Values: Integer [0, 5] (maximum of 5 reminders per person Type: email | email.reminder.limit.max-number |
Minimum interval between two reminder in hours | Values: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max) Type: email | email.remidner.limit.min-interval |
Time of the day to send the first reminder (UTC timezone) | Values: Integer [0, 23] representing hours of the day Type: email | email.reminder.limit.time-first |
Number of days before the Event, to start sending reminders | Values: Integer >= 0 Type: email | email.reminder.limit.days-first |
Amount of time (hour) after which the pending transfers will be canceled (Set 0 to not auto-cancel pending transfers) | Values: Integer >= 0 Value indicates the number of hours before auto-cancel is triggered (Value = 0 : no auto-cancel) | ticket.approval.cancel.delay |
Consolidate tickets purchased in one single email - timeframe (X hour) | · Value: Integer (hour) Default value = 0, which mean this feature is not Enable. · The user should only receive one email for his first injected purchased ticket. · The system shall block any purchase emails for X hours after the first sending of email for each ticket holder (counting separately for each ticket holder). · If the X (hours) time is past, those emails that are generated in X time will never be sent. | email.ticket.invitation.nextreceiveperiodtime |
Amount of days after which the unregistered personal information got anonymized (Set 0 to disable) | · Automatic anonymization processing X days after the event ended · Set 0 to not auto anonymize unregistered users · Automatic anonymization processing X days after the event ended, X get from the configuration · run every night (ex: 1:00 am server time) · Value: interger >= 0 | personal.information.anonymize.delay |
Multilingual Settings
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 | |
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 delete resale pending content | A ticket for $$event.name$$ has been being resold | notification.deleted.resale-pending.content |
| Push Notifications at delete resale pending title | Ticket being resold | notification.deleted.resale-pending.title |
| Push Notifications at delete resale cancelled content | A reselling ticket for $$event.name$$ has been cancelled | notification.deleted.resale-cancelled.content |
| Push Notifications at delete resale cancelled title | Reselling ticket cancel | notification.deleted.resale-cancelled.title |
| Push Notifications at delete resold content | A ticket for $$event.name$$ has been resold | notification.deleted.resold.content |
| Push Notifications at delete resold | Ticket resold | notification.deleted.resold.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 Notifications at transfer have been auto_canceled successfully title | Title of the push notification received by sender when transfer is auto canceled by TIXNGO system | notification.information.automaticallycancel.title |
| Push Notifications at transfer have been auto_canceled successfully content | Content of the push notification received by sender when transfer is auto canceled by TIXGO system | notification.information.automaticallycancel.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 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 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 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 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 (to recipients) | Email subject received by spectator(transfer receiver) when a ticket is auto_canceled | email.information.automaticallycancel.recipient.subject |
| Email body at transfer has been auto_canceled successfully (to recipients) | Email body received by spectator(transfer receiver) when a ticket is auto_canceled | email.information.automaticallycancel.recipient.body |
| Email subject at transfer has been auto_canceled successfully (to senders) | Email subject received by spectator(transfer sender) when a ticket is auto_canceled | email.information.automaticallycancel.sender.subject |
Email body at transfer has been auto_canceled successfully (to senders) | Email body received by spectator(transfer sender) when a ticket is auto_canceled | email.information.automaticallycancel.sender.subject |
Registration Configuration
Variable Name | Variable Description | Backend Key |
First name | Mandatory: it is required, spectators need to input on mobile apps | profile.display.firstname |
Last name | Mandatory: it is required, spectators need to input on mobile apps | profile.display.lastname |
Gender | Mandatory: it is required, spectators need to input on mobile apps | profile.display.gender |
Birth date | Mandatory: it is required, spectators need to input on mobile apps | profile.display.birthdate |
Nationality | Mandatory: it is required, spectators need to input on mobile apps | profile.display.nationality |
Passport number | Mandatory: it is required, spectators need to input on mobile apps | profile.display.passportnumber |
| Phone number | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.phonenumber |
| Address | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.address |
| Birth city | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.birthcity |
| Birth country | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.birthcountry |
| Residence country | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.residencecountry |
| Preferred language | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.preferredlanguage |
| Promo email | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.check.promoemail |
| Third-party promo email | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.check.tppromoemail |
| Tracking | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | profile.display.check.tracking |
Assignment Configuration
Variable Name | Variable Description | Backend Key |
Assign reason | Mandatory: it is required, spectators need to input on mobile apps | assign.display.reason |
First name | Mandatory: it is required, spectators need to input on mobile apps | assign.display.firstname |
Last name | Mandatory: it is required, spectators need to input on mobile apps | assign.display.lastname |
Birth date | Mandatory: it is required, spectators need to input on mobile apps | assign.display.birthdate |
Email holder | Mandatory: it is required, spectators need to input on mobile apps | assign.display.emailholder |
Phone number | Mandatory: it is required, spectators need to input on mobile apps | assign.display.phonenumber |
| Address | Mandatory: it is required, spectators need to input on mobile apps Optional: it is not required, and visible on mobile apps Not Visible: it is not visible on mobile apps | assign.display.address |
