There are many features, settings, and content that TIXnGO allows organizers to configure themselves on this Settings page. Only Backoffice users with role AU will be able to view and edit on this page.
Before any settings, make sure you select the correct Mobile App ID in the upper right of the page to update.
| Table of Contents |
|---|
For the details of each key, make sure you check the section here.
...
Go to Settings page > Click Application settings tab
Those settings are related to some specific features that will display or work on the app. Below are all related features that you can configure:
...
- User case: user has multiple tickets for 1 event, but different seat details (Block/Gate/Row..), and organizers want to remind users to transfer those tickets with specific seat details.
- Organizer The organizer needs to enable the feature need to:
- Set key to true: owner.transfer.alerts (Transfer alert for ticket owner has multiple tickets in different locations) – Settings > Application Features
- Define the time for the first reminder pop-up via key owner.transfer.alert.hour (Number of hours before event start time sending different-gates/blocks first message in the app)
- Define the interval time between 2 pop-up ups via key ticket.owner.transfer.alert.interval (Number of minutes before sending different-gates/blocks reminder in the app)
- Define the key to compare tickets with different seat details via key ticket.owner.transfer.alerts-keys (Ticket Owner Transfer Alert Keys)
- What will be displayed:
- X hours before the event start time (setting above), a pop-up message in app for transferring ticket tickets shown. The content of pop-up is editable and translatable on Crowdin for each app.
- If there’s no action from the user, pop-up will be shown again after interval time.
...
This is an on-demand feature and is only available for a paid package.
- Use case: organizer want to prevent users from having QR code in their screenshot and screen recording on their app, but still want to have the option to enable that in some cases.
- Enable the feature on mobile: set key screen.protect.shot.record to true (Protect screenshot and screen recording)
- Configure the special code for disable/enable the feature via key screen.protect.shot.record.secret-code
...
Under application feature tabs, an organizer can enable/disable a feature on the app by setting the key to a true/false value.
For a full list of those features available, please making make sure you check this section
...
- Sometimes, receiving multiple emails for a batch of purchased tickets can be really confusing to users. So this feature helps to consolidate multiple newly injected tickets to only one single email in a period of time.
- Default The default value should be 0, which mean means this feature is not Active
- With that feature enabled, 1st emailing is generated right after the very first injection. Then after the interval time (value to be set), another email will be sent including the rest tickets injected during the internal time.
- Unit timeframe: hour
Setting delay time for
...
transferred ticket auto-cancellation
- This feature dedicates the delay time auto-cancellation when a transfer transaction passes a delay time which that is set by the organizer, but the recipient still does not accept/reject the ticket.
- Delay unit: hour
...
- This feature is useful to remind those non-register users who has ticket have tickets on TIXNGO but have not yet downloaded and created an account on the app.
- In order to sending send a reminder email, the organizer needs to set these 4 keys below:
- email.reminder.limit.days-first : Number of days before the Event to start sending reminders
- email.reminder.limit.time-first : Hour of the day to send the first reminder, the next one will be after the min interval (UTC)
- email.reminder.limit.min-interval: Minimum interval between two reminder reminders in hours
- email.reminder.limit.max-number: Max number of reminder emails that can be sent per ticket
...
- As a solution to avoid performance issue issues during the creation and sending notification campaigns, we recommend organizers to define the batch size and interval time between 2 splited schedules.
- There are 2 keys on Back-Office to help you define that:
- push.notification.campaign.batch_size: Push notification campaign batch size
- push.notification.campaign.delay: Interval (in minutes) between split notification campaign schedules
More For more information on the Push Notification Campaign, please check this page.
...
- Based on the GDPR compliance, in some cases, organizers might need to anonymize unregistered userusers' s personal information after a period of time.
- On Back-Office (Organizer settings), organizers can set up an automatical job to do it by configuring the key below:
- personal.information.anonymize.delay: Default amount of days after the event expired date which the unregistered personal information got anonymized
...
TIXnGO provides a wide range of notification and emails to send to fans which are available to modify on Back-office Backoffice via Multilingual Settings.
...