Organizer Settings keys in TIXNGO V4
One promise of TIXNGO V4 is that you don’t need to be an Engineer at NASA to configure TIXNGO. Therefore, all the changes applied have the beneficial side effect and allowed us to abandon some settings keys.
Please note that for 2025, most of these “deprecated” legacy settings will still remain visible BUT won’t have any effect on TIXNGO V4. These settings will be properly removed after the last organizer on-boarding to V4.
Organizer Settings kept in V4
Setting Key | Setting Description | TIXNGO Back-Office | ALEX |
|---|---|---|---|
assignee.information.anonymize.delay | Anonymize ticket holder information after x days the event ends (set 0 to turn OFF the feature) | Visible | Visible |
personal.information.anonymize.delay | Default amount of days after which the unregistered personal information got anonymized | Visible | Visible |
bt.instanceid.unique-per-event | Unique Bluetooth instance id per event | Not visible | Visible |
bt.ns.gate | Bluetooth namespace for gate beacon (sha 1 of gate.tixngo.io) | Not visible | Visible |
bt.ns.preparation | Bluetooth namespace for preparation beacon (sha 1 of prep.tixngo.io) | Not visible | Visible |
bt.ns.steward | Bluetooth namespace for steward beacon (sha 1 of steward.tixngo.io) | Not visible | Visible |
ticket.bt.instanceid.constant | If true, make all tickets share the same instance id. Tickets sharing same instance id will be activated by the same beacon. | Not visible | Visible |
email.from | From field when the backend send email | Not visible | Visible |
email.invitation.limit.day-between-dispatch | Minimum number of days before we send an email to the same address | Not visible | Visible |
email.invitation.limit.number-per-event | Maximum number of email sent per event id | Not visible | Visible |
email.reminder.limit.days-first | Number of days before the Event to start sending reminders | Visible | Visible |
email.reminder.limit.max-number | Max number of reminder emails that can be sent per ticket | Visible | Visible |
email.reminder.limit.min-interval | Minimum interval between two reminder in hours | Visible | Visible |
email.reminder.limit.time-first | Hour of the day to send the first reminder, next one will be after the min interval (UTC) | Visible | Visible |
notification.stop.after.event.expiration.days | The system will stop sending notifications after a specified number of days after the event ended (enter the desired number of days; set 0 to turn OFF the feature) | Visible | Visible |
enable.digital-privileges | Show/Hide the DIGITAL PRIVILEGES menu item in the backoffice | Not visible | Visible |
enable.external-wallets | Enable external wallets integration | Not visible | Visible |
enable.contingent.feature | Enable contingent-specific features in the BackOffice | Visible | Visible |
external-wallets.ticket-details.mapping | Key set mapping for exporting seat details to external wallets | Not visible | Visible |
organizer.default.language | Organizer's default language for Back-Office & Wallet use | Not visible | Visible |
ticket.datacollection.custom | (TIXNGO V4) Allow organizer user to add new data collection rules and add new custom fields | Not visible | Visible |
ticket.email.custom | (TIXNGO V4) Allow organizer user to add new email rules and add new email templates | Not visible | Visible |
ticket.transfer.expiration | (TIXNGO V4) Pending Transfers will be automatically cancelled after X hours | Not visible | Visible |
ticket.transfer.reminder.properties | (TIXNGO V4) Transfer reminder alert on ticket properties | Not visible | Visible |
tixngo.features.wip | Features are under development | Not visible | Visible |
tixngo4.transition.enabled | Enable TIXNGO 4 Transition (TIXNGO 3.5) where data are sync back to DynamoDB Wallet Service | Not visible | Visible |
mobile.version.latest | Latest supported mobile app version | Not visible | Visible |
mobile.version.minimal | Minimal supported mobile app version | Not visible | Visible |
mobile.logs.retention | Mobile log retention period: retains logs for x MONTHs after creation date | Not visible | Visible |
organizer.api-key.max | Number of api keys a single organizer can have | Not visible | Visible |
ticket.activation.delay | Default time for time-based activation methods, x hours before event start time | Visible | Visible |
ticket.pin.default | Default pin code. If 000000 is provided, then a random value will be chosen for each event/activation group | Not visible | Visible |
Organizer Settings deprecated in V4
Setting Key | Setting Description | Topic | Why they are not kept ? |
|---|---|---|---|
enable.isolated.campaign.job | Run the notification campaign job on an isolated backend instance) | Campaigns V3 (legacy) | Replaced by Campaigns V4 |
push.notification.campaign.batch_size | Push notification campaign batch size | Campaigns V3 (legacy) | Replaced by Campaigns V4 |
push.notification.campaign.delay | Interval (in minutes) between split notification campaign schedules | Campaigns V3 (legacy) | Replaced by Campaigns V4 |
email.approval.must-send | If true, always send email to spectator at transfer (even if registered) | Emails V3 (legacy) | Replaced by Communication Engine V4 |
email.delete.must-send | If true, send an email at ticket deletion (even if registered) | Emails V3 (legacy) | Replaced by Communication Engine V4 |
email.ticket.invitation.nextreceiveperiodtime | Consolidate tickets purchased in one single email - timeframe | Emails V3 (legacy) | Replaced by Communication Engine V4 |
ticket.bulk-actions.quantity | Enable Single Email for Bulk Tickets Transfer feature | Emails V3 (legacy) | Replaced by Communication Engine V4 |
enable.ticket-detail.bulk-update | Enable ticket detail bulk update feature | Tickets V3 (legacy) | Feature does not exist yet in V4 |
fraud-detection.enable | If true, enable the fraud detection module Job | Chars V3 (legacy) | Feature does not exist yet in V4 |
reference.data.editable.ticket.detail.keys | Editable keys for ticket details at event level | Tickets V3 (legacy) | Feature won’t exist in V4 due to data structure change. |
io.tixngo.app.ffwc20 | If true, Ticket Holder persists after a transfer | Garbage V3 (legacy) |
|
allow.activation-method.onl | Allow the online activation method | Tickets V3 (legacy) | ONLINE activation is not supported since 2023 |
clean.up.ticket.processed.period | Delete all entries in ticket_processed table if the created_date is more than x days back (set 0 to turn OFF the feature) | Tickets V3 (legacy) | Replaced by Feedback Interface V4 |
diff.earliest-export-date | Earliest export date of the ticket diff | Tickets V3 (legacy) | Replaced by Feedback Interface V4 |
diff.ignore-on-event-update | Enable ignore notifying tickets affected by update event | Tickets V3 (legacy) | Replaced by Feedback Interface V4 |
diff.oldest-considered-tickets | Number of days after the event, to stop pushing ticket changes to the feedback interface | Tickets V3 (legacy) | Replaced by Feedback Interface V4 |
enable.details.from.event | Enable displayed ticket details from event level | Tickets V3 (legacy) | Feature does not exist yet in V4 |
mobile.appid.default | Mobile app id that will be associated with the ticket if not provided | Garbage V3 (legacy) | mobile_application_id is mandatory for V4 Injection |
ticket.approval.cancel.delay | Default amount of time (hour) after which the pending transfers will be cancelled | Transfers V3 (legacy) | Replaced by V4 dedicated new setting |
ticket.resell.allow | If true, allow the resell (transfer with price) of a ticket | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.resell.allow.after-activation | If true, allow the resell of a ticket after its activation | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.allow | If true, allow the transfer of a ticket. Else forbid it. | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.allow.after-activation | If true, allow the transfer of a ticket after its activation | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.allow.after-bt-activation | If true, allow the transfer of a ticket after its bluetooth activation. Need allowTransferAfterActivation = true | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.allow.after-control | If true, allow the transfer of a ticket after its control | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.allow.main-applicant | If true, allow the transfer of a Main Applicant's ticket | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.assign.limit | Upper bound of transfer level of a ticket for assign function | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.keep-one | If true, the spectator must keep at least one ticket of the group | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.keep-one-at-inject | If true, the initial spectator must keep at least one ticket of the group (the others will have no constraints) | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.max.number | Maximum number of transfer of a ticket. -1 is infinity. | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.max.profit | percentage of the price that is allowed as maximum profit in a resell. -1 is infinity | Transfers V3 (legacy) | Replaced by V4 Usage Rules |
ticket.transfer.persist-holder | If true, Ticket Holder persists after a transfer | Transfers V3 (legacy) | GDPR compliance, we should not keep personal data when a ticket changes owner. |