Introduction to V4 Design rules

One Design to Rule them all!

Ticket customizability has always been challenging due to the scattered configuration—some elements at the Event and Event Group levels, others within Design Groups, and even more hidden in ticket’s key-value pairs.

We’ve completely reimagined our ticket design approach by consolidating everything into the new Design Rules. All colors, pictures, assets, and links that influence the ticket’s look and feel on mobile are now grouped in one place.

Basics: QR Code Size, Ticket Layout (Classic & Curiosity)
Default colors: Background, Vertical & Horizontal stripes
Images (URL): My tickets, Thumbnail & Full Size
Event-day unique display: Background color & Image
Other design assets: Prohibited items, SeatMap, Sponsors
Ticket Check > Successful check screFooter color & image

New Design Rule

Ticket fields visibility customization

The field to display on the ticket can be finely selected in the ticket design rule, provided the data are available on the ticket of course.

Tick in the checkbox to display the field on Mobile Ticket Details screen

This is particularly useful to hide some data injected by default by S-360 when they are not useful for spectators. For instance, External entrance if there is only one in the venue, or Purchase date for sponsors tickets.

Seating details labels customization

In addition, the crowdin label used for any given seating details field can be customized if needed by providing an alternative crowdin label key for the corresponding fields.

This allows covering the frequent scenario where one field in S-360 physical configuration represents something else in the venue, for instance the block is actually a skybox or suite for the VIP tickets.

Input the new crowdin label keys to override the default Seating Details label

Please contact your CSM for assistance in adding custom Crowdin label keys if your application supports multiple languages.

If (and only if) your application is supporting only one language, you can alternatively directly enter the value to display in this field, but be aware that the application will still look for a crowdin label with this key.

Specific per-ticket customization

Independently of the design rule, some details of the ticket design can be customized using special hidden ticket metadata.

Hospitality room information

Set the hosp_room ticket hidden metadata to the value to display between the seating details and main ticket properties (VIP1 in this example).

Special access icon

Set the at_icon ticket hidden metadata to the URL of the small image to display at the top left of the ticket. Use a small square image that will fit nicely in the circle (color part of the app theme).