Create/Edit an Event

From the Nliven admin home page, click on the "Events" tab in the left-hand navigation menu. Click "Event List."

To create a new event: First, ensure the corresponding Event Template has been created. Then on the main “Events List” page, click the Actions dropdown button and then "+ Create New Event" on the top right-hand side of the page.

The “Create Event” Screen will appear. Fill in the fields below.

Basic Info

• Name: Enter an event “Name”. This will display on the customer Basket Page, in all customer email communications, & on the PDF ticket.
• Alternate Name: This is optional and will display below Event Name in the calendar view on the "Sell Tickets" tab or consumer purchase flow.
• Description: This is optional.
• Event Alert Override: This option can be used to display an Event specific message within the consumer purchase flow. When entered here, this message will override the Event Template Alert message (if one is configured, further details provided in Edit Event Template - Settings Tab page) on both the seat map and basket pages. Once text is entered in this field, a “Required Acknowledgement” check box will display.  Checking this box will require the consumer to acknowledge the message before they can complete the checkout process.

• Event Template: Here you select the corresponding Event Template that you will be pulling all your pricing, holds, etc. information from for this performance/event.
• External Event ID: Utilized only when interacting with TixTrack Professional or external ticketing systems via API integrations.
• Heavy on Sale Mode: This sets the event so that the ticket buyer can only select the amount of tickets they require and a maximum price. The system will display what is available. This stops inventory being held in inquiry while customers browse seat maps. This is used for events that expect a large number of clients to attempt to purchase tickets during an on sale. 
• Single Seats Policy: Checking this box will turn on the Single Seats Policy for this event. See the Single Seats Policy section below for more details.

Dates

• Event Date: The start date and start time of the event.
• Event End Date: The end date and end time of the event.
• Publish Date: This is the date you want to publish the event for sale.
• Web On Sale Start Date: The start date and time for the event to be on sale for Web sales.
• Web On Sale End Date: The end date and time for the performance to be off sale for Web sales.
• Box Office on Sale Date: This is the time and date you would like Box Office User Roles to see the event and be able to sell.  Configuring this field to be a date prior to the event on sale date will allow Admin and Event Admin Users only to test via Point of Sale ("Sell Tickets") for Events that are not yet on sale.

All Sales Channel fields below will auto-fill based on the Web On Sale and End Dates if they are left blank:

• • House Seat Requests start and end date
  • Group Sales start and end date
  • API On Sale start and end date
  • Call Center On Sale start and end date
  • Outlet On Sale start and end date
  • Admin Off Sale Date: This is the time when Admins will no longer be able to sell tickets, configure holds, or make any other changes to the event. The date must be equal to or later than the Event End Date.

• Lock Date (local venue time): This is the date and time after which it will not be possible to edit, cancel, or refund orders for the event. The date can be set at an individual event level or applied to multiple events through the bulk edit tool, and can be edited after the initial Lock Date has passed if you need to unlock the event.
• Pre Event Email Date (UTC)", and "Post Event Email Date (UTC): If this event has a different pre and post email rule than the Event Template, the event-specific email notification dates must be filled in here. Visit Event Template → "Settings" tab → "Options” to see Pre and Post Email dates assigned to an Event Template. Configuration details are provided on the Edit Event Template - Settings page.

Top Tip : To utilize presale functionality (set up at the Event Template → "Pricing" tab → "Promos", further details provided in Create/Edit Promos → Presale Configuration section of page), the Publish Date must be set before the On Sale Date (Note: The Publish Date is only applicable to web sales). 

Tickets

• Max Tickets per Order (Override): This setting is optional. This setting, like the parent setting on the event template, is only enforced for Web orders. This field can be edited in bulk using the bulk edit events tool (example below), the parameter is labeled “Order Ticket Limit.”
• Hard Ticket Event Name Line 1: This will be used instead of the information entered in the event "Name" field above.
• Hard Ticket Event Name Line 2: This will be used instead of the information entered in the event "Name" field above.
• Ticket Text 1-3: This text will be added to the ticket. The character limit is 55 characters per line.

Once you have edited all desired fields, scroll to the top of the screen and click the blue “Save New Event” button.

Activate an Event

Activate an Event: Before an event can be made active, seats must be generated and the desired map must be chosen (created in the Event Template "Maps" tab. For further details visit the Create/Edit Price, Hold, Accessible, Tag, or Seat Alert Maps in an Event Template page). Click the “Generate Seats” button at the top of the page.

The Generate Tickets box will appear. Select the correct seating Map for the event/performance. Default Map will likely be the only option. Click the blue “Submit” button.

Once the seats have been generated, click the Edit button on the top right and then check the "Active" box to publish the event to the Tickets Pages. Click the blue "Save" button.

Edit an Existing Event

To edit an existing event, click on the event name on the Event List information screen. A new screen will populate.
Click on the blue "Edit Event" link under the Event Name.

Single Seats Policy

The "Do Not Leave Single Seats" feature limits users from unnecessarily leaving single seats when they are selling from or buying from the seat map. Check the box if you DO NOT want users to leave single seats.

This feature is enforced for Web, Outlet, and API channels. The error message that is returned back when a customer tries to purchase a seat that would violate the rule is "Unfortunately, the seats you've chosen leave a single seat. Please select different seats."

Top Tip : The goal is to reduce the number of unnecessary single seats created in the venue, while also balancing the need to provide a pleasant user experience for the guest. NOT to eliminate single seats.

Examples:

• For a row with three seats, a user would be prohibited from buying the middle seat.

• For a row with several open seats, a user would be prohibited from buying a seat and leaving a single on one aisle.

• For a row with two seats, the user CAN buy one of the seats, leaving a single in the row on the aisle.

• "Heavy On Sale Mode" does not use this logic. Some single seats will inevitably be created.

Top Tip : The majority of fields configured for an event can be edited after an event has been created, either individually (by clicking on the event name in the Event List → "Edit Event") or in bulk at the "Events" → "Event Templates" tab. Further details are provided on the Bulk Edit Events page.