Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Organizers currently handle ticket exchanges outside of TIXNGO, relying on the S-360 back-office and ticketshop, which results in a manual and fragmented process. To streamline on-site operations, enhance the user experience, and provide spectators with more flexibility and autonomy, we’re integrating this functionality into TIXNGO. This enhancement will not only simplify management but also unlock new revenue opportunities.

...

Enable the S-360 Ticket Exchange feature from the organizer settings

From the Application Settings, enable the feature Ticket exchange via S-360 ticketshop (key: ticket.s360.ticketshop.exchange)

...

Redirection to the ticketshop

Event configuration at injection

By default, the S-360 Ticketshop Exchange URL specified at the event level will be used to redirect spectators to the ticketshop.

Ticket override at injection

However, you can override this URL on a per-ticket basis by modifying the S-360 injection template and utilizing hidden ticket details metadata. 
To set this up, apply the following configuration in your S-360 injection template:


Info

TIXNGO differentiates how URLs are managed based on their entry points: ticketDetails.hidden and event.metadata.

  • When both fields are available, ticketDetails.hidden takes precedence.
  • Using event.metadata applies URLs uniformly to all tickets of an event and allows for easy updates via the "Edit Event" screen under the "S-360 Integration" tab.
  • Conversely, ticketDetails.hidden is ideal for assigning distinct URLs to different ticket categories, types, locations, or currencies. However, since it operates at the ticket level, bulk updates across all tickets are not feasible.

Limitations

Spectator must be the ticket S-360 Cultural Contact to perform a Ticket Exchange

...