...
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 | ||
Option to add a name on a ticket with other required information that can be set up under Assignment Configuration. | assign-holder | |||
Deleted Tickets Visibility | Option to display deleted tickets under the section "Deleted Tickets" in the menu. | deleted-tickets-visibility | ||
Enable quick manual activation feature | Manually activate a ticket by tapping on the Event Number area (on the right side of the ticket image) to go to the next screen and by tapping the yellow icon. This functionality only works the day before the event and during the day of the event. | quick-manual-activation | ||
Protect screenshot and screen recording | Protect active QR codes from screenshots and screen recordings. Whenever these actions will be taken, the active QR code is covered with red text “This is a screenshot, not a valid ticket”. | screen.protect.shot.record | ||
Transfer alert for ticket owner who has multiple tickets in different locations | Turn on the functionality to send an alert about conflict within tickets with different seating details in one wallet (Dependent with ticket.owner.transfer.alerts-keys and ticket.owner.transfer.alert.hour) | ticket.owner.transfer.alerts | ||
Enable built-in encryption for activation/deactivation pin | For secure purposes, if this key is set to true, the Manual Activation ID will be encrypted on mobile local storage | ticket.pin.allow-encrypted | ||
Select language when transferring ticket | Add an additional step on the transfer screen and allow a spectator to choose the language of emails that will be sent to the ticket recipient. | transfer-language | ||
Transfer Reason Feature | Spectators will be asked to choose a predefined reason while transferring tickets (sending tickets via mail). | transfer-reason | ||
Bluetooth Feature | Enable/Disable feature, allowing preparation beacon behavior and its related reminder. | use-bluetooth | ||
Wristband Activation Feature | Enable/Disable | Wristband Activation Feature | Enable / Disable wristband-activation feature, allowing organizer to activate tickets have wristband option 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
Organizer Settings
Variable Name | Variable Description | Backend Key | |||
Anonymize ticket holder information after x days the event ends (set 0 to turn OFF the feature) | Value: Integer (days)(count from event end-time) | assignee.information.anonymize.delay | |||
Consolidate tickets purchased in one single email - time-frame | Value: Integer (hour)(count from previous email sending time) | email.ticket.invitation.nextreceiveperiodtime | |||
Default amount of days after which the unregistered personal information got anonymized | Value: Integer (hour)(count from event end-time) | personal.information.anonymize.delay | |||
Default amount of time (hour) after which the pending transfers will be cancelled | Value: Integer (hour)(count from transfer initiated) | ticket.approval.cancel.delay | |||
Enable contingent feature | Enable/Disable feature, allowing organizer to filter tickets by contingent | enable.contingent.feature | |||
Hour | |||||
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, next one will be after the min interval (UTC) | Values: Integer >= 0Type: email[0, 23] representing hours of the day On selected date, at X(hours) email reminder will be sent to user | email.reminder.limit.daystime-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 | |||
Interval (in minutes) between split notification campaign schedules | Values: Integer (minutes) (count from the previous notification campaign sent) | push.notification.campaign.delay | |||
| Max number of reminder emails that can be sent per ticket | Values: Integer [0, 5] (maximum of 5 reminders per ticket) Email is sent to spectator who has ticket injected but not yet registered on app | 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) | email.remidner.limit.min-interval | |||
| Number of days before the Event, to start sending reminders | Values: Integer >= 0 | email.reminder.limit.days-first | |||
| Push notification campaign batch size | Values: Integer > 0 | push.notification.campaign.batch_size | 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 |
| Email subject for activation code of spectator without ticket | Email subject received by spectator when this spectator is using pin code to login and not yet have a ticket in their wallet | email.account.activation.noticket.subject |
| Email body for activation code of spectator without ticket | Email body received by spectator when this spectator is using pin code to login and not yet have a ticket in their wallet | email.account.activation.noticket.body |
| Email subject for activation code of spectator with ticket | Email subject received by spectator when this spectator is using pin code to login and already have at least 1 ticket in their wallet | email.account.activation.subject |
| Email body for activation code of spectator with ticket | Email body received by spectator when this spectator is using pin code to login and already have at least 1 ticket in their wallet | email.account.activation.body |
| Account deletion URL | If a user change Account deletion mode to "Manage by Organizer" he or she must provide the Account deletion URL here, spectators will be redirected to this link when they click on "Delete my account" on the mobile ticket app | account.deletion.url |
...