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
Standard TIXNGO process
yes
Target translation version will be applied to ticket app
An upgrade from previous setting key enable-crowdin-sync
With the setting key enable-crowdin-sync, be able to load the latest translated files from Crowdin without release a new version of the apps
More benefit with this new setting key, be able to manage Crowdin version, and point to a specific version of translated files.
mobile.app.translations.target-version
null
yes
Set timer (in second) for green and blue ticket activation screens to disappear
The activation screen on spectator's device will automatically disappear after x seconds
color.fading.countdown
0
yes
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
Gate
yes
Request all users to consent to updated legal documents (version)
Free text allowed, whenever this value is changed, all spectators is required to consent to updated legal documents
legal.document.version
-1
yes
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
0
yes
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
0
yes
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
top
yes
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
external promotion image url
yes
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
active
yes
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
website_first
yes
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
bottom
yes
Event List: Promo 2 Image URL
Link of the image that will be displayed in the box related to the otherapp
promo.otherapp.image
other app promotion image url
yes
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
active
yes
Protect screenshot and screen recording - Secret code to change in-app
If you need to To disable protection against screenshots and screen recordings per device, follow the these steps:
Step 1: Triple tap on the bottom New UI (released Jan 2024):
Go to More → Support Details → triple tap on the QR code.
Enter the PIN Code.
Legacy UI:
Triple tap on the bottom of the menu
(
where all details about the app are displayed
)
.
Step 2: Provide a support code on the next screen
Enter the PIN code.
Important notes:Login out/in keeps the setting. Reinstalling the app removes the setting
This setting persists if you log out and log back in. However, the PIN code must be re-entered if the app is uninstalled and re-installed.
screen.protect.shot.record.secret-code
N/A
yes
Enable online/offline check if device reached max active sessions
Values: true/false; enable/disable the online check if device readed max active sesssions.
(For login restriction security purpose)
security.session.enable-online-check
true
yes
Max number of If you are Online, you will be kicked out
If you are Offline, you will stay in the app and the phone try to kick you out will have error.
Noted:
Online: the last fetch ticket ticket (or any API call) less than 2mins 2secs
Offline: the last fetch ticket ticket (or any API call) more than 2mins 2secs
security.session.enable-online-check
true
yes
Max number of active devices at once (only if security is enabled)
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. It would implies the same behavior. The first one was the first to be implemented. The second one at a later stage.
security.session.only-allow-one
false
yes
Enable max amount of active devices security
Values: FALSE, TRUE; disable or enable the max active phones security.
security.session.use-max-active-phone
false
yes
Minutes before the event starts to activate tickets offline (set 0 to turn off the feature)
Values: Integer ≥ 0 If the Emergency offline activation feature is enabled, at the configuration time, if ticket is not activated, then activate the ticket offline
ticket.emergency.activation
0
yes
Number of minutes before sending a non-assigned reminder in the appan in-app reminder for not yet assigned tickets
Values: Integer > 0
Pop-up message in app for assigning ticket reminder (F.). Value indicates the interval between 2 pop-ups.
ticket.non-assigned.reminder
10
If the value is superior to 0, it will trigger the following:
QR Code will not be revealed unless the ticket has been assigned
2. It will trigger a pop-up message in the app to remind the spectator to assign tickets. The value defined for this parameter represent the number of minutes between 2 pop-ups.
ticket.reminder.non-assigned
0 (disabled)
yes
Enable additional check of non-assigned tickets for transfer reminder
the pop-up & yellow ribbon asking for transferring/assigning tickets will be displayed
true: need to check if the spectator has more than 1 transferable ticket and at least one of them is unassigned false: only need to check if the spectator has more than 1 transferable ticket
ticket.non-transferred.additional-checking.enable
false
yes
Number of hours before event start time sending first transfer reminder
the pop-up & yellow ribbon asking for transferring/assigning tickets will be displayed the first time, X (hours) before event start time
ticket.non-transferred.display-time
0
yes
Number of minutes before sending a non-transferred reminder in the appan in-app reminder for not yet transferred tickets
Values: Integer > 0 , Pop-up message in app for transferring ticket reminder(currently, its require a new build for ticket apps also). .
Value indicates the interval between 2 pop-ups.
ticket.reminder.non-transferred.reminder
10
0 (disabled)
yes
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. Value indicates the number of hours between 1st pop-up and event start time.
(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
1
yes
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
60
yes
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
empty list
yes
Max number of devices used for one spectator account
Values: Integer >= -1 (-1 means no limits) Organizer can define a number of unique devices to be used to login for one account
mobile.limit-devices
-1
yes
Number of minutes before sending a not downloaded reminder in the app
Values: Integer >= 0 (0 to turn off the feature)
After 48 hours or today is on match day and the recipient hasn't download the tickets yet, display the below popup, it will repeat after each value of the given number in minutes
ticket.pending-transfer.reminder-frequency
10
yes
Default huawei app id
Values: Integer To setup push notification for spectators, who are using Huawei devices (also need the value of huawei.app-secret)
huawei.app-id
104086747
no
Default huawei app secret
Values: String To setup push notification for spectators, who are using Huawei devices (also need the value of huawei.app-id)
huawei.app-secret
N/A
noCognito app client secret
Default sns platform application
Values: String
cognito.secret
N/A
no
Default sns platform application
Values: String Setup of Setup of AWS SNS Service for the ticket app to use push notification
sns.platform-application
N/A
no
If true, skip x-security-token filter
Values: true/false
Skip session check of all feature related to session: security.session.only-allow-one security.session.max-active-phone security.session.use-max-active-phone security.session.enable-online-check
security.session.skip-filter
false
no
Default login mode
Currently, TIXNGO is supporting 3 login mode on mobile ticket apps COGNITO_STANDARD COGNITO_PINCODE OIDC
login.mode
COGNITO_STANDARD
no
Enable QRcode hidden after first check on another phone
Values: true/false
The logic when this feature was enable, In case, spectators login with the same account on 2 different devices, if tickets have been checked on 1 device, the QR code will not be displayed on the second phone at the first time, a red screen will be displayed instead. Tickets on second phone still can be activated by staff.
qrcode.hidden-after-first-check.enable
false
yes
Predetermined secure color is associated with ticket design for event day
When injecting a ticket with new designID and the secure color is empty, The secure color = ticket.secure.color.default If ticket.secure.color.default does not have any value, the secure color = default secure color of TIXNGO system
ticket.secure.color.default
#4ba6b5
yes
Ui tab
title
Application Features
Customize the Mobile App experience by enabling/disabling mobile features.
Variable Name
Variable Description
Backend Key
Default value
Visible on Backoffice
Assign Holder Feature
Option to add a name on a ticket with other required information that can be set up under Assignment Configuration.
assign-holder
false
yes
Deleted Tickets Visibilityitems (Tickets & Privileges) menu visibility
Option to display deleted tickets under the section "Deleted TicketsItems" in the menu. deleted-tickets-
The Deleted privileges section is visible if digital-privileges is also set to true
deleted-tickets-visibility
false
yes
Dynamic load from Crowdin (deprecated)
true: Allow the mobile ticket app to load the translation directly from Crowdin, and no need to release a new version of the apps false: All the translations on the mobile ticket app will be based on the translation file in the apps
this setting key will be replaced by mobile.app.translations.target-version (Application Settings tab)while the mobile app is update to a new version
enable-crowdin-sync
false
yes
Email Checker Feature
Email checker will detect and alert spectators about any special characters or typos in their provided email addresses during transfer tickets
enable-email-suggestion
true
yes
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
false
yes
Protect screenshot and screen recordingProtect 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”
Activate this setting to enable screenshot and live recording protection.
If a user attempts to capture a screenshot or record a video while in TIXNGO Wallet, the screenshot will display as a black picture, concealing all information.
If the screenshot is captured while the user is viewing a ticket, a mobile log will be generated in the admin tool. However, if the user takes a screenshot while on another screen (e.g., Home page), no mobile log will be created.
You can set a passcode to to disable this protection manually within the app via the setting screen.protect.shot.record.secret-code in the application settings.
screen.protect.shot.record
true
yes
Banner on event cells for different-gates/blocks
true: Banner on event cells for different-gates/blocks is displayed if the organizers have already defined ticket.owner.transfer.alerts-keys and spectators’ tickets have different values on defined alert keys, and one of them is transferable false: Banner on event cells for different-gates/blocks is not displayed
ticket.owner.transfer.alert.banner
false
yes
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
false
yes
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
false
yes
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
false
yes
Enable message box when transfer ticket
Add an additional step on the transfer screen and allow a spectator to input a message that will be sent to the ticket recipient.
transfer-message
false
yes
Transfer Reason Feature
Spectators will be asked to choose a predefined reason while transferring tickets (sending tickets via mail).
transfer-reason
false
yes
Bluetooth Feature
Enable/Disable feature, allowing preparation beacon behavior and its related reminder.
use-bluetooth
false
yes
Wristband Activation Feature
Enable/Disable feature, allowing organizer to activate tickets have wristband option (e.g. hospitability room)
wristband-activation
false
yes
Main Applicant FeatureEnable the Accept/Reject transfer feature
Enable/Disable feature, apply the main applicant rule on the mobile ticketsthe Accept/Reject transfer feature
enable-accept-reject-transfer
true
yes
Enable the S360 ticket shop resale feature
Enable/Disable the S360 ticket shop resale feature
enable-resale-ticket-shop-s360
false
yes
Main Applicant Feature
Enable/Disable feature, apply the main applicant rule on the mobile tickets
use-main-applicant
false
no
Display past tickets in separated tab
If false, past tickets are displayed in the same list with upcoming tickets If true, past tickets are displayed in separated tab
ticket.separated-past-tickets
false
no
Advanced Transfer Feature
Enable/Disable feature, allowing spectators to the transfer feature in advanced mode
ticket.advance-transfer
false
no
Digital Privileges Feature
Enable/Disable feature, allowing spectators to own an exclusive digital privileges in their mobile ticket app This key will be effected when enable.digital-privileges = true (in Organizer Settings tab)
digital-privileges
false
no
Ui tab
title
Organizer Settings
title
Variable Name
Variable Description
Backend Key
Default value
Visible on Backoffice
Add more detailed data in the multilingual export file
To include(true) or not(false) the activation group and the transfer rule in the multilingual export file Value: Boolean
event.multilingual-export.more-detailed
false
no
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) Default value = 0 → OFF feature If current time is X days after event end-time, ticket holder information will be anonymized. Job run 1:00 UTC everyday
assignee.information.anonymize.delay
0
yes
Consolidate tickets purchased in one single email - time-frame
Value: Integer (hour)(count from previous email sending time) Default value = 0 → OFF feature The user should only receive one email for the first injected ticket All other injection during X hours since first email sent will not be sent separately. After X hours, 1 consolidated injection email will be sent including all ticket-Ids injected.
email.ticket.invitation.nextreceiveperiodtime
0
yes
Default amount of days after which the unregistered personal information got anonymized
Value: Integer (hour)(count from event end-time) Default value = 0 → OFF feature If current time is X hours after event end-time, unregistered account information will be anonymized Job run 1:00 UTC everyday
personal.information.anonymize.delay
0
yes
Default amount of time (hour) after which the pending transfers will be cancelled
Value: Integer (hour)(count from transfer initiated) Default value = 0 → OFF feature If current time is X hours after ticket is transferred and no accept/reject is done on recipient's side, the transfer will be cancelled.
ticket.approval.cancel.delay
0
yes
Enable contingent feature
Enable/Disable feature, allowing organizer to filter tickets by contingent
enable.contingent.feature
false
yes
Hour of the day to send the first reminder, next one will be after the min interval (UTC)
Values: Integer [0, 23] representing hours of the day On selected date, at X(hours) email reminder will be sent to user It is applied for invitation reminder, and unregistered transfer reminder
email.reminder.limit.time-first
6
yes
Interval (in minutes) between split notification campaign schedules
Values: Integer (minutes) (count from the previous notification campaign sent) If one notification campaign is set with (total impacted spectator) > (Batch size), then after X minutes from the previous sending, the next push notification will be sent.
push.notification.campaign.delay
10
yes
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
2
yes
Minimum interval between two reminder in hours
Values: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max) It is applied for invitation reminder, and unregistered transfer reminder
email.reminder.limit.min-interval
48
yes
Number of days before the Event, to start sending reminders
Values: Integer >= 0It is applied for invitation reminder, and unregistered transfer reminder
This parameter specifies the number of days before an event starts to send a reminder to spectators who:
Have a ticket but haven't created an account yet.
Received a ticket via transfer but haven't created an account yet.
email.reminder.limit.days-first
3
yes
Push notification campaign batch size
Values: Integer > 0 Size of tickets to search for target audience and split the push notification campaign to each batch
push.notification.campaign.batch_size
15000
yes
Editable keys for ticket details at event level
Organizers can define the list of keys so that its value will be allowed to edit at the "Keys displayed on tickets" section of the Edit event screen
reference.data.editable.ticket.detail.keys
empty list
yes
Number of tickets to be re-encrypted per execution of the multi-tendency re-encryption job
Values: Integer >= 0 This setting is a read-only key, not allow to update from Backoffice or using API
multitendency.job.barcode-reencryption.limit
3000
no
Number of days after the event, to stop pushing ticket changes to the feedback interface
Values: Integer >= 0
diff.oldest-considered-tickets
365
no
If true, allow the transfer of a ticket after its bluetooth activation. Need allowTransferAfterActivation = true
Values: true/false Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.allow.after-bt-activation
true
no
Enable displayed ticket details from event level
Values: true/false
enable.details.from.event
false
no
Enable ignore notifying tickets affected by update event
Values: true/false
diff.ignore-on-event-update
true
no
Bluetooth namespace for preparation beacon (sha 1 of prep.tixngo.io)
Values: String This setting is a read-only key, not allow to update from Backoffice or using API
Default time for time-based activation methods, x hours before event start time
Values: Integer In case the organizers use a time-based activation method but do not provide the time, the default value will be applied
ticket.activation.delay
3
yes
If true, always send email to spectator at transfer (even if registered)
Values: true/false If false, it only send email to unregistered spectators if they are received a ticket from others
email.approval.must-send
true
no
Default pin code. If 000000 is provided, then a random value will be chosen for each event/activation group
Values: 6 digits If a specific number was provided, it will use this number Priority of activation/deactivation pin code: Event level → this setting value (organizer level) → random 6 digits
ticket.pin.default
000000
no
If true, allow the transfer of a ticket. Else forbid it.
Values: true/false Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.allow
true
no
Maximum number of transfer of a ticket. -1 is infinity.
Values: Integer Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.max.number
-1
no
Maximum number of ticket of the same activation group per phone
Values: Integer Default value for injected tickets if this information is not provided at ticket level
ticket.transfer.max.ticket-per-phone
-1
no
Maximum number of transfer for the same user
Values: Integer Default value for injected tickets if this information is not provided at ticket level
ticket.transfer.max.transfer-per-phone
-1
no
Latest supported mobile app version
Values: app version Latest supported mobile app version
Values: app version format This setting is a read-only key, not allow to update from Backoffice or using API
mobile.version.latest
3.4
no
Minimal supported mobile app version
Values: app version format This setting is a read-only key, not allow to update from Backoffice or using API
mobile.version.minimal
3.4
no
If true, the spectator must keep at least one ticket of the group
Values: true/false Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.keep-one
false
no
If true, the initial spectator must keep at least one ticket of the group (the others will have no constraints)
Values: true/false Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.keep-one-at-inject
false
no
If true, make all tickets share the same instance id. Tickets sharing same instance id will be activated by the same beacon.
Values: true/false if true, all the tickets of this organizer have the same Bluetooth instance id
if this key set to false, the logic of bt.instanceid.unique-per-event will be applied.
Values: true/false if true, all the tickets of this organizer in the same event will have the same Bluetooth instance id
if both ticket.bt.instanceid.constant and bt.instanceid.unique-per-event is set to false, the tickets in the same activation group of an event will share the same Bluetooth instance id
*Note: Bluetooth instance id is a random value
bt.instanceid.unique-per-event
false
no
If true, send an email at ticket deletion (even if registered)
Values: true/false Always send notification email to spectator if their tickets have been deleted
email.delete.must-send
false
no
If true, allow the transfer of a ticket after its control
Values: true/false Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.allow.after-control
false
no
If true, allow the transfer of a ticket after its activation
Values: true/false Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.allow.after-activation
false
no
Mobile app id that will be associated with the ticket if not provided
Values: String
mobile.appid.default
io.tixngo.app
no
Upper bound of transfer level of a ticket for assign function
Values: Integer Default value for injected tickets if this information is not providedat ticket level
ticket.transfer.assign.limit
-1
no
Earliest export date of the ticket diff
Values: String If referenceTimestamp of diff endpoint is not provided, the default time will be get from the value of this key
diff.earliest-export-date
1900-01-01T00:00:00Z
no
Enable Single Email for Bulk Tickets Transfer feature
Values: Integer
Set a specific ticket quantity that triggers consolidated email communication for bulk ticket actions.
If the action involves tickets equal to or exceeding this number, a single email will be sent.
For actions involving tickets below the defined quantity, the existing behavior (one email per ticket, including ticket details) will remain
Default value = 2 (set value = 0 to turn OFF feature)
()
ticket.bulk-actions.quantity
2
yes
Enable digital privileges feature for an organizer
Values: true/false Allow organizers to see digital privilege on the Backoffice and be able to setup the digital privileges for spectators
enable.digital-privileges
false
no
Ui tab
Delete all entries in ticket_processed table if the created_date is more than x days back (set 0 to turn OFF the feature)
Value: Integer (number of days)
clean.up.ticket.processed.period
90
no
Ui tab
title
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.
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.body
Refer:
yes
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
Refer:
yes
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
Refer:
yes
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
Refer:
yes
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
Refer:
yes
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
Email subject sent to recipient when ticket transfer to Unknown account (single email for bulk tickets)
Email subject sent to recipient when ticket transfer to an unregistered account
email.invitation.bulk.approval.subject
Refer:
yes
Email body sent to recipient when ticket transfer to Unknown account (single email for bulk tickets)
Email body sent to recipient when ticket transfer to an unregistered account
email.invitation.bulk.approval.body
Email
Refer:
yes
Email subject sent to recipient when ticket transfer to Known account (single email for bulk tickets)
Email subject sent to recipient when ticket transfer to an already registered account
email.information.bulk.approval.subject
Refer:
yes
Email body sent to recipient when ticket transfer to Known account (single email for bulk tickets)
Email body sent to recipient when ticket transfer to an already registered account
email.information.bulk.approval.body
Refer:
yes
Email subject sent to sender when ticket transfer delivered successfully (single email for bulk tickets)
Email subject sent to sender when ticket transfer delivered successfully (recipient accepted and downloaded the tickets)
email.sent.sender.bulk.subject
Refer:
yes
Email body sent to sender when ticket transfer delivered successfully (single email for bulk tickets)
Email body sent to sender when ticket transfer delivered successfully (recipient accepted and downloaded the tickets)
email.sent.sender.bulk.body
Refer:
yes
Email subject sent to recipient when ticket transfer cancel by sender (single email for bulk tickets)
Email subject sent to recipient of transfer when the transfer is cancelled by sender
email.information.bulk.cancel.subject
Refer:
yes
Email body sent to recipient when ticket transfer cancel by sender (single email for bulk tickets)
Email body sent to recipient of transfer when the transfer is cancelled by
sender
email.information.bulk.cancel.subject
Email body sent to recipient when ticket transfer cancel by sender (single email for bulk tickets)
Email body sent to recipient of transfer when the transfer is cancelled by sender
email.information.bulk.cancel.body
sender
email.information.bulk.cancel.body
Refer:
yes
Email subject sent to spectator for account deletion confirmation If the email address has valid future mobile tickets (the confirmation link is valid for 24 hours)
Email subject sent to spectator to prompt & confirm the deletion intent
If the email address has valid future mobile tickets
Confirmation link is valid for 24 hours
email.account.deletion.confirmation.subject
Refer:
Email body sent to spectator for account deletion confirmation If the email address has valid future mobile tickets (the confirmation link is valid for 24 hours)
Email body sent to spectator to prompt & confirm the deletion intent
If the email address has valid future mobile tickets
Confirmation link is valid for 24 hours
email.account.deletion.confirmation.body
Refer:
Email subject sent to spectator to confirm that their account has been deleted for following cases: • If no valid future mobile tickets are associated with the email address. • Mobile user clicks on the confirmation link before its expired.
Email subject sent to spectator to confirm the finalization of the deletion of his/her account
If no valid future mobile tickets are associated with the email address
Mobile user clicks on the confirmation link before its expired
email.account.deleted.subject
Refer:
Email body sent to spectator to confirm that their account has been deleted for following cases: • If no valid future mobile tickets are associated with the email address. • Mobile user clicks on the confirmation link before its expired.
Email body sent to spectator to confirm the finalization of the deletion of his/her account
If no valid future mobile tickets are associated with the email address
Mobile user clicks on the confirmation link before its expired
email.account.deleted.body
Refer:
Ui tab
title
Registration Configuration
Customize the registration experience in the Mobile App by altering the visibility of spectator fields.
Variable Name
Variable Description
Backend Key
Default value
Visible on Backoffice
First name
Mandatory: it is required, spectators need to input on mobile apps
profile.display.firstname
Mandatory
yes
Last name
Mandatory: it is required, spectators need to input on mobile apps
profile.display.lastname
Mandatory
yes
Gender
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.gender
Mandatory
yes
Birth date
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.birthdate
Optional
yes
Nationality
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.nationality
Optional
yes
Passport 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.passportnumber
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
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
Optional
yes
Ui tab
title
Assignment Configuration
Customize the ticket assignment experience in the Mobile App by altering the visibility of guests fields.
Variable Name
Variable Description
Backend Key
Default value
Visible on Backoffice
Assign reason
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.reason
Optional
yes
First name
Mandatory: it is required, spectators need to input on mobile apps
assign.display.firstname
Mandatory
yes
Last name
Mandatory: it is required, spectators need to input on mobile apps
assign.display.lastname
Mandatory
yes
Birth date
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.birthdate
Optional
yes
Email holder
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.emailholder
Optional
yes
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
assign.display.phonenumber
Optional
yes
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