Variable Name | Variable Description | Backend Key | Default value | Visible 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 | 0 | yes |
Consolidate tickets purchased in one single email - time-frame | Value: Integer (hour)(count from previous email sending time) Default value = 0 → OFF feature The user should only receive one email for the first injected ticket All other injection during X hours since first email sent will not be sent separately. After X hours, 1 consolidated injection email will be sent including all ticket-Ids injected. | email.ticket.invitation.nextreceiveperiodtime | 0 | yes |
Default amount of days after which the unregistered personal information got anonymized | Value: Integer (hour)(count from event end-time) Default value = 0 → OFF feature If current time is X hours after event end-time, unregistered account information will be anonymized Job run 1:00 UTC everyday | personal.information.anonymize.delay | 0 | yes |
Default amount of time (hour) after which the pending transfers will be cancelled | Value: Integer (hour)(count from transfer initiated) Default value = 0 → OFF feature If current time is X hours after ticket is transferred and no accept/reject is done on recipient's side, the transfer will be cancelled. | ticket.approval.cancel.delay | 0 | yes |
Enable contingent feature | Enable/Disable feature, allowing organizer to filter tickets by contingent | enable.contingent.feature | false | yes |
Hour of the day to send the first reminder, next one will be after the min interval (UTC) | Values: Integer [0, 23] representing hours of the day On selected date, at X(hours) email reminder will be sent to user It is applied for invitation reminder, and unregistered transfer reminder | email.reminder.limit.time-first | 6 | yes |
Interval (in minutes) between split notification campaign schedules | Values: Integer (minutes) (count from the previous notification campaign sent) If one notification campaign is set with (total impacted spectator) > (Batch size), then after X minutes from the previous sending, the next push notification will be sent. | push.notification.campaign.delay | 10 | yes |
Max number of reminder emails that can be sent per ticket | Values: Integer [0, 5] (maximum of 5 reminders per ticket) Email is sent to spectator who has ticket injected but not yet registered on app | email.reminder.limit.max-number | 2 | yes |
Minimum interval between two reminder in hours | Values: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max) It is applied for invitation reminder, and unregistered transfer reminder | email.reminder.limit.min-interval | 48 | yes |
Number of days before the Event, to start sending reminders | Values: Integer >= 0 It is applied for invitation reminder, and unregistered transfer reminder | email.reminder.limit.days-first | 3 | yes |
Push notification campaign batch size | Values: Integer > 0 Size of tickets to search for target audience and split the push notification campaign to each batch | push.notification.campaign.batch_size | 15000 | yes |
Editable keys for ticket details at event level | Organizers can define the list of keys so that its value will be allowed to edit at the "Keys displayed on tickets" section of the Edit event screen | reference.data.editable.ticket.detail.keys | empty list | yes |
Number of tickets to be re-encrypted per execution of the multi-tendency re-encryption job | Values: Integer >= 0 This setting is a read-only key, not allow to update from Backoffice or using API | multitendency.job.barcode-reencryption.limit | 3000 | no |
Number of days after the event, to stop pushing ticket changes to the feedback interface | Values: Integer >= 0 | diff.oldest-considered-tickets | 365 | no |
If true, allow the transfer of a ticket after its bluetooth activation. Need allowTransferAfterActivation = true | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.allow.after-bt-activation | true | no |
Enable displayed ticket details from event level | Values: true/false | enable.details.from.event | false | no |
Enable ignore notifying tickets affected by update event | Values: true/false | diff.ignore-on-event-update | true | no |
Bluetooth namespace for preparation beacon (sha 1 of prep.tixngo.io) | Values: String This setting is a read-only key, not allow to update from Backoffice or using API | bt.ns.preparation | N/A | no |
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.steward | N/A | no |
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.gate | N/A | no |
Maximum number of email sent per event id | Values: Integer > 0 | email.invitation.limit.number-per-event | 100000 | no |
Minimum number of days before we send an email to the same address | Values: Integer | email.invitation.limit.day-between-dispatch | -1 | no |
If true, allow the resell (transfer with price) of a ticket | Values: true/false | ticket.resell.allow | true | no |
If true, allow the resell of a ticket after its activation | Values: true/false | ticket.resell.allow.after-activation | false | no |
Percentage of the price that is allowed as maximum profit in a resell. -1 is infinity | Values: Integer | ticket.transfer.max.profit | -1 | no |
If true, allow the transfer of a Main Applicant's ticket | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.allow.main-applicant | true | no |
If true, Ticket Holder persists after a transfer | Values: true/false if false, remove the assigned information (ticket holder information) | ticket.transfer.persist-holder | false | no |
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.enable | false | no |
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.prefix | empty | no |
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.secret | N/A | no |
If true, enable the fraud detection module Job | Values: true/false Disable enable the Charts feature on TIXNGO Backoffice | fraud-detection.enable | false | no |
Number of API keys a single organizer can have | Values: Integer This setting is a read-only key, not allow to update from Backoffice or using API | organizer.api-key.max | 3 | no |
From field when the backend send email | Values: String | email.from | no-reply@tixngo.io | no |
Default time for time-based activation methods, x hours before event start time | Values: Integer In case the organizers use a time-based activation method but do not provide the time, the default value will be applied | ticket.activation.delay | 3 | yes |
If true, always send email to spectator at transfer (even if registered) | Values: true/false If false, it only send email to unregistered spectators if they are received a ticket from others | email.approval.must-send | true | no |
Default pin code. If 000000 is provided, then a random value will be chosen for each event/activation group | Values: 6 digits If a specific number was provided, it will use this number Priority of activation/deactivation pin code: Event level → this setting value (organizer level) → random 6 digits | ticket.pin.default | 000000 | no |
If true, allow the transfer of a ticket. Else forbid it. | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.allow | true | no |
Maximum number of transfer of a ticket. -1 is infinity. | Values: Integer Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.max.number | -1 | no |
Maximum number of ticket of the same activation group per phone | Values: Integer Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.max.ticket-per-phone | -1 | no |
Maximum number of transfer for the same user | Values: Integer Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.max.transfer-per-phone | -1 | no |
Latest supported mobile app version | Values: app version format This setting is a read-only key, not allow to update from Backoffice or using API | mobile.version.latest | 3.4 | no |
Minimal supported mobile app version | Values: app version format This setting is a read-only key, not allow to update from Backoffice or using API | mobile.version.minimal | 3.4 | no |
If true, the spectator must keep at least one ticket of the group | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.keep-one | false | no |
If true, the initial spectator must keep at least one ticket of the group (the others will have no constraints) | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.keep-one-at-inject | false | no |
If true, make all tickets share the same instance id. Tickets sharing same instance id will be activated by the same beacon. | Values: true/false if true, all the tickets of this organizer have the same Bluetooth instance id if this key set to false, the logic of bt.instanceid.unique-per-event will be applied. *Note: Bluetooth instance id is a random value | ticket.bt.instanceid.constant | false | no |
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-event | false | no |
If true, send an email at ticket deletion (even if registered) | Values: true/false Always send notification email to spectator if their tickets have been deleted | email.delete.must-send | false | no |
If true, allow the transfer of a ticket after its control | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.allow.after-control | false | no |
If true, allow the transfer of a ticket after its activation | Values: true/false Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.allow.after-activation | false | no |
Mobile app id that will be associated with the ticket if not provided | Values: String | mobile.appid.default | io.tixngo.app | no |
Upper bound of transfer level of a ticket for assign function | Values: Integer Default value for injected tickets if this information is not provided at ticket level | ticket.transfer.assign.limit | -1 | no |
Earliest export date of the ticket diff | Values: String If referenceTimestamp of diff endpoint is not provided, the default time will be get from the value of this key | diff.earliest-export-date | 1900-01-01T00:00:00Z | no |
Enable Single Email for Bulk Tickets Transfer feature | Values: Integer Set a specific ticket quantity that triggers consolidated email communication for bulk ticket actions. If the action involves tickets equal to or exceeding this number, a single email will be sent. For actions involving tickets below the defined quantity, the existing behavior (one email per ticket, including ticket details) will remain Default value = 2 (set value = 0 to turn OFF feature) (Minimize the number of emails sent to your spectators for bulk ticket actions) | ticket.bulk-actions.quantity | 2 | yes |
Enable digital privileges feature for an organizer | Values: true/false Allow organizers to see digital privilege on the Backoffice and be able to setup the digital privileges for spectators | enable.digital-privileges | false | no |