Use Cases
Use CasesSeason Tickets with Purchase Intents
Purchase Intents provide an optimal solution for addressing Season Tickets use cases. Especially during the season transition, they allow the import of season tickets into the system to provide customers with a payment link. This link allows customers to actively initiate payment and secure their season ticket for the upcoming season. By setting a reservation time, it ensures that seats are automatically released if season ticket reservations are not completed in time.
Note: To create season tickets in the system, the season ticket event must be created first.
1 Set Up a Strategy
In the first step, create a Purchase Intent strategy to define what this season ticket reservation means and what rules are behind it. It is recommended to create a new strategy for each season to maintain previous settings and to be able to capture changes flexibly in a new strategy.
Navigate to the Purchase Intents module and select Strategies to open the settings.
Click on Create in the top right corner to generate a new strategy and give it a name (e.g., "Season 2024-2025" or "Season 24 | VIP").
Click on the newly created strategy and choose Edit to make adjustments.
Leave Required Admission disabled. Use this function if you want to activate reservations only after creation, before a customer completes payment.
Enable Create Tickets to generate a ticket with the reserved status, blocking the seat directly.
Enable Check Availability to consider your stored ticket and event quotas and prevent overbooking the event.
Specify the desired Reservation Validity. After this period expires, the Purchase Intent will be automatically canceled, and the seats will be released. Validities can be adjusted for individual Purchase Intents at any time.
Disable Create Valid Tickets to ensure that customers must complete payment before receiving the tickets.
Disable Without Seat to directly block the associated seats for customers. Even if you only use GA sections, this function should remain deactivated.
Click Save to apply the changes.
After creating the Purchase Intent strategy, link it to your season ticket event to capture the settings for all Purchase Intents created for this event. Follow these steps:
Go to the Events module and select the specific season ticket event.
Navigate to the Sales tab in the event settings.
Scroll down to the Reservations section.
Activate through the top drop-down menu what type of reservations you want to allow. Choose Internal Reservations & Payment Possible to ensure that only you can internally create season ticket reservations.
Click Save.
2 Create Import File
To import all season ticket reservations in bulk, generate an import file with all the necessary information. There are two different ways to create this import file:
1. Importing Season Tickets from the vivenu System
If you want to import season tickets that were already stored in the vivenu System from the previous season, you can easily retrieve them through a Ticket Export from the system. Subsequently, you only need to update the new Event ID and Ticket Type ID, and the file is ready for a reimport into the new season. Follow these steps to export tickets from the old season in the first step:
Go to the Tickets module to perform the export of season tickets from the old season.
Choose Export in the upper right corner.
Select the desired season ticket event from which the tickets should be used.
Leave the options for date and time blank.
Activate seat to also export seating information.
Click on Export. You will be automatically redirected to the Jobs module, where you can download your export.
Go to the three dots under Output to download your new export. Choose the desired file format; we recommend the .xlsx format as the file still needs to be edited.
How to Adjust the Export File for Import
Open the export file in Excel.
Delete all columns except the following: customerId, ticketName, category, price, deliveryType, seat.section, seat.group, seat.row, seat.seat, seat.general_admission.
Additionally, create the following columns: eventId, ticketTypeId.
In the new eventId column, enter the ID of the event to which you want to import the season tickets. The ID is a numerical combination that you can obtain from the URL in the event settings.
In the new ticketTypeId column, enter the ID of the ticket type to be used for creating the season tickets. You can find the Ticket Type ID in the event settings under the Ticket Categories tab, right next to the names of the ticket types. Use the exported columns ticketName, category, and price to make the associations.
Check the deliveryType column. Specify "VIRTUAL" for all tickets that should only be generated online as P@H or Wallet Tickets. Specify "HARD" for all tickets that should be printed.
Rename the seat columns as follows: "seat.section" to "sectionName," "seat.group" to "groupName," "seat.row" to "rowName," "seat.seat" to "seatName," "seat.general_admission" to "gaName."
If you have both GA tickets and seated tickets, these tickets must be split into two separate import files. This is because the system requires a value in each column for each ticket. If you were to import them all at once, you would encounter an error because the GA column for seated tickets is left unfilled, and vice versa.
Double-check all data.
Export your file as a CSV.
2. Importing Season Tickets from Another System
If you want to import season tickets from an external system, you need to export them from that system first to prepare the import file. Since a Purchase Intent Import is created based on customer IDs in the vivenu system, your customers must be imported into the vivenu system first to generate customer IDs.
Refer to the article on Data Migration for more information.
3 Perform the Import
To carry out a Purchase Intent Import, follow these steps. Navigate to the Purchase Intents module and select the "Import" button. Alternatively, the import can also be initiated through the same process in the Jobs module.
Click on the Import button in the Purchase Intents module. A new window will open.
Choose the Select button to upload the import file. Subsequently, additional settings will unfold.
Decide whether you want to send the reservation directly via email. Through this email, customers will have the opportunity to finalize the reservation and receive the tickets.
Link the fields of your CSV file with the internal fields. If the fields in your CSV are already named in the same way, the mapping will be done automatically.
Click on Import to initiate the import. You will be automatically redirected to the Jobs module.
Was this page helpful?
For the sake of better readability, the simultaneous use of the language forms male, female and diverse (m/f/d) is waived. All personal designations apply equally to all genders.