There are many features, settings, and content that TIXNGO allows organizers to configure themselves on this Settings page. Only Backoffice users with role AU will be able to view and edit on this page.
Before any settings, make sure you select the correct Mobile App ID in the upper right of the page to update.
For the details of each key, make sure you check the section here.
Application settings
Go to Settings page > Click Application settings tab
Those settings are related to some specific features that will display or work on the app. Below are all related features that you can configure:
Promo items on Burger Menu:
TIXNGO offer organizer the posibility to have up to 2 promo items on burger menu.
Each promo item on burger menu is associated with 4 components: visibility, title, description and URLs. (Note: URLs for burger promo items are same as event list promo items)
You can decide to show them on app or not as well as customizing the content and URLs associated with them.
- Make it visible : Changing the value of 2 keys below to active (Settings > Application Settings)
external.event.position (Burger Menu: Item 1 Visibility)
promo.otherapp.menu.displayed (Burger Menu: Item 2 Visibility)
- Change content: you can update the content for those respectively keys on Multilingual settings for item 1 and item 2:
- external.menu.title (Burger Menu: Item 1 Title)
- external.menu.description (Burger Menu: Item 1 Description)
- external.link (Event List: Promo 1 Url)
- otherapp.menu.title (Burger Menu: Item 2 Title)
- otherapp.menu.description (Burger Menu: Item 2 Title)
- otherapp.link (Event List: Promo 2 Url)
- Titles and URLs for all supported languages must be filled in order to activate the burger promo items.
Promo items on Event List:
Similar to promo items on burger menu, TIXNGO also allow organizer to have up to 2 promo items on event list screen.
Each promo item on Event List is associated with 5 components: visibility, image URL, title, description and URLs. (Note: URLs for burger promo items are same as event list promo items)
- Make it visible: changing 2 keys below to value top/bottom/after_first
- external.event.position (Event List: Promo 1 Position)
- otherapp.event.position (Event List: Promo 2 Position)
- Update the image for items:
- external.image (Event List: Promo 1 Image Url)
- otherapp.image (Event List: Promo 2 Image Url)
- Change content: you can update the content for those respectively keys on Multilingual settings for item 1 and item 2:
- external.event.title (Event List: Promo 1 Title)
- external.event.description (Event List: Promo 1 Description)
- external.link (Event List: Promo 1 Url)
- otherapp.event.title (Event List: Promo 2 Title)
- otherapp.event.description (Event List: Promo 2 Description)
- otherapp.link (Event List: Promo 2 Url)
- Titles and image URLs for all supported languages must be filled in order to activate the event list promo items.
- If promo 1 & promo 2 have the same position: you can define if which one will be displayed first by using the key promo.external.other.prioritized.position (Relative position between Events List Promo 1 and Promo 2)
Force Upgrade & Update:
In case your application has a new build (version) and you would like to force every user to be up to date.
- Under Settings > Application settings, looking for these 2 keys to define your latest or minimum supported version.
- version.latest (Latest version of mobile application)
- version.minimal (Minimal supported version of mobile application)
- To force users to upgrade to the latest version (if not upgrade, user won’t be able to use the app), fill the latest mobile app version at key mobile.version.minimal
- To give users the option to upgrade or not (if not upgrade, user can still use the app), fill the latest mobile app version at key mobile.version.latest
Limit max active devices at once:
This feature allows organizer to limit the number of active sesstion for 1 account at once per app.
In order to enable this feature, under Settings > Application Settings, organizers need to:
- Set the key security.session.use-max-active-phone to true (Enable max amount of active devices security)
- Define the max value that you want to limit user at key security.session.max-active-phone (Max number of active devices at once)
Assign reminder for non-assigned tickets:
- Use case: you want to remind user to always assign a name as ticket holder for every ticket they have. This feature is useful to allow organizer to do it.
- What will be displayed on user’s app:
- When user opens app for the first time, a pop-up message in app for assigning ticket reminder. The content of pop-up is editable and translatable on Crowdin for each app.
- If the assignment is not made by user, pop-up will be shown again after interval time that being set on Backoffice.
- Interval time in minutes (between 2 pop-ups) is defined at key ticket.non-assigned.reminder (Number of minutes before sending a non-assigned reminder in the app) and must be greater than 0.
Transfer reminder for non-transfered tickets
- Use case: you want to remind user to transfer their tickets (only allow to keep 1 ticket per event). This feature is useful to allow organizer to do it.
- What will be displayed on user’s app:
- When user opens app for the first time, a pop-up message in app for transfering ticket reminder shown. The content of pop-up is editable and translatable on Crowdin for each app.
- If the transfering is not made by user, pop-up will be shown again after interval time that being set on Backoffice.
- Interval time in minutes (between 2 pop-ups) is defined at key ticket.non-transferred.reminder (Number of minutes before sending a non-transfered reminder in the app) and must be greater than 0
Different seat details reminder:
- User case: user has multiple tickets for 1 event, but different seat details (Block/Gate/Row..), and organizers want to remind users to transfer those tickets with specific seat details.
- The organizer needs to enable the feature need to:
- Set key to true: owner.transfer.alerts (Transfer alert for ticket owner has multiple tickets in different locations) – Settings > Application Features
- Define the time for the first reminder pop-up via key owner.transfer.alert.hour (Number of hours before event start time sending different-gates/blocks first message in the app)
- Define the interval time between 2 pop-ups via key ticket.owner.transfer.alert.interval (Number of minutes before sending different-gates/blocks reminder in the app)
- Define the key to compare tickets with different seat details via key ticket.owner.transfer.alerts-keys (Ticket Owner Transfer Alert Keys)
- What will be displayed:
- X hours before the event start time (setting above), a pop-up message in app for transferring tickets shown. The content of pop-up is editable and translatable on Crowdin for each app.
- If there’s no action from the user, pop-up will be shown again after interval time.
Protect screenshot and screen recording:
This is an on-demand feature and is only available for a paid package.
- Use case: organizer want to prevent users from having QR code in their screenshot and screen recording on their app, but still want to have the option to enable that in some cases.
- Enable the feature on mobile: set key screen.protect.shot.record to true (Protect screenshot and screen recording)
- Configure the special code for disable/enable the feature via key screen.protect.shot.record.secret-code
Customize Ticket Details displayed on Activation Screen
- Under Application Settings, find the key design.activation.ticket-details-key (Ticket detail key that displayed on activation screen)
- Select from the dropdown list which value you want to show on the screen
What will be shown on mobile:
Application features
Under application feature tabs, an organizer can enable/disable a feature on the app by setting the key to a true/false value.
For a full list of those features available, please make sure you check this section
Key features:
- Assignment functionality - assign-holder
- Deleted tickets tab shown on app - deleted-tickets-visibility
- Request mandatory reason for assignment - mandatory-assign-reason
- Prevent screenshot and video recording - screen.protect.shot.record
- Reminder in case user has tickets in different locations - ticket.owner.transfer.alerts
- Option to select language when transfering - transfer-language
- Request reason for transfering ticket - transfer-reason
- Bluetooth activation feature - use-bluetooth
Organizer settings:
Consolidate tickets purchased in one single
- Sometimes, receiving multiple emails for a batch of purchased tickets can be really confusing to users. So this feature helps to consolidate multiple newly injected tickets to only one single email in a period of time.
- The default value should be 0, which means this feature is not Active
- With that feature enabled, 1st emailing is generated right after the very first injection. Then after the interval time (value to be set), another email will be sent including the rest tickets injected during the internal time.
- Unit timeframe: hour
Setting delay time for transferred ticket auto-cancellation
- This feature dedicates the delay time auto-cancellation when a transfer transaction passes a delay time that is set by the organizer, but the recipient still does not accept/reject the ticket.
- Delay unit: hour
Setting reminder emails for non-register users
- This feature is useful to remind those non-register users who have tickets on TIXNGO but have not yet downloaded and created an account on the app.
- In order to send a reminder email, the organizer needs to set these 4 keys below:
- email.reminder.limit.days-first : Number of days before the Event to start sending reminders
- email.reminder.limit.time-first : Hour of the day to send the first reminder, the next one will be after the min interval (UTC)
- email.reminder.limit.min-interval: Minimum interval between two reminders in hours
- email.reminder.limit.max-number: Max number of reminder emails that can be sent per ticket
Setting limited batch for push notification campaign
- As a solution to avoid performance issues during the creation and sending notification campaigns, we recommend organizers define the batch size and interval time between 2 splited schedules.
- There are 2 keys on Back-Office to help you define that:
- push.notification.campaign.batch_size: Push notification campaign batch size
- push.notification.campaign.delay: Interval (in minutes) between split notification campaign schedules
For more information on the Push Notification Campaign, please check this page.
Setting default time for anonymizing unregistered user's personal information
- Based on the GDPR compliance, in some cases, organizers might need to anonymize unregistered users' personal information after a period of time.
- On Back-Office (Organizer settings), organizers can set up an automatical job to do it by configuring the key below:
- personal.information.anonymize.delay: Default amount of days after the event expired date which the unregistered personal information got anonymized
Multilingual settings:
TIXNGO provides a wide range of notification and emails to send to fans which are available to modify on Backoffice via 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 | 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 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 | 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 |
For all details, please follow this page for Notification and Email templates here.