Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

In this page, you'll find the list of all the available settings in TIXNGO backoffice, a quick introduction of the outcome if activated or used.

Variable Name

Variable Description

Backend Key

Account deletion mode

Standard TIXNGO proccess (STP) or Manage by Organizer (MBO)

If STP, then the deletion is applied with TIXNGO normal process

If MBO, users is redirected to organizer's URL (configured on Crowdin)

account.deletion.mode
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.countdown
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-key
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
Latest version of mobile application

Values: (with X, Y, Z are Integers and X is required)

Latest version of the app that requires user to install. (Should always same or later than minimal one)

There are no features implemented yet related to this one. An example of a potential feature, you might be interested and asked us to develop, would be a new feature to display a pop-up in the app informing a new version is available

mobile.version.latest
Minimal supported version of mobile application

Values: (with X, Y, Z are Integers and X is required)

Oldest version of the app that requires user to install. 

Using for force update purpose: the organizer can decide to request to have a minimal version of the TIXNGO wallet to be used. So the app will show you a informative screen to ask you to update the app (cannot do anything else in the app).

mobile.version.minimal
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.position
Event List: Promo 1 Image URLLink of the image that will be displayed in the box related to the external websitepromo.external.image

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

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

Event List: Promo 2 Position

Values: INACTIVE, TOP, AFTER_FIRST, BOTTOM; controls where the other app link box is shown in the event list view of the app.

promo.otherapp.event.position

Event List: Promo 2 Image URL

Link of the image that will be displayed in the box related to the otherapp

promo.otherapp.image

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

Protect screenshot and screen recording - Secret code to change in-app

If you need to disable protection against screenshots and screen recordings per device, follow the steps:

Step 1: Triple tap on the bottom of the menu (where all details about the app are displayed).
Step 2: Provide a support code on the next screen.

Important notes:
Login out/in keeps the setting. Reinstalling the app removes the setting.

screen.protect.shot.record.secret-code

Disable online/offline check if device reached max active sessions

Values: FALSE, TRUE; disable or enable the online check if device readed max active sesssions.

(For login restriction security purpose)

security.session.disable-online-check

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

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-one
Enable max amount of active devices securityValues: FALSE, TRUE; disable or enable the max active phones security.security.session.use-max-active-phone
Minutes before the event starts to activate tickets offline (set 0 to turn off the feature)

Values: Integer ≥ 0
If the Emergency offline activation feature is enabled, at the configuration time, if ticket is not activated, then activate the ticket offline

ticket.emergency.activation

Number of minutes before sending a non-assigned reminder in the app

Values: Integer > 0
Pop-up message in app for assigning ticket reminder (F.). Value indicates the interval between 2 pop-ups.

ticket.non-assigned.reminder

Number of minutes before sending a non-transferred reminder in the app

Values: Integer > 0 ,
Pop-up message in app for transferring ticket reminder (RBL). Value indicates the interval between 2 pop-ups. 

ticket.non-transferred.reminder

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

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

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



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

Variable Name

Variable Description

Backend Key

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

Deleted Tickets Visibility

Option to display deleted tickets under the section "Deleted Tickets" in the menu. 

deleted-tickets-visibility

Enable quick manual activation feature

Manually activate a ticket by tapping on the Event Number area (on the right side of the ticket image) to go to the next screen and by tapping the yellow icon. This functionality only works the day before the event and during the day of the event. 

quick-manual-activation

enable-crowdin-synctrue: 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
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

Variable Name

Variable Description

Backend Key

Anonymize ticket holder information after x days the event ends (set 0 to turn OFF the feature)

Value: Integer (days)(count from event end-time)
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

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

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

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

Enable contingent feature

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

enable.contingent.feature

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

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

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-number
Minimum interval between two reminder in hoursValues: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max)email.remidner.limit.min-interval
Number of days before the Event, to start sending remindersValues: Integer >= 0email.reminder.limit.days-first
Push notification campaign batch sizeValues: Integer > 0push.notification.campaign.batch_size

Variable Name

Variable Description

Backend Key

Anonymize ticket holder information after x days the event ends (set 0 to turn OFF the feature)

Value: Integer (days)(count from event end-time)
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

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

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

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

Enable contingent feature

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

enable.contingent.feature

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

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

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-number
Minimum interval between two reminder in hoursValues: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max)email.remidner.limit.min-interval
Number of days before the Event, to start sending remindersValues: Integer >= 0email.reminder.limit.days-first
Push notification campaign batch sizeValues: Integer > 0push.notification.campaign.batch_size

Variable Name

Variable Description

Backend Key

Burger Menu: Item 1 Title

Title of the menu item for the external website

promo.external.menu.title

Burger Menu: Item 1 Description 

Sub-text of the menu item for the external website

promo.external.menu.description

Event List: Promo 1 Title

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

promo.external.event.title

Event List: Promo 1 Description

Sub-text of the event list for the external website

promo.external.event.description

Event List: Promo 1 URL

Multilingual link to an external website

promo.external.link

Burger Menu: Item 2 Title

Title of the menu item for the other app

promo.otherapp.menu.title

Burger Menu: Item 2 Description

Sub-text of the menu item for the other app

promo.otherapp.menu.description

Event List: Promo 2 Title

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

promo.otherapp.event.title

Event List: Promo 2 Description

Sub-text of the event list for the other app

promo.otherapp.event.description

Event List: Promo 2 URL

Multilingual link to an other app

promo.otherapp.link

App download link in Emails

Multilingual link to branded app

app.dl.link

App name in Emails

Multilingual app name

app.name

Push Notifications at ticket injection content

Content of the push notification recieved at injection

notification.inject.content

Push Notifications at ticket injection title

Title of the push notification recieved at injection

notification.inject.title

Push Notifications transfer recipient content

Content of the push notification recieved by recipient of transfer

notification.received.content

Push Notifications transfer recipient title

Title of the push notification recieved by recipient of transfer

notification.received.title

Push Notifications transfer sender content

Content of the push notification recieved by sender of transfer

notification.sent.content

Push Notifications transfer sender title

Title of the push notification recieved by sender of transfer

notification.sent.title

Push Notifications at ticket deletion content

Content of the push notification recieved when a ticket is deleted

notification.deleted.content

Push Notifications at ticket deletion title

Title of the push notification recieved when a ticket is deleted

notification.deleted.title

Push Notifications at delete content: Resale pending A ticket for $$event.name$$ has been being resoldnotification.deleted.resale-pending.content
Push Notifications at delete title: Resale pendingTicket being resoldnotification.deleted.resale-pending.title
Push Notifications at delete content: Resale cancelledA reselling ticket for $$event.name$$ has been cancellednotification.deleted.resale-cancelled.content
Push Notifications at delete title: Resale cancelledReselling ticket cancelnotification.deleted.resale-cancelled.title
Push Notifications at delete content: Resold - Resale after distribution to mobile phoneA ticket for $$event.name$$ has been resoldnotification.deleted.resold.content
Push Notifications at delete title: Resold - Resale after distribution to mobile phoneTicket resoldnotification.deleted.resold.title
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.title
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.content
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.title
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.content
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.title
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.content
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.title
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.content
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.title
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.content
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.title
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.content
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.title
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.content
Push Notifications at ticket delete title: Cancelled - RefundedContent of the push notification received when ticket is deleted with delete reason REFUNDEDnotification.deleted.refunded.title
Push Notifications at ticket delete content: Cancelled - RefundedTitle of the push notification received when ticket is deleted with delete reason REFUNDEDnotification.deleted.refunded.content
Push Notifications at ticket delete title: Cancelled by EBOContent of the push notification received when ticket is deleted with delete reason EBO_CANCELLEDnotification.deleted.ebo_cancelled.title
Push Notifications at ticket delete content: Cancelled by EBOTitle of the push notification received when ticket is deleted with delete reason EBO_CANCELLEDnotification.deleted.ebo_cancelled.content
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.title
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
Push Notifications at ticket delete title: Event cancellationContent of the push notification received when ticket is deleted with delete reason ITA_EVENT_CANCELLATIONnotification.deleted.ita_event_cancellation.title
Push Notifications at ticket delete content: Event cancellationTitle of the push notification received when ticket is deleted with delete reason ITA_EVENT_CANCELLATIONnotification.deleted.ita_event_cancellation.content
Push Notifications at ticket delete title: ForbiddenContent of the push notification received when ticket is deleted with delete reason FORBIDDENnotification.deleted.forbidden.title
Push Notifications at ticket delete content: ForbiddenTitle of the push notification received when ticket is deleted with delete reason FORBIDDENnotification.deleted.forbidden.content
Push Notifications at ticket delete title: Invalid printContent of the push notification received when ticket is deleted with delete reason ITA_INVALID_PRINTnotification.deleted.ita_invalid_print.title
Push Notifications at ticket delete content: Invalid printTitle of the push notification received when ticket is deleted with delete reason ITA_INVALID_PRINTnotification.deleted.ita_invalid_print.content
Push Notifications at ticket delete title: Loss - Courier failure situation unclearContent of the push notification received when ticket is deleted with delete reason LOSS_COURIER_FAILUREnotification.deleted.loss_courier_failure.title
Push Notifications at ticket delete content: Loss - Courier failure situation unclearTitle of the push notification received when ticket is deleted with delete reason LOSS_COURIER_FAILUREnotification.deleted.loss_courier_failure.content
Push Notifications at ticket delete title: Loss - Return back to organization distributionContent of the push notification received when ticket is deleted with delete reason LOSS_RETURN_DISTRIBUTIONnotification.deleted.loss_return_distribution.title
Push Notifications at ticket delete content: Loss - Return back to organization distributionTitle of the push notification received when ticket is deleted with delete reason LOSS_RETURN_DISTRIBUTIONnotification.deleted.loss_return_distribution.content
Push Notifications at ticket delete title: Mobile take backContent of the push notification received when ticket is deleted with delete reason MOBILE_TAKE_BACKnotification.deleted.mobile_take_back.title
Push Notifications at ticket delete content: Mobile take backTitle of the push notification received when ticket is deleted with delete reason MOBILE_TAKE_BACKnotification.deleted.mobile_take_back.content
Push Notifications at ticket delete title: Other causeContent of the push notification received when ticket is deleted with delete reason OTHERnotification.deleted.other.title
Push Notifications at ticket delete content: Other causeTitle of the push notification received when ticket is deleted with delete reason OTHERnotification.deleted.other.content
Push Notifications at ticket delete title: Printing issue-Low printing quality or paper jamContent of the push notification received when ticket is deleted with delete reason PRINT_KOnotification.deleted.print_ko.title
Push Notifications at ticket delete content: Printing issue-Low printing quality or paper jamTitle of the push notification received when ticket is deleted with delete reason PRINT_KOnotification.deleted.print_ko.content
Push Notifications at ticket delete title: ReprintContent of the push notification received when ticket is deleted with delete reason REPRINTnotification.deleted.reprint.title
Push Notifications at ticket delete content: ReprintTitle of the push notification received when ticket is deleted with delete reason REPRINTnotification.deleted.reprint.content
Push Notifications at ticket delete title: Reprint - App not working, change to paper ticketContent of the push notification received when ticket is deleted with delete reason REPRINT_APP_PAPERnotification.deleted.reprint_app_paper.title
Push Notifications at ticket delete content: Reprint - App not working, change to paper ticketTitle of the push notification received when ticket is deleted with delete reason REPRINT_APP_PAPERnotification.deleted.reprint_app_paper.content
Push Notifications at ticket delete title: Reprint - Customer requests change to mobile ticketContent of the push notification received when ticket is deleted with delete reason REPRINT_CONTACT_MOBILEnotification.deleted.reprint_contact_mobile.title
Push Notifications at ticket delete content: Reprint - Customer requests change to mobile ticketTitle of the push notification received when ticket is deleted with delete reason REPRINT_CONTACT_MOBILEnotification.deleted.reprint_contact_mobile.content
Push Notifications at ticket delete title: Reprint - Customer requests change to paper ticketContent of the push notification received when ticket is deleted with delete reason REPRINT_CONTACT_PAPERnotification.deleted.reprint_contact_paper.title
Push Notifications at ticket delete content: Reprint - Customer requests change to paper ticketTitle of the push notification received when ticket is deleted with delete reason REPRINT_CONTACT_PAPERnotification.deleted.reprint_contact_paper.content
Push Notifications at ticket delete title: Reprint - Destroyed or unreadable barcodeContent of the push notification received when ticket is deleted with delete reason REPRINT_DAMAGEDnotification.deleted.reprint_damaged.title
Push Notifications at ticket delete content: Reprint - Destroyed or unreadable barcodeTitle of the push notification received when ticket is deleted with delete reason REPRINT_DAMAGEDnotification.deleted.reprint_damaged.content
Push Notifications at ticket delete title: Reprint - Organization requests change to mobile ticketContent of the push notification received when ticket is deleted with delete reason REPRINT_ORG_MOBILEnotification.deleted.reprint_org_mobile.title
Push Notifications at ticket delete content: Reprint - Organization requests change to mobile ticketTitle of the push notification received when ticket is deleted with delete reason REPRINT_ORG_MOBILEnotification.deleted.reprint_org_mobile.content
Push Notifications at ticket delete title: Reprint - Organization requests change to paper ticketContent of the push notification received when ticket is deleted with delete reason REPRINT_ORG_PAPERnotification.deleted.reprint_org_paper.title
Push Notifications at ticket delete content: Reprint - Organization requests change to paper ticketTitle of the push notification received when ticket is deleted with delete reason REPRINT_ORG_PAPERnotification.deleted.reprint_org_paper.content
Push Notifications at ticket delete title: Reprint - PNA requests to on-site collectionContent of the push notification received when ticket is deleted with delete reason REPRINT_PNA_ON_SITEnotification.deleted.reprint_pna_on_site.title
Push Notifications at ticket delete content: Reprint - PNA requests to on-site collectionTitle of the push notification received when ticket is deleted with delete reason REPRINT_PNA_ON_SITEnotification.deleted.reprint_pna_on_site.content
Push Notifications at ticket delete title: Reprint - Reseating after distributionContent of the push notification received when ticket is deleted with delete reason REPRINT_RESEATnotification.deleted.reprint_reseat.title
Push Notifications at ticket delete content: Reprint - Reseating after distributionTitle of the push notification received when ticket is deleted with delete reason REPRINT_RESEATnotification.deleted.reprint_reseat.content
Push Notifications at ticket delete title: ReseatingContent of the push notification received when ticket is deleted with delete reason RESEATnotification.deleted.reseat.title
Push Notifications at ticket delete content: ReseatingTitle of the push notification received when ticket is deleted with delete reason RESEATnotification.deleted.reseat.content
Push Notifications at ticket delete title: Stolen - Ticket stolenContent of the push notification received when ticket is deleted with delete reason THEFTnotification.deleted.theft.title
Push Notifications at ticket delete content: Stolen - Ticket stolenTitle of the push notification received when ticket is deleted with delete reason THEFTnotification.deleted.theft.content
Push Notifications at ticket delete title: Ticket lossContent of the push notification received when ticket is deleted with delete reason LOSSnotification.deleted.loss.title
Push Notifications at ticket delete content: Ticket lossTitle of the push notification received when ticket is deleted with delete reason LOSSnotification.deleted.loss.content
Push 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.title
Push 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.content
Push 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.title
Push 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.content
Push 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.title
Push 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

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.body
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.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.subject
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.body
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.subject
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.body
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.url

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

Variable Name

Variable Description

Backend Key

First name

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

profile.display.firstname

Last name

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

profile.display.lastname

Gender

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

profile.display.gender

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

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

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

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.phonenumber
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.address
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.birthcity
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.birthcountry
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.residencecountry
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.preferredlanguage
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.promoemail
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.tppromoemail
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.tracking

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

Variable Name

Variable Description

Backend Key

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

First name

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

assign.display.firstname

Last name

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

assign.display.lastname

Birth date

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

assign.display.birthdate

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

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

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.address
  • No labels