/
V4 Ticket Layout > Custom Flow

V4 Ticket Layout > Custom Flow

Why should you use it?

If the seating details sent by the ticketing system (e.g. S-360 physical configuration) are too different from what should be displayed on the ticket to guide properly the spectators onsite, then a Custom flow can be used.

We recommend to use the Custom flow as a last resort, for exotic or advanced situations, as this implies more complex and error prone setup during ticket injection.

In most cases, customizing the visibility and labels of seating details on the V4 Design rulesis sufficient to cover business requirement and much more simple to manage.

How does it work?

A new concept of Custom flow which defines how seating information is displayed to guide spectators in their journey onsite with full flexibility.

image-20251113-073422.png
Ticket’s Seating details box

Tickets injected to TIXNGO can define a navigation flow with full freedom in S-360 injection template.

  • Injected by S360

    • User can define the flow in the Integration Template when injecting tickets to TIXNGO by setting the variable TicketDetail.flow

    • Format:ticketDetails.flow.$index$.[key|value] = ‘Z1’

    • Example:

      • ticketDetails.flow.1.key = 'Zone' ticketDetails.flow.1.value = 'Z1'

Warning

Custom Flow does not support translations.

Use only key + value entries (e.g. ticketDetails.flow.$index$.[key|value]).

Do not inject translated flow entries (e.g. ticketDetails.flow.$index$.[key|lang|value]).

  • Injected by csv to TIXNGO

    • User can use this template to define the navigation flow in the column of ticketDetails.flow

    • Example:

      • Column title: ticketDetails.flow

      • Value: [{"key":"Room","value":"E1"},{"key":"Door","value":"E1"},{"key":"Zone","value":"Z1"},,{"key":"Floor","value":"F1"},{"key":"Column","value":"C1"},{"key":"Seat","value":"S1"}]

image-20251113-075744.png

This flow will be visible on Mobile and on Ticket support in Backoffice.

image-20251113-074039.png
On Backoffice-Ticket Support screen, user can click “View flow details” button to view the Custom Flow
image-20251113-074956.png
Mobile Ticket Details screen shows exactly like the defined Flow

Mobile now applies the organizer’s seating display configuration consistently across the app—on Ticket details, transfers, resale, deleted tickets, and any other screen where seating information appears—reducing confusion when spectators switch between screens.

The standard seating details remain visible where needed, as they uniquely identify the access given by the ticket—in particular:

  • in campaign notifications and email communications.

The standard seating details will still be passed automatically and stored separately on the ticket so it can be used for all filtering & searching in Backoffice and other special features (like warnings when tickets with different gates are kept on a same wallet for instance).

The labels & values will be displayed exactly like injected, without any translation and in the order provided.

NOTES:

This is the display priority used by the Mobile app: