Skip to main content

​
Overview

The configuration of an event in Vivenu is a critical task for FKL Operations. If events are configured incorrectly, various tools and platforms developed to support operations will break.
Even if events are subsequently corrected, any ticket sales that have already occurred will be incorrect — it is not possible to re-trigger sold tickets when making changes.
The following must be configured correctly:
  • Event naming convention
  • Event metadata
  • Ticket category naming convention
  • Ticket category pricing
  • Ticket category metadata

​
Creating the Event

1

Select the hub

Navigate to the Vivenu dashboard and select the hub you wish to create an event for.
2

Create a new event

Navigate to Events and click New event.
3

Populate the event details

On the sidebar, populate the following fields:
FieldValue
PhotoOne of the existing configured photos
TypeSingle event (most common)
NameTaken directly from the event creation request form
Time zoneSet this first — changing it after setting times will require the times to be re-entered
Event start07:00 on the day of the event
Event end18:00 on the day of the event
Location nameMust match exactly from the tracks database
Location streetMust match exactly from the tracks database
Location ZIP codeMust match exactly from the tracks database
Location cityMust match exactly from the tracks database
Location countryMust match exactly from the tracks database
Sales startCurrent day
Sales endDay of the event at 08:00
Maximum amount of tickets120
Maximum tickets per order120
4

Create the event

Click Create event.

​
Setting Event Information

1

Navigate to Information

Open the event and navigate to Information.
2

Add the event slogan

Copy the relevant event slogan from the Event Slogan for Vivenu Events page and paste it into the Event slogan field.
3

Add the event description

Copy the relevant event description from the Event Description for Vivenu Events page and paste it into the Description field.
4

Disable show start time

Disable the Show start time field.
5

Validate and save

Ensure all other details added during the Create stage are correct, then click Save.

​
Setting Event Metadata

1

Navigate to Metadata

Navigate to Custom and scroll to the bottom of the page to the Metadata section.
2

Add metadata fields

Click Add field and add the following keys. Note that all keys are case-sensitive.Type — set to one of the following values depending on the event:
  • Testing
  • Regional
  • Pro
IsChampionship — set to true.
IsChampionship is only required for Season Pass events.

​
Creating Ticket Categories

All tickets must have two metadata fields — eligibleClasses and eligibleParts — and both are case-sensitive. Pay careful attention when configuring these.
1

Add a new category

Navigate to Ticket categories and click More categories.
2

Set the category and ticket name

Under Category name and Ticket name, enter the name as defined in the specification sheet.
3

Set the volume

Under Category volume and Ticket type volume, enter the volume as defined in the specification sheet.
4

Set the price

Under Price, enter the price as defined in the specification sheet.
5

Set tickets per order

Set the maximum number of tickets per order to 1.
6

Open the ticket metadata

On the ticket card, click … to open the sidebar and scroll to the bottom to find the metadata section.
7

Add eligibleClasses

Add the eligibleClasses field. Where multiple classes are needed, separate them with a comma. Valid values are:BB, BR2R, CADL, CADH, CR2R, JRL, JRH, JR2R
8

Add eligibleParts

Add the eligibleParts field. Valid values are:D1/AM, D1/PM, D1/RACE, D1/RACE_AM, D1/RACE_PM, D2/AM, D2/PM, D2/RACE, D2/RACE_AM, D2/RACE_PM
9

Save

Click Save.

​
Checking Default Settings

1

Disable Show other events

Navigate to Display and disable Show other events.
If you do not want customers to see the event yet, you can also enable Hide under Display.
2

Clear the confirmation page URL

Navigate to Custom, then Order process, and ensure the Custom confirmation page URL field is empty.
Last modified on June 23, 2026