Note: This entity can be customized to fit bespoke needs. The fields described in this article may not coincide with the ones in your FORGE instance.
Where do I find Tickets?
In the menu on the left, select the Tickets icon:
Note: The Tickets icon can be in a different place because of the custom entities in your FORGE instance.
Managing the Ticket entity
When creating and managing a Ticket entity, the entity-specific fields are:
Competition name: The official title of the tournament or league in which the event takes place.
Kick-off date and time: The scheduled starting date and time of the sports event.
Home team: The name of the team hosting the match or event.
Home team Triletter: A three-letter abbreviation used to represent the home team (e.g., "ARS" for Arsenal).
Home Club badge from GAD: Official home team badge sourced from the Graphic Asset Dashboard (GAD) for branding use.
Away team: The name of the team visiting or playing away in the event.
Away team Triletter: A three-letter abbreviation representing the away team.
Away Club badge from GAD: Official away team badge retrieved from the Graphic Asset Dashboard (GAD).
Pack name: The branded or commercial name of the ticket bundle or access offer.
Pack type: The classification of the pack (e.g., single-match, season ticket, hospitality).
Pack content: A summary of what's included in the ticket pack (e.g., seats, perks, matches).
CTA Link Display Text: The visible label prompting users to take action (e.g., "Buy Now").
CTA Accessible Text: Screen-reader-friendly text describing the action of the main CTA link.
CTA URL: The link users follow when clicking the promotional call to action.
Ticket CTA Link Display Text: Specific label for the ticketing action (e.g., "Get Tickets", "Reserve Seat").
Ticket CTA Accessible Text: Text for assistive technologies describing the purpose of the ticket CTA.
Ticket CTA URL: Direct link to the ticket purchasing or reservation page.
By scrolling down, the other fields display:
Translations
Ticket entities follow the language-independent workflow. The entity fields and publishing status can be different for each language.
For example, a Ticket can have different field values for the English UK language and for the French language. Also, the English UK Ticket can be published while the French one is unpublished.