Objectives & high level scope

Last minute adjustments before the major summer events

Back-Office improvements

We are refining user roles and improving the most-used Backoffice screens. We are also adding pagination and page-to-page navigation in Ticket list search to better support sponsors working with large numbers of tickets.

In addition, we start integrating with organizer's Corporate SSO for Backoffice access. If you are interested by this, please contact your CSM to check if your IDP is already compatible.

Reporting performance improvement

TIXNGO reporting domain is definitely getting traction during operation. We are doing some targeted

Boost notifications

Live notifications on event day PREVIEW

Do you sometimes have spectators reaching the access control without their ticket open in the app? Now a live permanent reminder is displayed on event day when the ticket is activated for a one-tap access to the ticket! This could also lead to a lower rate of no-shows by encouraging last-minute transfers (or put on resell when available).

Show past notifications

Are you sending push notification campaigns but fans still miss them ? This is probably simply because the notification came at a bad time and the fan dismissed it. Now all past campaign notifications are available at anytime, right from the home screen.

Misc.

We are doing small improvements here and there related to the notifications management. Please check the detailed release notes for more details.

Release planning

Here are the planned installation dates of every iteration of this version.

Exact deployment date per slot can vary by a few days for operational reasons.

Detailed release notes

DBV2.6

Miscellaneous improvements

• There is a new variable $$ticket.count$$ available for push notification templates to explicitly communicate to the spectator the number of tickets just injected or transferred.

• It’s now possible to change the event end date & time, even when it is in the past. A last minute change or a configuration mistake caught too late can now be fixed without technical assistance. Please note that this action requires updating all existing tickets, and that it will take some time to reach all spectators' devices.

DBV2.5

Display seating information for non-numbered seats on mobile

The mobile app now shows seating details (entrance, gate, area) for non-numbered seated tickets on the transfer, resale, and deleted ticket screens — using the same layout as numbered seats. Previously, only the seat category and tariff were displayed, making it difficult for spectators with many tickets to identify them during transfers.

Open

Examples of non-numbered seat tickets displayed in ticket selection for transfer screen

MATCH event layout now available with CURIOSITY design

Open

Example of MATCH event type on the CURIOSITY layout

The mobile app now supports the MATCH event type on the CURIOSITY layout for both Upcoming and Past ticket details:

• Match tickets using the CURIOSITY layout now displays the team names and logos instead of the event name.

• Unlike the CLASSIC layout, the competition logo animation is not available in this view to avoid drawing too much attention and undermining the power of the background image

Improved display of main and extra metadata on TIXNGO ticket layouts

• Curiosity layout: Main metadata now appear in a dedicated section 'Before you go'.

• Classic layout: Custom fields disabled from the Main section in the Ticket Design rule are no longer shown in "More info".

DBV2.4

Show past notifications

Are you sending push notification campaigns but fans still miss them ? This is probably simply because the notification came at a bad time and the fan dismissed it. Now all past campaign notifications are available at anytime, right from the home screen.

Open

Review past notifications from the bell icon on top right, and especially organizers communications sent via campaigns

For more information see Past Notifications

DBV2.3

Data collection in more context

Do you need to capture information for every ticket in the app, but not the ticket holder name? For instance, request ticket holders to enter a licence plate number for a parking ticket? Now the ticket Assignment feature can be used for that use cases.

Open

Example of data collection for parking ticket

Miscellaneous

• On Android 14 and later, screenshot protection now uses the native Android protection and doesn’t requires anymore the permission to access local files. Note: as screenshots are blocked directly at Android level and not by the app, the app cannot record a mobile log at every blocked screenshot tentative.

• We continue improving the Curiosity layout and we are now displaying the main ticket metadata higher on the ticket, in a dedicated section just before the Purchase details.

• Manual activation codes can now be automatically randomized per event. When the organizer setting ‘Unique activation code per event' is enabled, a single unique code is generated for each event — regardless of how many activation rules are linked to it. This ensures every event has its own distinct code, simplifying management and improving security. See setting key Organizer Settings keys in TIXNGO V4

DBV2.2b

In this release, we are increasing the Backoffice security by allowing login to TIXNGO Backoffice using Corporate Single Sign On (SSO). In other words, your organizer account is now also your TIXNGO account !

Open

Corporate SSO login to TIXNGO Backoffice through your organization's unique Backoffice URL (e.g., https://your-org.backoffice.tixngo.io).

See Backoffice SSO for more details.

DBV2.2a

This is small release to push some surgical Backoffice improvements in our preparation for summer operations:

• Mobile logs search: we added the result count and the same pagination behavior as for the ticket list to allow quickly getting a sense of the volume and making review more efficient when troubleshooting.

• Global external wallet statistics have been added to the Event statistics screen to support monitoring and reporting. See Simple event statistics in Backoffice for more details.

We also introduced new parameters in our Reporting Domain event statistics endpoint to allow fetching all events starting in a date range at once. See Reporting endpoint - Event statistics for more details.

DBV2.1

Backoffice

Search tickets by initial owner

The global ticket list now allows searching all tickets that have been initially injected to a given spectator using the new Initial owner filter.

Open

Easily find tickets originally injected to someone

Number of tickets & pagination improvements

To better support B2B spectators with high number of tickets, the number of tickets is now displayed on the top right of the ticket list in the spectator support screen.

Open

Total number of tickets owned by the spectator in support screen

The pagination behavior of the ticket list has also been improved with:

• A clearer display, and a link to open the last page of the currently loaded results (max 1’000 at first load):

  Open

  

• Link to Load more results (the next 1’000) on the last page loaded

  Open

  

Refining user roles

The Backoffice user roles have been refined based on various feedbacks. In summary:

• The “BASIC” (BU) role has been tighten and can no longer modify tickets: no updates of tickets rules/metadata and no transfers from Backoffice.

• A new intermediate role named “ADVANCED” (AD) is introduced to extend the BASIC role by allowing transfers and spectator lock/unlock when needed, without giving the wider TIXNGO_SUPPORT or ADMIN permissions.

• The “MODERATOR” (MOD) has been tighten as well and now inherits from SUPPORT instead of BASIC: ticket updates, deletions or transfers are thus not allowed anymore.

Please refer to https://go.confluence.secutix.com/wiki/x/7IjSCg for more details.

Reporting

Performance improvements

We did some targeted performance improvements on the most data-intensive endpoints by introducing new parameters & dedicated endpoints to allow you to get only the amount of data you actually need for your analysis, saving both time and network usage.

In particular:

• The full ticket list can now also be accessed for multiple events at once, by providing a range of event start dates (all events starting from … to ….)

• We added a new tickets light endpoint that contains all tickets, but with only the common information useful to perform global analysis. Please use this endpoint by default and only the detailed one when absolutely necessary for your particular analysis.

• Support of incremental update (get only data added or updated in a given time period) has been added for:

  • Ticket list endpoints

  • Spectators

  • Devices

Please refer to V4 Reporting Domain for more details.

New Ticket Status Log endpoint

The ticket status logs are now available in the Reporting Domain, allowing you perform some thorough analysis on mobile user behavior and in particular on the complete transfer history of tickets.

Please refer to https://go.confluence.secutix.com/wiki/x/VYC6NQ for more details.

Other miscellaneous changes

• It’s now possible to target spectators in up to 3 events when creating a push

• When ownership transfer is used on a ticket in S-360, it will now be cancelled in TIXNGO with a specific reason called TRANSFER_OWNERSHIP, for clear history and proper listing in the mobile app.