Understand S-360 variables for tickets Injection

String

Unique identifier of the event

No

Yes

Set systematically by Injection Batch

No

String

Name of the Event

Yes

Yes

Set systematically by Injection Batch

Yes

String

Name of the site the Event will take place.

Yes

Yes

Set systematically by Injection Batch

Yes

String

City where the event takes place

No

Yes

Set systematically by Injection Batch

Yes

String

Country code for the Address

No

Yes

Set systematically by Injection Batch

Yes

String

Zip code where the Event takes place

No

Yes

Set systematically by Injection Batch

Yes

Date follows RFC 3339 standard

Time at which the event starts.

Date Format: 2022-12-12T16:11:00Z

Yes

Yes

Set systematically by Injection Batch

no

Date follows RFC 3339 standard

Time at which the event expire. Expired event cannot be used anymore.

No

Yes

Set systematically by Injection Batch

no

String

Website URL of the Event.

No

No

Set systematically by Injection Batch

Yes

List

Specific "key-value" fields provided to Organizer for special information about the event.
For now we handle the reserved keys below. You can override all those keys if you put them (same name, case sensitive) in the ticket details hidden section of the ticket.

 Resale

• RESALE_TICKETSHOP_URL: value = URL of ticket shop that use to resale a ticket (must include http or https)

• CANCEL_RESALE_TICKETSHOP_URL: value = URL of ticket shop that use to cancel a ticket (must include http or https)

Exchange

• EXCHANGE_TICKETSHOP_URL: value = URL of ticket shop that use to exchange a ticket (must include http or https)

Event schedule

• EVENT_SCHEDULE: value = List of JSON objects with the pair of Crowdin label and time

Detailed instructions on how to set up

add EVENT_SCHEDULE as an event metada key

Open

Put this JSON as a static value

[ { "label": "e_gateOpening", "time": "18:30" }, { "label": "e_ceremony", "time": "19:30" }, { "label": "e_startTime", "time": "19:45" }, { "label": "e_gateClosing", "time": "22:30" } ]

Open

You can adjust the time and remove unnecessary information if need

Current supported Crowdin labels for the event schedule: e_gateOpening, e_ceremony, e_startTime,

And make sure you have already provide the translation for these Crowndin labels, example:

Open

Event semantics Event semantics - MatchPreview

• Can be defined at TIXNGO Backoffice or can be injected from S-360 by defining a value for the following metadata: event_type, team_home_name, team_home_logo, team_away_name, team_away_logo, competition_name, competition_logo, event_number

Ticket Layout - Overriding at event-level V4 Ticket Layout - Overriding at event-levelPreview

• ticket_image_myticket: My Tickets screen

• ticket_image_thumbnail: Ticket screen Image

• ticket_image_fullsize: Ticket sreen Full-Size Image

• prohibited_items_image: Prohibited items Image URL

• prohibited_items_link: Prohibited items Redirect URL

• sponsorImage: Sponsors Image URL

• sponsorLink: Sponsors Redirect URL

• seat_map_image: Seat map Image URL

• seat_map_link: Seat map Redirect URL

• ticket_secure_backgroundcolor: Event-day secure display Background color

• ticket_secure_imag : Event-day secure display Image

• ticket_manual_activation_gs_footer_color: Footer color

• ticket_manual_activation_gs_footer_image: Footer image

Yes

No

Set systematically by Injection Batch

Yes

String

Unique identifier of this ticket in the organizer's ticketing system (typically technical ID)

No

Yes

Set systematically by Injection Batch

No

String

Business, human-readable, unique ticket identifier (i.e., tax number)

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

String

Barcode of the Ticket.

Yes

Yes

Set systematically by Injection Batch

No

String

Name of the activation rule to use for this ticket.

If no value is provided or no matching rule is found, the system will use the rule named 'DEFAULT'.

No

No

Yes

String

Name of the data collection rule to use for this ticket.

If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'

No

No

Yes

String

Name of the design rule to use for this ticket.

If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'

No

No

Yes

String

Name of the email rule to use for this ticket.

If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'

No

No

Yes

String

Name of the usage rule to use for this ticket.

If not provided or not matching a rule associated with the event, will use the one named 'DEFAULT'

No

No

Yes

String

Purchase reference number in the ticketing system.

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

date time - Date follows RFC 3339 standard

Purchase date and time

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

number

Price of the ticket

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

String

Currency following the ISO 4217 format

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

String

Unique identifier of the seat category corresponding to this ticket. This identifier should have a matching translation in the event metadata in order to be displayed properly on the mobile

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

String

Unique identifier of the contingent from which this ticket is coming. For reference and display in Backoffice only, this is not visible on the mobile ticket.

Yes

No

Set systematically by Injection Batch

No

String

Unique identifier of the tariff applied to this purchase.

Yes
(changeable)

Yes

Set systematically by Injection Batch

No

List

Free main ticket metadata "lang-key-value" fields display essential custom information in the first section.

V4 Ticket Layout > Classic | Ticket metadata displayPreview

Format: ticketDetails.main.$index$.[lang|key|value] = ‘xyz’
Example:

Yes
(changeable)

No

No

Yes

List

Free ticket metadata "key-value" fields display less important custom information in a dedicated "More info" section at the bottom of the ticket, just above the sponsors' footer.

V4 Ticket Layout > Classic | Ticket metadata displayPreview

Format: ticketDetails.main.$index$.[lang|key|value] = ‘xyz’

Yes

No

No

Yes

List

Free "key-value" fields are used for specific per-ticket customization. For more details, visit Introduction to V4 Design rules | Specific per ticket customizationPreview.

Keys:

• hosp_room: Optional field set by the Organizer at injection to define the hospitality room for the ticket.

• show_price: Optional field set by the Organizer at injection to indicate whether to display the price on purchase details.

• at_icon: Optional field set by the Organizer at injection to show an extra icon in the top-left corner of the ticket layout.

You can also visit this page to understand how to set up the Multingual for ticket metadataPreview

-

No

No

Yes

Navigation flow with "key-value" fields to display custom information in the “box” section instead of the Seating Details when presented

For more details, visit V4 Ticket Layout > Custom FlowPreview

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

Boolean

Set to true if the seating details below are available and can be displayed to the spectator on the ticket.

Set to false for cases like parking tickets for instance.

No

Yes

Set systematically by Injection Batch

Yes

Boolean

True when the ticket gives access to a numbered seat.

No

Yes

Set systematically by Injection Batch

Yes

String

Area to which the ticket gives access.

Condition: This field is required if value of seatingDetails.seated is true

Yes
(changeable)

Condition

Set systematically by Injection Batch

Yes

String

Level to which the ticket gives access.

Yes
(changeable)

No

Set systematically by Injection Batch

Yes