TIXNGO Portal

Page tree

Page History

Versions Compared

Old Version 17

changes.mady.by.user huyh

Saved on

compared with

New Version Current

changes.mady.by.user huyh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UI Tabs


UI Tab
titleApplication Settings


Variable Name

Variable Description

Backend Key

Default valueVisible on Backoffice
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.modeStandard TIXNGO processyes
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-versionnullyes
Set timer (in second) for green and blue ticket activation screens to disappearThe activation screen on spectator's device will automatically disappear after x secondscolor.fading.countdown0yes
Ticket detail key that displayed on activation screenValues: ticket details main or extra key  which define by organizer (eg. Gate, Block, Row, Seat,...) which is used to display on activation screendesign.activation.ticket-details-keyGateyes
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 documentslegal.document.version-1yes
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.latest0yes
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.minimal0yes
Event List: Promo 1 PositionValues: 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.positiontopyes
Event List: Promo 1 Image URLLink of the image that will be displayed in the box related to the external websitepromo.external.imageexternal promotion image urlyes

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

activeyes
Relative position between Events List Promo 1 and Promo 2Values: OTHERAPP_FIRST, WEBSITE_FIRST; controls the order when both are put in the same locationpromo.external.other.prioritized.positionwebsite_firstyes

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

bottomyes

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 urlyes

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

activeyes

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

New UI (released Jan 2024):

  1. Go to More → Support Details → triple tap on the QR code.
  2. Enter the PIN Code.

Legacy UI:

  1. Triple tap on the bottom of the menu
(
  1. where all details about the app are displayed
)
  1. .
Step 2: Provide a support code on the next screen
  1. 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/Ayes

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

trueyes

Max number of active devices at once (only if security is enabled)

Values: Integer >0
(For login restriction security purpose)

security.session.max-active-phone

5000yes
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.
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-onefalseyes
Enable max amount of active devices securityValues: FALSE, TRUE; disable or enable the max active phones security.security.session.use-max-active-phonefalseyes
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.activation0yes

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

If the value is superior to 0, it will trigger the following: 

  1. QR Code will not be revealed unless the ticket has been assigned

Image Added

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.reminder

0 (disabled)10yes
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.enablefalseyes
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-time0yes

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 (RBL).

Value indicates the interval between 2 pop-ups. 

ticket.reminder.non-transferred.reminder

0 (disabled)10yes

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

1yes

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

60yes

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 listyes
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-1yes
Default huawei app idValues: Integerhuawei.app-id104086747no
Region of cognito user poolValues: Stringcognito.regioneu-west-1no
Cognito app client secretValues: Stringcognito.secretN/Ano
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-frequency10yes
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-id104086747no
Default huawei app secretValues: String
To setup push notification for spectators, who are using Huawei devices (also need the value of huawei.app-id)		huawei.app-secretCognito audience (app client id)Values: Stringcognito.audN/Ano
Default sns platform applicationValues: String
Setup of AWS SNS Service for the ticket app to use push notification		sns.platform-applicationN/Ano
Pushy secret api keyValues: Stringpushy.secret-api-keyN/Ano
Cognito user pool idValues: Stringcognito.poolidN/Ano
Cognito user pool domain nameValues: Stringcognito.domainnameN/Ano
The default identity provider : COGNITOValues: Stringcognito.providerN/Ano
Default huawei app secretValues: Stringhuawei.app-secretN/Ano
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

If true, skip x-security-token filterValues: true/false

security.session.skip-filterfalseno
Default login mode

Currently, TIXNGO is supporting 3 login mode on mobile ticket apps
COGNITO_STANDARD
COGNITO_PINCODE
OIDC

login.modeCOGNITO_STANDARDno
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-firstqrcode.hidden-after-first-check.enablefalseyes
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#4ba6b5yes




true: Allow the mobile ticket app to
UI Tab
titleApplication Features

Customize the

UI Tab
titleApplication Features

Customize the Mobile App experience by enabling/disabling mobile features.

Variable Name

Variable Description

Backend Key

Default valueVisible 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

falseyes

Deleted

Tickets Visibility

items (Tickets & Privileges) menu visibility

Option to display deleted tickets under the section "Deleted

Tickets

Items" in the menu. 

The Deleted privileges section is visible if digital-privileges is also set to true

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

enable-crowdin-sync

falseyes
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

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

Banner on event cells for different-gates/blockstrue: 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

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 feature, allowing organizer to activate tickets have wristband option (e.g. hospitability room)

wristband-activation

falseyes
Email Checker FeatureEmail checker will detect and alert spectators about any special characters or typos in their provided email addresses during transfer ticketsenable-email-suggestiontrueyes
Enable quick manual activation featureManually 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-activationfalseyes

Protect screenshot and screen recording

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.


Image Added

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

trueyes
Banner on event cells for different-gates/blockstrue: 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.bannerfalseyes

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

falseyes

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

falseyes

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

falseyes

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

falseyes

Transfer Reason Feature

Spectators will be asked to choose a predefined reason while transferring tickets (sending tickets via mail). 

transfer-reason

falseyes

Bluetooth Feature

Enable/Disable feature, allowing preparation beacon behavior and its related reminder.

use-bluetooth

falseyes

Wristband Activation Feature

Enable/Disable feature, allowing organizer to activate tickets have wristband option (e.g. hospitability room)

wristband-activation

falseyes

Enable the Accept/Reject transfer feature

Enable/Disable the Accept/Reject transfer feature

enable-accept-reject-transfer

trueyes

Enable the S360 ticket shop resale feature

Enable/Disable the S360 ticket shop resale feature

enable-resale-ticket-shop-s360

falseyes

Main Applicant Feature

Enable/Disable feature, apply the main applicant rule on the mobile tickets

use-main-applicant

falseno

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

falseno

Advanced Transfer Feature

Enable/Disable feature, allowing spectators to the transfer feature in advanced mode

ticket.advance-transfer

falseno

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

falseno



UI Tab
titleOrganizer Settings


Variable Name

Variable Description

Backend Key

Default valueVisible on Backoffice

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

0yes

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

0yes

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

0yes

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

0yes

Enable contingent feature

Enable/Disable feature, allowing organizer to filter tickets by contingent

enable.contingent.feature

falseyes

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

6yes

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

10yes
Max number of reminder emails that can be sent per ticketValues: 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-number2yes
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-interval48yes
Number of days before the Event, to start sending reminders

Values: Integer >= 0

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-first3yes
Push notification campaign batch sizeValues: Integer > 0
Size of tickets to search for target audience and split the push notification campaign to each batch		push.notification.campaign.batch_size15000yes
Editable keys for ticket details at event levelOrganizers 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 screenreference.data.editable.ticket.detail.keysempty listyes
Number of tickets to be re-encrypted per execution of the multi-tendency re-encryption jobValues: Integer >= 0
This setting is a read-only key, not allow to update from Backoffice or using API		multitendency.job.barcode-reencryption.limit3000no
Number of days after the event, to stop pushing ticket changes to the feedback interfaceValues: Integer >= 0diff.oldest-considered-tickets365no
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 provided

ticket.transfer.allow.after-bt-activationtrueno
Enable displayed ticket details from event levelValues: true/falseenable.details.from.eventfalseno
Enable ignore notifying tickets affected by update eventValues: true/falsediff.ignore-on-event-updatetrueno
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		bt.ns.preparationN/Ano
Bluetooth namespace for steward beacon (sha 1 of steward.tixngo.io)Values: String
This setting is a read-only key, not allow to update from Backoffice or using API		bt.ns.stewardN/Ano
Bluetooth namespace for gate beacon (sha 1 of gate.tixngo.io)Values: String
This setting is a read-only key, not allow to update from Backoffice or using API		bt.ns.gateN/Ano
Maximum number of email sent per event idValues: Integer > 0email.invitation.limit.number-per-event100000no
Minimum number of days before we send an email to the same addressValues: Integeremail.invitation.limit.day-between-dispatch-1no
If true, allow the transfer of a Main Applicant's ticketValues: true/false
Default value for injected tickets if this information is not provided		ticket.transfer.allow.main-applicanttrueno
If true, Ticket Holder persists after a transferValues: true/false
if false, remove the assigned information (ticket holder information)		ticket.transfer.persist-holderfalseno
If true, enable the registration link autofill at injection

Enable feature

Values: true/false
applied in case organizer use TIXNGO API to encrypt the link to their spectators' tickets

email.registration-link.enablefalseno
Registration link prefix used in autofill at injection

Prefix of the URL

Values: String
applied in case organizer use TIXNGO API to encrypt the link to their spectators' tickets

the registration URL format: prefix + encrypted email (by using email.registration-link.secret)

email.registration-link.prefixemptyno
Organizer Secret Key for registration link encryption algorithm

Secret key to encrypt email

Values: String
applied in case organizer use TIXNGO API to encrypt the link to their spectators' tickets

email.registration-link.secretN/Ano
If true, enable the fraud detection module JobValues: true/false
Disable enable the Charts feature on TIXNGO Backoffice		fraud-detection.enablefalseno
Number of API keys a single organizer can have
UI Tab
titleOrganizer Settings
Values: Integer >= 0multitendencyjob.barcodereencryptionlimit3000Number of days after the event, to stop pushing ticket changes to the feedback interface Integer >= 0Unique Bluetooth instance id per eventValues: Stringbtnsgate-1 allow the resell (transfer with price) of a ticketresellallowtrue allow the resell of a ticket after its activationticket.transfer.persist-holder enable the registration link autofill at injection

Variable Name

Variable Description

Backend Key

Default valueVisible on Backoffice

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

0yes

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

0yes

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

0yes

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

0yes

Enable contingent feature

Enable/Disable feature, allowing organizer to filter tickets by contingent

enable.contingent.feature

falseyes

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

email.reminder.limit.time-first

6yes

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

10yes
Max number of reminder emails that can be sent per ticketValues: 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-number2yes
Minimum interval between two reminder in hoursValues: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max)email.reminder.limit.min-interval48yes
Number of days before the Event, to start sending remindersValues: Integer >= 0email.reminder.limit.days-first3yes
Push notification campaign batch sizeValues: Integer > 0push.notification.campaign.batch_size15000yes
Editable keys for ticket details at event levelOrganizers 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 screenreference.data.editable.ticket.detail.keysempty listyes
Number of tickets to be re-encrypted per execution of the multi-tendency re-encryption jobValues: Integer
This setting is a read-only key, not allow to update from Backoffice or using API		organizer.api-key.max3no
From field when the backend send emailValues: diff.oldest-considered-tickets365no
If true, allow the transfer of a ticket after its bluetooth activation. Need allowTransferAfterActivation = trueValues: true/falseticket.transfer.allow.after-bt-activationtrueno
Stringemail.fromno-reply@tixngo.iono
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.delay3yes
If true, always send email to spectator at transfer (even if registered)

Values: true/false

bt.instanceid.unique-per-eventfalseno
Enable displayed ticket details from event levelValues: true/falseenable.details.from.eventfalseno
Enable ignore notifying tickets affected by update eventValues: true/falsediff.ignore-on-event-updatetrueno
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		bt.ns.preparationN/Ano
Bluetooth namespace for steward beacon (sha 1 of steward.tixngo.io)Values: String
This setting is a read-only key, not allow to update from Backoffice or using API		bt.ns.stewardN/Ano

If false, it only send email to unregistered spectators if they are received a ticket from others

email.approval.must-sendtrueno
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.default000000no
If true, allow the transfer of a ticket. Else forbid it.Values: true/false
Default value for injected tickets if this information is not provided		ticket.transfer.allowtrueno
Maximum number of transfer of a ticket. -1 is infinity.Values: Integer
Default value for injected tickets if this information is not provided		ticket.transfer.max.number-1no
Latest supported mobile app versionBluetooth namespace for gate beacon (sha 1 of gate.tixngo.io)Values: app version format
This setting is a read-only key, not allow to update from Backoffice or using API		mobile.version.N/AnoValues: Integer > 0invitation.limit.number-per-event2noValues: Integer > 0invitation.limit.day-between-dispatch1no
Maximum number of email sent per event idValues: Integer > 0email.invitation.limit.number-per-event100000no
latest3.4no
Minimal supported mobile app versionValues: app version format
This setting is a read-only key, not allow to update from Backoffice or using API		mobile.version.minimal3.4Minimum number of days before we send an email to the same addressValues: Integeremail.invitation.limit.day-between-dispatchno
If true, the spectator must keep at least one ticket of the groupValues: true/false
Default value for injected tickets if this information is not provided		ticket.transfer.keep-onefalseno
If true, Values: true/falseticket.resell.allow.after-activationfalseno
Fixed amount fee of StripeValues: Doublefee.fixed.stripe0no
Fixed amount fee of organizerValues: Doublefee.fixed.organizer0no
Fixed amount fee of TIXNGOValues: Doublefee.fixed.tixngo0no
Percentage of the price that is allowed as maximum profit in a resell. -1 is infinityValues: Integerticket.transfer.max.profit-1no
If true, allow the transfer of a Main Applicant's ticketValues: true/falseticket.transfer.allow.main-applicanttrueno
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 provided		ticket.transfer.keep-one-at-injectfalseno
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.

*Note: Bluetooth instance id is a random value

ticket.bt.instanceid.constantfalseno
Unique Bluetooth instance id per event

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-eventIf true, Ticket Holder persists after a transferValues: true/falsefalseno
If true, send an email at ticket deletion (even if registered)

Values: true/false

email.registration-link.enablefalseno
Registration link prefix used in autofill at injectionValues: Stringemail.registration-link.prefixemptyno
Organizer Secret Key for registration link encryption algorithmValues: Stringemail.registration-link.secretN/Ano
Maximum number of resale of a ticket. -1 is infinity.Values: Integerticket.resale.max.number-per-ticket-1no
Default amount of time (hour) which the pending resales will be canceledValues: Integerticket.resale.auto-cancel.delay24no
Percent of amount fee of StripeValues: Doublefee.percent.stripe0.01no
Percent of amount fee of organizerValues: Doublefee.percent.organizer0.01no
Percent of amount fee of TIXNGOValues: Doublefee.percent.tixngo0.01no
If true, allow ticket to be resoldValues: true/falseticket.resale.resell-allowfalseno
If true, allow ticket to be resold after activationValues: true/falseticket.resale.resell-allow-after-activationfalseno
Resale & Purchase Agreement URLValues: Stringticket.resale.purchase-agreement-urlemptyno
Ticket Terms & Conditions URLValues: Stringticket.resale.ticket-term-and-condition-urlemptyno
Min resale price decrease (in % of the initial price): numberValues: Doubleticket.resale.min.resale-price-decrease-percent0no
Max resale price increase (in % of the initial price): numberValues: Doubleticket.resale.max.resale-price-increase-percent0no
Specific resale price decrease/increase (in % of the initial price): numberValues: Doubleticket.resale.specific-resale-price-percent0no
Max resale price amount for OPTION CValues: Doubleticket.resale.fixed-resale-prices1000no
Resale Option (A,B or C)Values: Stringticket.resale.resale-optionOPTION_Cno
Flag for define to apply fee to purchaserValues: true/falsefee.charge.purchasertrueno
If true, enable the fraud detection module JobValues: true/falsefraud-detection.enablefalseno
Number of api keys a single organizer can haveValues: Integer
This setting is a read-only key, not allow to update from Backoffice or using API		organizer.api-key.max3no
The limit hour after event happened that could fulfill the payment of the eventValues: Integerorganizer.resale.fulfillpayment.limit.hour12no
From field when the backend send emailValues: Stringemail.fromno-reply@tixngo.iono
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.delay3yes
If true, always send email to spectator at transfer (even if registered)Values: true/falseemail.approval.must-sendtrueno
Default pin code. If 000000 is provided, then a random value will be chosen for each event/activation groupValues: 6 digitsticket.pin.default000000no
If true, allow the transfer of a ticket. Else forbid it.Values: true/falseticket.transfer.allowtrueno
Maximum number of transfer of a ticket. -1 is infinity.Values: Integerticket.transfer.max.number-1no
Maximum number of ticket of the same activation group per phoneValues: Integerticket.transfer.max.ticket-per-phone-1no
Maximum number of transfer for the same userValues: Integerticket.transfer.max.transfer-per-phone-1no
Latest supported mobile app versionValues: app version format
This setting is a read-only key, not allow to update from Backoffice or using API		mobile.version.latest3.4no
Minimal supported mobile app versionValues: app version format
This setting is a read-only key, not allow to update from Backoffice or using API		mobile.version.minimal3.4no
If true, the spectator must keep at least one ticket of the groupValues: true/falseticket.transfer.keep-onefalseno
If true, the initial spectator must keep at least one ticket of the group (the others will have no constraints)Values: true/falseticket.transfer.keep-one-at-injectfalseno
If true, make all tickets share the same instance id. Tickets sharing same instance id will be activated by the same beacon.Values: true/falseticket.bt.instanceid.constantfalseno
If true, send an email at ticket deletion (even if registered)Values: true/falseemail.delete.must-sendfalseno
If true, allow the transfer of a ticket after its controlValues: true/falseticket.transfer.allow.after-controlfalseno
If true, allow the transfer of a ticket after its activationValues: true/falseticket.transfer.allow.after-activationfalseno
Mobile app id that will be associated with the ticket if not providedValues: Stringmobile.appid.defaultio.tixngo.appno
If true, enable feature resale for organizerValues: true/falseorganizer.p2p.resale.enablefalseno
Upper bound of transfer level of a ticket for assign functionValues: Integerticket.transfer.assign.limit-1no
Earliest export date of the ticket diffValues: Stringdiff.earliest-export-date1900-01-01T00:00:00Zno

Always send notification email to spectator if their tickets have been deleted

email.delete.must-sendfalseno
If true, allow the transfer of a ticket after its controlValues: true/false
Default value for injected tickets if this information is not provided		ticket.transfer.allow.after-controlfalseno
If true, allow the transfer of a ticket after its activationValues: true/false
Default value for injected tickets if this information is not provided		ticket.transfer.allow.after-activationfalseno
Mobile app id that will be associated with the ticket if not providedValues: Stringmobile.appid.defaultio.tixngo.appno
Upper bound of transfer level of a ticket for assign functionValues: Integer
Default value for injected tickets if this information is not provided		ticket.transfer.assign.limit-1no
Earliest export date of the ticket diffValues: String
If referenceTimestamp of diff endpoint is not provided, the default time will be get from the value of this key		diff.earliest-export-date1900-01-01T00:00:00Zno

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)

(Minimize the number of emails sent to your spectators for bulk ticket actions)

ticket.bulk-actions.quantity2yes

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-privilegesfalseno

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.period90no



Push Notifications at delete content: Resale pending 
UI Tab
titleMultilingual Settings

TIXNGO provides a wide range of notification and emails to send to fans which are available to modify on Backoffice via Multilingual Settings.

For more details about templates, please have a look at Notification and Email templates. 

Variable Name

Variable Description

Backend Key

Default valueVisible on Backoffice

Burger Menu: Item 1 Title

Title of the menu item for the external website

promo.external.menu.title

external menu titleyes

Burger Menu: Item 1 Description 

Sub-text of the menu item for the external website

promo.external.menu.description

external menu descriptionyes
Burger Menu: Item 1 UrlMultilingual link to burger menu item 1promo.external.menu.urlexternal menu linkyes

Event List: Promo 1 Title

Title of the box in the event list for the external website

promo.external.event.title

external event titleyes

Event List: Promo 1 Description

Sub-text of the event list for the external website

promo.external.event.description

external event descriptionyes

Event List: Promo 1 URL

Multilingual link to an external website

promo.external.link

external linkyes

Burger Menu: Item 2 Title

Title of the menu item for the other app

promo.otherapp.menu.title

other app menu titleyes

Burger Menu: Item 2 Description

Sub-text of the menu item for the other app

promo.otherapp.menu.description

other app menu descriptionyes
Burger Menu: Item 2 UrlMultilingual link to burger menu item 2promo.otherapp.menu.urlother app menu urlyes

Event List: Promo 2 Title

Title of the box in the event list for the other app

promo.otherapp.event.title

other app event titleyes

Event List: Promo 2 Description

Sub-text of the event list for the other app

promo.otherapp.event.description

other app event descriptionyes

Event List: Promo 2 URL

Multilingual link to an other app

promo.otherapp.link

other app linkyes

App download link in Emails

Multilingual link to branded app

app.dl.link

http://r.tixngo.io/ma/pyes

App name in Emails

Multilingual app name

app.name

TIXNGOyes

Push Notifications at ticket injection content

Content of the push notification recieved at injection

notification.inject.content

You received a ticket for "$$event.name$$"yes

Push Notifications at ticket injection title

Title of the push notification recieved at injection

notification.inject.title

New Ticketyes

Push Notifications transfer recipient content

Content of the push notification recieved by recipient of transfer

notification.received.content

You received a ticket from $$spectator.name$$.yes

Push Notifications transfer recipient title

Title of the push notification recieved by recipient of transfer

notification.received.title

New Ticket Receivedyes

Push Notifications transfer sender content

Content of the push notification recieved by sender of transfer

notification.sent.content

Your ticket was successfully transferred to $$spectator.name$$yes

Push Notifications transfer sender title

Title of the push notification recieved by sender of transfer

notification.sent.title

Ticket Sentyes

Push Notifications at ticket deletion content

Content of the push notification recieved when a ticket is deleted

notification.deleted.content

A ticket for $$event.name$$ has been deletedyes

Push Notifications at ticket deletion title

Title of the push notification recieved when a ticket is deleted

notification.deleted.title

Ticket deletedyes
Push Notifications at delete content: Resale pending Content of the push notification received when ticket is deleted with delete reason
RESALE_PENDING		notification.deleted.resale-pending.contentThe ticket for $$event.name$$ is now available for resaleyes
Push Notifications at delete title: Resale pendingTitle of the push notification received when ticket is deleted with delete reason
RESALE_PENDING		notification.deleted.resale-pending.titleTicket available for resaleyes
Push Notifications at delete content: Resale cancelledContent of the push notification received when ticket is deleted with delete reason
RESALE_CANCELLED		notification.deleted.resale-cancelled.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at delete title: Resale cancelledTitle of the push notification received when ticket is deleted with delete reason
RESALE_CANCELLED		notification.deleted.resale-cancelled.titleTicket deletedyes
Push Notifications at delete content: Resold - Resale after distribution to mobile phoneContent of the push notification received when ticket is deleted with delete reason
RESOLD		notification.deleted.resold.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at delete title: Resold - Resale after distribution to mobile phoneTitle of the push notification received when ticket is deleted with delete reason
RESOLD		notification.deleted.resold.titleTicket deletedyes
Push Notifications at ticket delete title: Blacklist - PNA requests to blacklistContent of the push notification received when ticket is deleted with delete reason OTHER_PNA_REQUEST_BLnotification.deleted.other_pna_request_bl.titleTicket deletedyes
Push Notifications at ticket delete content: Blacklist - PNA requests to blacklistTitle of the push notification received when ticket is deleted with delete reason OTHER_PNA_REQUEST_BLnotification.deleted.other_pna_request_bl.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title: Blacklist - Security requests to blacklistContent of the push notification received when ticket is deleted with delete reason OTHER_SECURITY_REQUEST_BLnotification.deleted.other_security_request_bl.titleTicket deletedyes
Push Notifications at ticket delete content: Blacklist - Security requests to blacklistTitle of the push notification received when ticket is deleted with delete reason OTHER_SECURITY_REQUEST_BLnotification.deleted.other_security_request_bl.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title: Cancellation for customer name changeContent of the push notification received when ticket is deleted with delete reason ITA_CUST_NAME_CHANGEnotification.deleted.ita_cust_name_change.titleTicket deletedno
Push Notifications at ticket delete content: Cancellation for customer name changeTitle of the push notification received when ticket is deleted with delete reason ITA_CUST_NAME_CHANGEnotification.deleted.ita_cust_name_change.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title: Cancellation for service reasonContent of the push notification received when ticket is deleted with delete reason ITA_SERVICE_REASONnotification.deleted.ita_service_reason.titleTicket deletedno
Push Notifications at ticket delete content: Cancellation for service reasonTitle of the push notification received when ticket is deleted with delete reason ITA_SERVICE_REASONnotification.deleted.ita_service_reason.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title: Cancellation for theft/ lossContent of the push notification received when ticket is deleted with delete reason ITA_THEFT_LOSSnotification.deleted.ita_theft_loss.titleTicket deletedno
Push Notifications at ticket delete content: Cancellation for theft/ lossTitle of the push notification received when ticket is deleted with delete reason ITA_THEFT_LOSSnotification.deleted.ita_theft_loss.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title: Cancellation for upsellingContent of the push notification received when ticket is deleted with delete reason ITA_UPSELLINGnotification.deleted.ita_upselling.titleTicket deletedno
Push Notifications at ticket delete content: Cancellation for upsellingTitle of the push notification received when ticket is deleted with delete reason ITA_UPSELLINGnotification.deleted.ita_upselling.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title: Cancellation on customer requestContent of the push notification received when ticket is deleted with delete reason ITA_CUSTOMER_REQUESTnotification.deleted.ita_customer_request.titleTicket deletedno
Push Notifications at ticket delete content: Cancellation on customer requestTitle of the push notification received when ticket is deleted with delete reason ITA_CUSTOMER_REQUESTnotification.deleted.ita_customer_request.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title: Cancelled - RefundedContent of the push notification received when ticket is deleted with delete reason REFUNDEDnotification.deleted.refunded.titleTicket deletedno
Push Notifications at ticket delete content: Cancelled - RefundedTitle of the push notification received when ticket is deleted with delete reason REFUNDEDnotification.deleted.refunded.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title: Change card numberContent of the push notification received when ticket is deleted with delete reason CHANGE_RFIDnotification.deleted.change_rfid.titleTicket deletedno
Push Notifications at ticket delete content: Change card numberTitle of the push notification received when ticket is deleted with delete reason CHANGE_RFIDnotification.deleted.change_rfid.content
UI Tab
titleMultilingual Settings

TIXNGO provides a wide range of notification and emails to send to fans which are available to modify on Backoffice via Multilingual Settings.

For more details about templates, please have a look at Notification and Email templates. 

Variable Name

Variable Description

Backend Key

Default valueVisible on Backoffice

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

Burger Menu: Item 1 UrlMultilingual link to burger menu item 1promo.external.menu.url

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

Burger Menu: Item 2 UrlMultilingual link to burger menu item 2promo.otherapp.menu.url

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 Notifications at ticket deletion title

Title of the push notification recieved when a ticket is deleted

notification.deleted.title

A ticket for $$event.name$$ has been
being resold
deletedno
notification.deleted.resale-pending.content
Push Notifications at ticket delete title:
Resale pending
Event cancellationContent of the push notification received when ticket is deleted with delete reason ITA_EVENT_CANCELLATION
Ticket being resold
notification.deleted.
resale-pending
ita_event_cancellation.titleTicket deletedno
Push Notifications at ticket delete content:
Resale cancelledA reselling ticket for $$event.name$$ has been cancellednotification.deleted.resale-cancelled.content
Event cancellationTitle of the push notification received when ticket is deleted with delete reason ITA_EVENT_CANCELLATION
Push Notifications at delete title: Resale cancelledReselling ticket cancel
notification.deleted.
resale-cancelled.titlePush Notifications at delete content: Resold - Resale after distribution to mobile phone
ita_event_cancellation.contentA ticket for $$event.name$$ has been
resoldnotification.
deleted
.resold.contentPush Notifications at delete title: Resold - Resale after distribution to mobile phoneTicket resoldnotification.deleted.resold.title
no
Push Notifications at ticket delete title:
Blacklist - PNA requests to blacklist
ForbiddenContent of the push notification received when ticket is deleted with delete reason
OTHER_PNA_REQUEST_BL
FORBIDDENnotification.deleted.
other_pna_request_bl
forbidden.titleTicket deletedyes
Push Notifications at ticket delete content:
Blacklist - PNA requests to blacklist
ForbiddenTitle of the push notification received when ticket is deleted with delete reason
OTHER_PNA_REQUEST_BL
FORBIDDENnotification.deleted.
other_pna_request_bl.content
forbidden.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Blacklist - Security requests to blacklist
Invalid printContent of the push notification received when ticket is deleted with delete reason
OTHER
ITA_
SECURITY
INVALID_
REQUEST_BL
PRINTnotification.deleted.
other
ita_
security
invalid_
request_bl
print.titleTicket deletedno
Push Notifications at ticket delete content:
Blacklist - Security requests to blacklist
Invalid printTitle of the push notification received when ticket is deleted with delete reason
OTHER
ITA_
SECURITY
INVALID_
REQUEST_BL
PRINTnotification.deleted.
other
ita_
security
invalid_
request_bl
print.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title:
Cancellation for customer name change
Loss - Courier failure situation unclearContent of the push notification received when ticket is deleted with delete reason
ITA
LOSS_
CUST
COURIER_
NAME_CHANGE
FAILUREnotification.deleted.
ita
loss_
cust_name_change.title
courier_failure.titleTicket deletedyes
Push Notifications at ticket delete content:
Cancellation for customer name change
Loss - Courier failure situation unclearTitle of the push notification received when ticket is deleted with delete reason
ITA
LOSS_
CUST
COURIER_
NAME_CHANGE
FAILUREnotification.deleted.
ita
loss_
cust
courier_
name_change
failure.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Cancellation for service reason
Loss - Return back to organization distributionContent of the push notification received when ticket is deleted with delete reason
ITA
LOSS_
SERVICE
RETURN_
REASON
DISTRIBUTIONnotification.deleted.
ita
loss_
service
return_
reason
distribution.titleTicket deletedyes
Push Notifications at ticket delete content:
Cancellation for service reason
Loss - Return back to organization distributionTitle of the push notification received when ticket is deleted with delete reason
ITA
LOSS_
SERVICE
RETURN_
REASON
DISTRIBUTIONnotification.deleted.
ita
loss_
service
return_
reason
distribution.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Cancellation for theft/ loss
Mobile take backContent of the push notification received when ticket is deleted with delete reason
ITA
MOBILE_
THEFT
TAKE_
LOSS
BACKnotification.deleted.
ita
mobile_
theft
take_
loss
back.titleTicket deletedyes
Push Notifications at ticket delete content:
Cancellation for theft/ loss
Mobile take backTitle of the push notification received when ticket is deleted with delete reason
ITA
MOBILE_
THEFT
TAKE_
LOSS
BACKnotification.deleted.
ita
mobile_
theft
take_
loss
back.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Cancellation for upselling
Other causeContent of the push notification received when ticket is deleted with delete reason
ITA_UPSELLING
OTHERnotification.deleted.
ita_upselling
other.titleTicket deletedno
Push Notifications at ticket delete content:
Cancellation for upselling
Other causeTitle of the push notification received when ticket is deleted with delete reason
ITA_UPSELLING
OTHERnotification.deleted.
ita_upselling
other.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title:
Cancellation on customer request
Printing issue-Low printing quality or paper jamContent of the push notification received when ticket is deleted with delete reason
ITA
PRINT_
CUSTOMER_REQUEST
KOnotification.deleted.
ita
print_
customer_request
ko.titleTicket deletedyes
Push Notifications at ticket delete content:
Cancellation on customer request
Printing issue-Low printing quality or paper jamTitle of the push notification received when ticket is deleted with delete reason
ITA
PRINT_
CUSTOMER_REQUEST
KOnotification.deleted.
ita
print_
customer_request
ko.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Cancelled - Refunded
ReprintContent of the push notification received when ticket is deleted with delete reason
REFUNDED
REPRINTnotification.deleted.
refunded
reprint.titleTicket deletedno
Push Notifications at ticket delete content:
Cancelled - Refunded
ReprintTitle of the push notification received when ticket is deleted with delete reason
REFUNDED
REPRINTnotification.deleted.
refunded
reprint.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete title:
Cancelled by EBO
Reprint - App not working, change to paper ticketContent of the push notification received when ticket is deleted with delete reason
EBO
REPRINT_APP_
CANCELLED
PAPERnotification.deleted.
ebo
reprint_app_
cancelled
paper.titleTicket deletedyes
Push Notifications at ticket delete content:
Cancelled by EBO
Reprint - App not working, change to paper ticketTitle of the push notification received when ticket is deleted with delete reason
EBO
REPRINT_APP_
CANCELLED
PAPERnotification.deleted.
ebo
reprint_app_
cancelled
paper.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Change card number
Reprint - Customer requests change to mobile ticketContent of the push notification received when ticket is deleted with delete reason
CHANGE
REPRINT_CONTACT_
RFID
MOBILEnotification.deleted.
change
reprint_contact_
rfid
mobile.titleTicket deletedyes
Push Notifications at ticket delete content:
Change card number
Reprint - Customer requests change to mobile ticketTitle of the push notification received when ticket is deleted with delete reason
CHANGE
REPRINT_CONTACT_
RFID
MOBILEnotification.deleted.
change_rfid.content
reprint_contact_mobile.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Event cancellation
Reprint - Customer requests change to paper ticketContent of the push notification received when ticket is deleted with delete reason
ITA
REPRINT_
EVENT
CONTACT_
CANCELLATION
PAPERnotification.deleted.
ita
reprint_
event
contact_
cancellation
paper.titleTicket deletedyes
Push Notifications at ticket delete content:
Event cancellation
Reprint - Customer requests change to paper ticketTitle of the push notification received when ticket is deleted with delete reason
ITA
REPRINT_
EVENT
CONTACT_
CANCELLATION
PAPERnotification.deleted.
ita
reprint_
event
contact_
cancellation
paper.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Forbidden
Reprint - Destroyed or unreadable barcodeContent of the push notification received when ticket is deleted with delete reason
FORBIDDEN
REPRINT_DAMAGEDnotification.deleted.
forbidden
reprint_damaged.titleTicket deletedyes
Push Notifications at ticket delete content:
Forbidden
Reprint - Destroyed or unreadable barcodeTitle of the push notification received when ticket is deleted with delete reason
FORBIDDEN
REPRINT_DAMAGEDnotification.deleted.reprint_damaged.contentA ticket for $$event.name$$ has been deletedyes
notification.deleted.forbidden.content
Push Notifications at ticket delete title:
Invalid print
Reprint - Organization requests change to mobile ticketContent of the push notification received when ticket is deleted with delete reason
ITA
REPRINT_
INVALID
ORG_
PRINT
MOBILEnotification.deleted.
ita
reprint_
invalid
org_
print
mobile.titleTicket deletedyes
Push Notifications at ticket delete content:
Invalid print
Reprint - Organization requests change to mobile ticketTitle of the push notification received when ticket is deleted with delete reason
ITA
REPRINT_
INVALID
ORG_
PRINT
MOBILEnotification.deleted.
ita
reprint_
invalid
org_
print
mobile.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Loss - Courier failure situation unclear
Reprint - Organization requests change to paper ticketContent of the push notification received when ticket is deleted with delete reason
LOSS
REPRINT_
COURIER
ORG_
FAILURE
PAPERnotification.deleted.
loss
reprint_
courier
org_
failure
paper.titleTicket deletedyes
Push Notifications at
ticket delete content: Loss - Courier failure situation unclear
ticket delete content: Reprint - Organization requests change to paper ticketTitle of the push notification received when ticket is deleted with delete reason
LOSS
REPRINT_
COURIER
ORG_
FAILURE
PAPERnotification.deleted.
loss
reprint_
courier
org_
failure
paper.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Loss
Reprint -
Return back to organization distribution
PNA requests to on-site collectionContent of the push notification received when ticket is deleted with delete reason
LOSS
REPRINT_PNA_
RETURN
ON_
DISTRIBUTION
SITEnotification.deleted.
loss
reprint_pna_
return
on_
distribution
site.titleTicket deletedyes
Push Notifications at ticket delete content:
Loss
Reprint -
Return back to organization distribution
PNA requests to on-site collectionTitle of the push notification received when ticket is deleted with delete reason
LOSS
REPRINT_PNA_
RETURN
ON_
DISTRIBUTION
SITEnotification.deleted.
loss
reprint_pna_
return_distribution.content
on_site.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Mobile take back
Reprint - Reseating after distributionContent of the push notification received when ticket is deleted with delete reason
MOBILE
REPRINT_
TAKE_BACK
RESEATnotification.deleted.
mobile
reprint_
take_back
reseat.titleTicket deletedyes
Push Notifications at ticket delete content:
Mobile take back
Reprint - Reseating after distributionTitle of the push notification received when ticket is deleted with delete reason
MOBILE
REPRINT_
TAKE_BACK
RESEATnotification.deleted.
mobile
reprint_
take_back
reseat.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete title:
Other cause
ReseatingContent of the push notification received when ticket is deleted with delete reason
OTHER
RESEATnotification.deleted.
other
reseat.title
Push Notifications at ticket delete content: Other causeTitle of the push notification received when ticket is deleted with delete reason OTHER
Ticket deletedno
notification.deleted.other.content
Push Notifications at ticket delete
title: Printing issue-Low printing quality or paper jam
content: ReseatingTitle
Content
of the push notification received when ticket is deleted with delete reason
PRINT_KO
RESEATnotification.deleted
.print_ko.title
.reseat.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete
content
title:
Printing issue-Low printing quality or paper jam
Stolen - Ticket stolenContent
Title
of the push notification received when ticket is deleted with delete reason
PRINT_KO
THEFTnotification.deleted.
print_ko.content
theft.titleTicket deletedyes
Push Notifications at ticket delete
title: ReprintContent
content: Stolen - Ticket stolenTitle of the push notification received when ticket is deleted with delete reason
REPRINT
THEFTnotification.deleted
.reprint.title
.theft.contentA ticket for $$event.name$$ has been deletedyes
Push Notifications at ticket delete
content
title:
Reprint
Ticket loss
Title
Content of the push notification received when ticket is deleted with delete reason
REPRINT
LOSSnotification.deleted.
reprint.content
loss.titleTicket deletedno
Push Notifications at
ticket delete title: Reprint - App not working, change to paper ticketContent
ticket delete content: Ticket lossTitle of the push notification received when ticket is deleted with delete reason
REPRINT_APP_PAPER
LOSSnotification.deleted.
reprint_app_paper.title
loss.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete
content
title:
Reprint - App not working, change to paper ticket
Transaction not completedContent
Title
of the push notification received when ticket is deleted with delete reason
REPRINT
ITA_TRANS_
APP
NOT_
PAPER
COMPLETEDnotification.deleted.
reprint
ita_trans_
app
not_
paper.content
completed.titleTicket deletedno
Push Notifications at ticket delete
title: Reprint - Customer requests change to mobile ticketContent
content: Transaction not completedTitle of the push notification received when ticket is deleted with delete reason
REPRINT
ITA_TRANS_
CONTACT
NOT_
MOBILE
COMPLETEDnotification.deleted.
reprint
ita_trans_
contact_mobile.title
not_completed.contentA ticket for $$event.name$$ has been deletedno
Push Notifications at ticket delete
content: Reprint - Customer requests change to mobile ticket
title: Wrong dataContent
Title
of the push notification received when ticket is deleted with delete reason
REPRINT
ITA_
CONTACT
WRONG_
MOBILE
DATAnotification.deleted.
reprint
ita_
contact
wrong_
mobile.content
data.titleTicket deletedno
Push Notifications at ticket delete
title: Reprint - Customer requests change to paper ticketContent
content: Wrong dataTitle of the push notification received when ticket is deleted with delete reason
REPRINT
ITA_
CONTACT
WRONG_
PAPER
DATAnotification.deleted.
reprint
ita_
contact_paper.title
wrong_data.contentA ticket for $$event.name$$ has been deletedno

Push Notifications at ticket

delete content: Reprint - Customer requests change to paper ticket

activation content

Content

Title

of the push notification received when a ticket is

deleted with delete reason REPRINT_CONTACT_PAPER

activated

notification

.deleted.reprint_contact_paper

.activated.content

A ticket for $$event.name$$ has been activatedyes

Push Notifications at ticket

delete title: Reprint - Destroyed or unreadable barcodeContent

activation title

Title of the push notification received when a ticket is

deleted with delete reason REPRINT_DAMAGED

activated

notification.

deleted

activated.

reprint_damaged.title

title

Ticket activatedyes

Push Notifications at

ticket delete content: Reprint - Destroyed or unreadable barcode

transfer cancelation content

Content

Title

of the push notification received when

ticket is deleted with delete reason REPRINT_DAMAGED

a transfer is canceled by sender

notification.

deleted.reprint_damaged.content

cancel.content

The transfer of the ticket "$$event.name$$" has been cancelledyes

Push Notifications at

ticket delete title: Reprint - Organization requests change to mobile ticketContent

transfer cancelation title

Title of the push notification received when

ticket is deleted with delete reason REPRINT_ORG_MOBILE

a transfer is canceled by sender

notification.

deleted.reprint_org_mobile

cancel.title

Ticket Transfer Cancelledyes
Push Notifications at ticket
delete content: Reprint - Organization requests change to mobile ticketTitle
update contentContent of the push notification received when a ticket
is deleted with delete reason REPRINT_ORG_MOBILE
's information is updated by organizernotification.
deleted.reprint_org_mobile.content
update.ticket.contentYour ticket for $$event.name$$ has been updatedyes
Push Notifications at ticket
delete title: Reprint - Organization requests change to paper ticketContent
update titleTitle of the push notification received when a ticket
is deleted with delete reason REPRINT_ORG_PAPER
's information is updated by organizernotification.
deleted.reprint_org_paper
update.ticket.titleTicket Updatedyes

Push Notifications at

ticket delete content: Reprint - Organization requests change to paper ticket

transfer accept title

Title of the push notification received by sender when

ticket is deleted with delete reason REPRINT_ORG_PAPER

transfer is accepted by the receiver

notification.

deleted.reprint_org_paper.content

acknowledge.accepted.title

Ticket Transfer Acceptedyes

Push Notifications at

ticket delete title: Reprint - PNA requests to on-site collection

transfer accept content

Content of the push notification received by sender when

ticket is deleted with delete reason REPRINT_PNA_ON_SITE

transfer is accepted by the receiver

notification.acknowledge.accepted.content

The ticket's transfer for $$event.name$$ was accepted by $$spectator.name$$yes

Push Notifications at transfer reject title

notification.deleted.reprint_pna_on_site.titlePush Notifications at ticket delete content: Reprint - PNA requests to on-site collection

Title of the push notification received by sender when

ticket is deleted with delete reason REPRINT_PNA_ON_SITE

transfer is rejected by the receiver

notification.

deleted.reprint_pna_on_site.content

acknowledge.rejected.title

Ticket Transfer Rejectedyes

Push Notifications at

ticket delete title: Reprint - Reseating after distribution

transfer reject content

Content of the push notification received by sender when

ticket is deleted with delete reason REPRINT_RESEATnotification.deleted.reprint_reseat.title

transfer is rejected by the receiver

notification.acknowledge.rejected.content

The ticket's transfer for $$event.name$$ was rejected by $$spectator.name$$yes
Push Notifications at transfer have been auto_canceled successfully title
Push Notifications at ticket delete content: Reprint - Reseating after distribution
Title of the push notification received by sender when
ticket is deleted with delete reason REPRINT_RESEAT
transfer is auto canceled by TIXNGO systemnotification.
deleted
information.
reprint_reseat.content
automaticallycancel.titleTicket is canceledyes
Push Notifications at
ticket delete title: Reseating
transfer have been auto_canceled successfully contentContent of the push notification received by sender when
ticket is deleted with delete reason RESEAT
transfer is auto canceled by TIXGO systemnotification.information.
deleted.reseat.titlePush Notifications at ticket delete content: Reseating
automaticallycancel.contentYour ticket transfer for $$event.name$$ is canceledyes

Push Notification at session logout title

Title of the push notification received

when ticket is deleted with delete reason RESEAT

by a user at session logout

notification.

deleted.reseat.content

logout.title

Logout from deviceyes

Push

Notifications at ticket delete title: Stolen - Ticket stolen

Notification at session logout content

Content of the push notification received

when ticket is deleted with delete reason THEFT

by a user at session logout

notification.

deleted.theft.titlePush Notifications at ticket delete content: Stolen - Ticket stolen

logout.content

You have been successfully logged outyes

Push Notification to initiate logout of session title

Title of the push notification received

when ticket is deleted with delete reason THEFTnotification.deleted.theft.content

by a user at force logout by security rules

notification.logout.force.title

New connection on your accountyes

Push Notification to initiate logout of session content

Push Notifications at ticket delete title: Ticket loss

Content of the push notification received

when ticket is deleted with delete reason LOSS

by a user at force logout by security rules

notification.

deleted

logout.

loss.titlePush Notifications at ticket delete content: Ticket lossTitle of the push notification received when ticket is deleted with delete reason LOSSnotification.deleted.loss.contentPush Notifications at ticket delete title: Transaction not completedContent of the push notification received when ticket is deleted with delete reason ITA_TRANS_NOT_COMPLETEDnotification.deleted.ita_trans_not_completed.titlePush Notifications at ticket delete content: Transaction not completedTitle of the push notification received when ticket is deleted with delete reason ITA_TRANS_NOT_COMPLETEDnotification.deleted.ita_trans_not_completed.contentPush Notifications at ticket delete title: Wrong dataContent of the push notification received when ticket is deleted with delete reason ITA_WRONG_DATAnotification.deleted.ita_wrong_data.titlePush Notifications at ticket delete content: Wrong dataTitle of the push notification received when ticket is deleted with delete reason ITA_WRONG_DATAnotification.deleted.ita_wrong_data.content

Push Notifications at ticket activation content

Content of the push notification recieved when a ticket is activated

notification.activated.content

Push Notifications at 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 ticket update contentContent of the push notification received when a ticket's information is updated by organizernotification.update.ticket.contentPush Notifications at ticket update titleTitle of the push notification received when a ticket's information is updated by organizernotification.update.ticket.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 titleTitle of the push notification received by sender when transfer is auto canceled by TIXNGO systemnotification.information.automaticallycancel.titlePush Notifications at transfer have been auto_canceled successfully contentContent of the push notification received by sender when transfer is auto canceled by TIXGO systemnotification.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

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

force.content

Another device connected to your account and you will be disconnectedyes

Email subject at ticket injection

Email subject received by initial spectator when a ticket is injected

email.invitation.inject.subject

Refer: How to configure Notification & Email Templatesyes

Email body at ticket injection

Email body received by initial spectator when a ticket is injected

email.invitation.inject.body

Refer: How to configure Notification & Email Templatesyes

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

Refer: How to configure Notification & Email Templatesyes

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

Refer: How to configure Notification & Email Templatesyes

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

Refer: How to configure Notification & Email Templatesyes

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

Refer: How to configure Notification & Email Templatesyes

Email subject at ticket transfer cancellation

Email subject received by recipient of transfer when transfer is cancelled

email.information.cancel.subject

Refer: How to configure Notification & Email Templatesyes

Email body at ticket transfer cancellation

Email body received by recipient of transfer when transfer is cancelled

email.information.cancel.body

Refer: How to configure Notification & Email Templatesyes

Email subject for reminders

Email subject received when spectator gets a reminder (has not downloaded his ticket yet)

email.reminder.subject

Refer: How to configure Notification & Email Templatesyes

Email body for reminders

Email body received when spectator gets a reminder (has not downloaded his ticket yet)

email.reminder.body

Refer: How to configure Notification & Email Templatesyes

Email subject at ticket deletion

Email subject received by spectator when a ticket is deleted

email.delete.subject

Refer: How to configure Notification & Email Templatesyes

Email body at ticket deletion

Email body received by spectator when a ticket is deleted

email.delete.body

Refer: How to configure Notification & Email Templatesyes

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

Refer: How to configure Notification & Email Templatesyes
Email body at transfer has been auto_canceled successfully (to recipients)Email body received by spectator(transfer receiver) when a ticket is auto_canceledemail.information.automaticallycancel.recipient.bodyRefer: How to configure Notification & Email Templatesyes
Email subject at transfer has been auto_canceled successfully (to senders)Email subject received by spectator(transfer sender) when a ticket is auto_canceledemail.information.automaticallycancel.sender.subjectRefer: How to configure Notification & Email Templatesyes

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: How to configure Notification & Email Templatesyes
Email subject for activation code of spectator without ticketEmail subject received by spectator when this spectator is using pin code to login and not yet have a ticket in their walletemail.account.activation.noticket.subjectRefer: How to configure Notification & Email Templatesyes
Email body for activation code of spectator without ticketEmail body received by spectator when this spectator is using pin code to login and not yet have a ticket in their walletemail.account.activation.noticket.bodyRefer: How to configure Notification & Email Templatesyes
Email subject for activation code of spectator with ticketEmail subject received by spectator when this spectator is using pin code to login and already have at least 1 ticket in their walletemail.account.activation.subjectRefer: How to configure Notification & Email Templatesyes
Email body for activation code of spectator with ticketEmail body received by spectator when this spectator is using pin code to login and already have at least 1 ticket in their walletemail.account.activation.bodyRefer: How to configure Notification & Email Templatesyes
Account deletion URLIf 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 appaccount.deletion.urlhttps://r.tixngo.io/account-deletion/p5/index.htmlyes
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.subjectRefer: How to configure Notification & Email Templatesyes
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 accountemail.invitation.bulk.approval.bodyRefer: How to configure Notification & Email Templatesyes
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 accountemail.information.bulk.approval.subjectRefer: How to configure Notification & Email Templatesyes
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 accountemail.information.bulk.approval.bodyRefer: How to configure Notification & Email Templatesyes
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.subjectRefer: How to configure Notification & Email Templatesyes
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.bodyRefer: How to configure Notification & Email Templatesyes
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.subjectRefer: How to configure Notification & Email Templatesyes
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.bodyRefer: How to configure Notification & Email Templatesyes

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.subjectRefer: How to configure Notification & Email Templates

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.bodyRefer: How to configure Notification & Email Templates

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.subjectRefer: How to configure Notification & Email Templates

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.bodyRefer: How to configure Notification & Email Templates
Email body at transfer has been auto_canceled successfully (to recipients)Email body received by spectator(transfer receiver) when a ticket is auto_canceledemail.information.automaticallycancel.recipient.bodyEmail subject at transfer has been auto_canceled successfully (to senders)Email subject received by spectator(transfer sender) when a ticket is auto_canceledemail.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.body

Email subject for activation code of spectator without ticketEmail subject received by spectator when this spectator is using pin code to login and not yet have a ticket in their walletemail.account.activation.noticket.subjectEmail body for activation code of spectator without ticketEmail body received by spectator when this spectator is using pin code to login and not yet have a ticket in their walletemail.account.activation.noticket.bodyEmail subject for activation code of spectator with ticketEmail subject received by spectator when this spectator is using pin code to login and already have at least 1 ticket in their walletemail.account.activation.subjectEmail body for activation code of spectator with ticketEmail body received by spectator when this spectator is using pin code to login and already have at least 1 ticket in their walletemail.account.activation.bodyAccount deletion URLIf 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 appaccount.deletion.url



UI Tab
titleRegistration Configuration

Customize the registration experience in the Mobile App by altering the visibility of spectator fields.

Variable Name

Variable Description

Backend Key

Default valueVisible on Backoffice

First name

Mandatory: it is required, spectators need to input on mobile apps

profile.display.firstnameMandatoryyes

Last name

Mandatory: it is required, spectators need to input on mobile apps

profile.display.lastname

Mandatoryyes

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

Mandatoryyes

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

Optionalyes

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

Optionalyes

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

Optionalyes
Phone numberMandatory: 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.phonenumberOptionalyes
AddressMandatory: 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.addressOptionalyes
Birth cityMandatory: 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.birthcityOptionalyes
Birth countryMandatory: 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.birthcountryOptionalyes
Residence countryMandatory: 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.residencecountryOptionalyes
Preferred languageMandatory: 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.preferredlanguageOptionalyes
Promo emailMandatory: 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.promoemailOptionalyes
Third-party promo emailMandatory: 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.tppromoemailOptionalyes
TrackingMandatory: 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.trackingOptionalyes



UI Tab
titleAssignment Configuration

Customize the ticket assignment experience in the Mobile App by altering the visibility of guests fields.

Variable Name

Variable Description

Backend Key

Default valueVisible 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

Optionalyes

First name

Mandatory: it is required, spectators need to input on mobile apps

assign.display.firstname

Mandatoryyes

Last name

Mandatory: it is required, spectators need to input on mobile apps

assign.display.lastname

Mandatoryyes

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

Optionalyes

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

Optionalyes

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

Optionalyes
AddressMandatory: 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.addressOptionalyes



...