2026 Dent Blanche V2

2026 Dent Blanche V2

Objectives & high level scope

The objectives of this release are:

  • Last minute adjustments before the major summer events

  • Boost notifications in TIXNGO

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

Boost notifications

Live notifications on event day

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.

 

PRE-PROD

PROD

DBV2.1

29.04 + 05.05

07.05

DBV2.2a

12.05

14.05 (only on p26)

DBV2.2b1

13.05

19.05

DBV2.3

27.05

02.06

DBV2.4

10.06

16.06

DBV2.5

24.06

30.06

DBV2.6

08.07

14.07

1 For slots 5 & 25, 2.2a&b will be deployed in the same time.

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

Detailed release notes

Here will be unveiled, one increment at a time, the new features available in the next deployment.

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 !

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

See https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/1022427145 for more details.

DBV2.2a

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

We also introduced new parameters in our Reporting Domain event statistics endpoint to allow fetching all events starting i a date range at once. See https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/269221978 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.

image-20260505-082411.png
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.

image-20260504-070911.png
Total number of tickets owned by the spectator in support screen

The number of tickets takes into account the filters on statuses on the left, as well as show past events option.

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):

    image-20260504-074353.png
  • Link to Load more results (the next 1’000) on the last page loaded

    image-20260504-074455.png

Note that only 5’000 tickets can be loaded like that in BackOffice (in other words 100 pages!). Please use the https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/235210405 when you need more than that.

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 https://go.confluence.secutix.com/wiki/spaces/TIXNGO/pages/235210405 for more details.

Please leverage incremental update in your API integration with your Data platform. For Power BI users, pleasehttps://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview. This will save you a great amount of time to fetch the latest data.

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 notification campaign from the Back Office.

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