With Inventory-Based Actions, you can automate changes to your ticketing page based on how many tickets are left for your event. You can create inventory-based actions for your entire event, or a specific ticket level. Whether you're increasing the price of your event when there are less than 100 spots less or hiding options as availability decreases, these actions give you control over the ticketing experience.

For example, you can automatically hide a merchandise item when your General ticket level sells out, or increase the price for your event when there are less than 20 tickets left. These actions help streamline your workflow and ensure your page stays accurate and up to date.

Note: For Reserved Seating pages, actions can be used to target fields outside of the Reserved Seating venue, but cannot be used to target the venue itself. This means you currently cannot use actions to change the price of Reserved Seating tickets, adjust the venue based on date triggers, or dynamically modify seat inventory.

You can use actions to target fields outside the venue, such as showing or hiding merchandise options, applying discounts to add-ons, or displaying custom questions.

Example Use Cases

When the inventory of your event drops below 30 tickets, increase the price for your event by $10
When your General ticket level sells out, hide one of your add-on experiences

Getting Started

From the Pages screen, click the pencil icon under the page you want to edit
Go to the Actions tab
Click Create Your First Action, or click the + icon on your action if you already have actions on your page

Add Your Trigger

In TicketSpice, you can create actions that trigger based on your event’s inventory. These actions can be tied to the overall event inventory or to a specific ticket level's inventory.

Add a Trigger That Targets Inventory for Your Entire Event

On the left-hand side, select Tickets from the dropdown
Select your desired option, and add a value/quantity to the field below if needed
- The Remaining Inventory Is option triggers your action when the total remaining ticket inventory for your event reaches the amount you specify
- The Inventory Sold Out option triggers your action when all tickets for your event have been sold
Click the + button if you would like to add multiple triggers
- If you click this button, click the All of these must be true checkbox if you would like all of the conditions to be met to trigger your action
- If this checkbox is not selected, the action will occur if any one of the conditions is met

Add a Trigger That Targets Inventory for a Specific Ticket Level

On the left-hand side, select the ticket level you would like to target from the dropdown
Select your desired option, and add a value/quantity to the field below if needed
- The Remaining Inventory Is option will trigger your action when the ticket level's remaining inventory reaches the values you set
- The Inventory Sold Out option will trigger your action when the ticket level is sold out
Click the + button if you would like to add multiple triggers
- If you click this button, click the All of these must be true checkbox if you would like all of the conditions to be met to trigger your action
- If this checkbox is not selected, the action will occur if any one of the conditions is met

Add Your Action

You can create a variety of actions in TicketSpice that are triggered by the inventory of your event or ticket level. Below are some of the action types you can set up to customize the ticketing experience.

Pro Tip: It is important to know that actions run from top to bottom. So if you have multiple actions in your TicketSpice page, actions towards the bottom can override actions above them. You have full control over the order of your actions and can reorder as needed. Because the order of actions can impact how your page behaves, we highly recommend previewing and testing your page before publishing it live. This helps ensure that all your actions work together the way you intend.

Show-Hide Actions

In TicketSpice, you can dynamically show or hide fields based on the inventory of your event or ticket level. For example, you can automatically show a specific merchandise option when your inventory drops below 100 spots.

Pro Tip: Our actions automatically assume the opposite is true. For example, if a field is set to only show based on a certain condition, it will be hidden by default until that condition is met. Once the condition is met, the field will show.

Likewise, if a field is set to hide until a condition is met, it will by default show. For instance, if a text field is set to hide when your inventory is between 100 and 300 tickets, the field will by default be shown until that inventory range is reached.

By default, TicketSpice fields show all of the time, so if you would like to show your field at all times, no action is needed.

On the right-hand side, find and select Show or Hide
Choose the Field(s) or Function(s) that you would like to show or hide when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Require/Don't Require Field Actions

In TicketSpice, you can dynamically require or not require fields based on the inventory of your event or ticket level. For example, you can automatically require a require a specific merchandise field to be completed when your General admission tickets are sold out.

Pro Tip: Actions will override the default requirement settings you set on the page builder. Actions also automatically assume the inverse is true. For example, if you create an action to require a field based on a certain condition, this field will not be required by default, even if it is marked as required in the Page Builder settings. This field will only become required once the condition is met.

For example, if your meal choice field is required in the page builder, but you create an action to require this field when your inventory is above 400 tickets, our system will automatically make the meal choice field not required when the inventory is below 400 tickets. Even though the Page Builder has marked this field as required, the action takes precedence. While the inventory is above 400 tickets, the field will be required.

If you want a field to always be required (or not required), no action is necessary. In this case, we recommend adjusting the Required setting within the Page Builder itself.

On the right-hand side, find and select Require or Not Require
Choose the Field(s) or Function(s) that you would like to require/not require when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Select an Option Actions

In TicketSpice, you can dynamically select an option based on the inventory of your event or ticket level. For example, you can automatically select a specific multiple choice option when your inventory is below 100 tickets.

Pro Tip: Select an Option actions will only take place when the condition event is met. If the condition event is not met, the Select an Option action will not take place. For example, if you create an action to select two specific sessions when your VIP inventory is above 10 tickets, the session field will remain unselected by default once the inventory drops below 10 tickets. While the inventory remains above 10 tickets, the required sessions will be automatically checked.

On the right-hand side, find and select Select Option
Choose the Field(s) that you would like to target when the condition is met
Click Lock Selection if you would like to prevent attendees from changing their option
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Note: Select an Option actions works with time slots (on date-based pages), Sessions, and Multiple Choice actions. This action does not work with checkboxes and merchandise fields. If you do not have a date-based page with time slots, a Sessions field, or a Multiple Choice field on your TicketSpice page, the Select an Option action will not appear in your list of events.

Set Value Actions

In TicketSpice, you can dynamically set a value in a text field based on the inventory of your event or ticket level. For example, you can automatically set the value of a text field to “N/A” when your event has between 100-200 remaining tickets.

Pro Tip: Set a Value actions will only take place when the condition event is met. If the condition event is not met, the Set a Value action will not take place. For example, if you create an action to set the value of your text field to "N/A" when your inventory is below 100 tickets, the text field will be blank until that inventory range is met. Once your event has less than 100 remaining tickets, the text field will automatically be filled in with the text "N/A."

On the right-hand side, find and select Set Value
Enter the value you would like to enter in the text field
Choose the Field(s) that you would like to target when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Note: Set a Value actions are designed to insert text into text-based fields and are not intended for adding financial amounts to pricing fields. If your page doesn’t include any text-entry fields, the Set Value action won’t show up in your list of available events.

Price Change Actions

In TicketSpice, you can dynamically update the price based on the inventory of your event or ticket level. For example, you can automatically apply a 20% discount on your tickets when your inventory is above 500 tickets.

Pro Tip: Price change actions will change the price only when the condition event is met. If the condition (aka trigger) is not met, the price change actions will not take place. For example, if you create an action to raise the price of your merchandise from $10 to $15 when your event drops below 20 tickets, the price of the t-shirt will remain $10 until that inventory range is met. Once your event has less than 20 available tickets, the price will then automatically change to $15.

Note: Price change actions affect each ticket or item, not the total order amount. If you're using these actions, it's important to set up your price change action with the understanding that the discount or increase will apply to every ticket or item on the order.

For example, if you set a $10 discount on your VIP ticket level when the event has over 30 tickets left, and someone purchases two VIP tickets for attendees when the inventory is above that range, the total discount on the order will be $20. The $10 discount will be applied to each ticket.

On the right-hand side, select your price change action
- Set Price will set the price of the field(s) to a new value that you set. If this option is selected, set the price in the text field
- Increase Price will increase the price of the field(s) by a $ or % amount that you set. If this option is selected, choose whether you would like to adjust the price by $ or %, and enter the value increase in the text field
- Decrease Price will decrease the price of the field(s) by a $ or % amount that you set. If this option is selected, choose whether you would like to adjust the price by $ or %, and enter the value decrease in the text field
- Apply Discount will apply a discount on the field(s) by a $ or % amount that you set. If this option is selected, choose whether you would like to adjust the price by $ or %, and enter the discount in the text field
- Limit Discount will limit the discount on a field(s) to a certain number on merchandise fields. If this option is selected, choose the limit of the discount in the text box that appears
- Set Fee will change the fee on your ticket level(s) to the new amount you enter. If you choose this option, enter the desired fee in the text field on the right. This will override the default fee set in the page builder
- Multiply Coupon increases the value of a coupon by the multiplier you set. This action multiplies the coupon's value when someone enters a valid coupon and meets the trigger condition. If this option is selected, set the multiplier in the text field that appears on the right
Choose the Field(s) on which you would like to adjust the price when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Note: This Limit Discount applies to ticket levels, merchandise fields, and quantity boxes, not multiple choice fields and donation fields.

Users must use the Apply Discount action for the Limit Discount action to work. If users do not use the Apply Discount action, the Limit Discount action will not apply.

Users must add the Apply Discount event and the Limit Discount event within the same action by clicking the + button on the right-hand side of the action. If users create two separate actions (even if they use the same trigger), the Limit Discount field will not apply.

Capacity Limit Actions

In TicketSpice, you can dynamically adjust the overall capacity of your event based on the inventory of your event or ticket level. For example, you can decrease the capacity from 500 to 400 when the inventory of your General ticket level drops below 50 tickets.

Pro Tip: Capacity actions override the default capacity settings configured in the page builder. These capacity actions only take effect when the condition event is met. If the condition isn't met, the Capacity Limit action won't apply. For example, if you create an action to set the capacity to 500 when your VIP ticket level inventory is under 10, that limit will only apply when the inventory drops below that limit. If the VIP ticket level has over 10 available tickets, the event will have the standard capacity set in the page builder.

If you want the same capacity to apply in all situations, no action is necessary. In this case, we recommend setting the capacity directly in the page builder.

Note: You can only use actions to lower the capacity below the default set in the page builder. If you need the capacity to be higher in certain situations, we recommend increasing the overall default capacity and then using actions to reduce the limit in all other cases.

On the right-hand side, find and select Set Capacity Limit from the dropdown
Enter the new capacity limit for your event in the text field on the right
Select the Tickets option from the dropdown
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Ticket Limit Actions

In TicketSpice, you can dynamically adjust the maximum number of tickets a buyer can purchase in a single order based on the inventory of your event or ticket level. For example, you can change the maximum number of tickets allowed per order from 5 to 3 when the inventory drops below 50 tickets.

Pro Tip: Set Tickets Per Order actions override the default ticket limit settings you set on the page builder. Additionally, actions will only take place when the condition event is met. If the condition event is not met, the Set Tickets Per Order actions will not take place. For example, if you create an action to allow buyers to purchase up to 5 tickets when the inventory is above 100 tickets, this limit will only take place while the inventory of your event is above 100 tickets.

If you want to set the same ticket limit in all circumstances, no action is necessary. In this case, we recommend setting this limit in the page builder itself.

On the right-hand side, select Set Tickets Per Order from the dropdown
Enter the maximum number of tickets allowed per order in the text field on the right
Select the Tickets field from the dropdown
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Manage Your Actions

Find the Action you would like to manage, and click any of the following icons:

The pencil icon allows you to edit the action
The pages icon allows you to copy the action
The + icon allows you to create a new action
The trash can icon allows you to delete the action

FAQs

What's the best way to test my actions?

We recommend using Preview mode to test your actions. Preview Mode allows you to review the visual and communication experience of your event page without processing real payments or saving data. Since Preview Mode respects actions and date-based conditions, you can test your page in real time to ensure everything functions as expected.

To use Preview mode, go to your TicketSpice edit page
Save any changes on your page by clicking Save in the top-right corner
Select the Preview button in the top right corner

Warning: Because the Preview mode is only used for testing, do not share this URL with attendees. This link will not accept real orders or payments.

Why is my live page still showing pre-registration, offline payments, or credit card payment options when I've disabled these payment methods on my TicketSpice page?

A common reason a disabled payment method still appears on the live page is that there is an action on the page that references that payment method. Actions override the payment settings in the page builder. So, if an actions includes a reference to a payment method, it will appear on the live page — even if that method is turned off in your settings.

To fix this, review your actions and remove any references to the payment method you no longer want to offer.

Create Date-based Actions That Trigger Based on the Current Date or the Event Date

Create Actions That Trigger Based on the Attendee's Email or other Text Inputs

Create Actions that Trigger Based on the Attendee's Date of Birth

Create Actions that Trigger Based on the Date or Time Your Attendee Goes to Your Event

Create Actions that Trigger Based on the Ticket Level an Attendee Selects

Create Actions that Trigger Based on the Inventory Left for Your Event