With Date-Based Actions, you can automate changes to your ticketing page based on the current date or event date without manually updating your page. Whether you're managing early bird pricing, unveiling VIP upgrades, or phasing out certain options over time, these actions give you full control over the ticketing experience from start to finish.

For example, you can offer a 10% discount to individuals who purchase tickets before July 15 or show a unique merchandise option to ticket buyers who attend your events between October 1 and October 31. By using Date-Based Actions, you can streamline your workflow, ensure timely communication, and create a more dynamic ticketing journey for your attendees.

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

After January 31, increase the price for your tickets by $5
On October 31, hide a paragraph text field
For ticket buyers who attend your events between between June 1 and June 15, don't require a specific merchandise field is otherwise required
For ticket buyers who attend your events between before July 22, decrease the price for your merchandise by 10%

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 Date-Based Trigger

In TicketSpice, you can create actions that trigger based on the current date or event date. For example, you can lower your event's capacity if the date is after January 31, and show a unique Merchandise item for your events that take place between January 1 and June 1.

Note: TicketSpice offers several types of date-based actions, each tailored to target different kinds of dates. Below are common scenarios where you might want to use a date-based action, along with instructions on how to set them up:

Trigger an action based on the current date. We recommend using the Date trigger to trigger an action based on the current date when a ticket buyer purchases tickets.
Trigger an action based on the date a ticket buyer chooses to attend your event (available on date-based pages only). We recommend selecting the Ticket Date Selection to trigger an action based on the specific event date(s) a buyer selects.

Add a Trigger Based on the Current Date

You can use TicketSpice to set up actions that trigger based on the current date at the time the attendee is purchasing tickets for your event.

Pro Tip: When using the Date trigger, the action is triggered by the current date when the ticket buyer signs up for your event. If you edit the order after the action date has passed, the action will still apply as long as the ticket buyer originally purchased tickets before that date.

For example, if you choose to hide a field for orders that are completed before March 1, this field will remain hidden for an order that signed up on February 27, even if you edit their order on May 1.

On the left-hand side, select Date from the dropdown
Select one of the following options and add the desired date and time
- The Is option will trigger your action on a specific date
- The Is Between option will trigger your action between specific dates
- The Is Before option will trigger your action before a specific date
- The Is After option will trigger your action after a specific date
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 are met

Add a Trigger Based on the Date a Ticket Buyer Chooses to Attend Your Event (Date-Based Events Only)

You can use TicketSpice to set up actions that trigger based on the date your ticket buyer chooses to attend your event. This trigger is only available for date-based events.

On the left-hand side, select Ticket Date Selection from the dropdown
Select your desired option, and add a value/quantity to the field below if needed
- The Is Completed option will trigger your action when an attendee selects any date
- The Is Not Completed option will trigger your action when an attendee doesn't select a date
- The Date is Before option will trigger your action when an attendee chooses to attend your event before the specific date you set
- The Date is After option will trigger your action when an attendee chooses to attend your event after the specific date you set
- The Date Is option will trigger your action when an attendee chooses to attend your event on the specific date you set
- The Day of the Week option will trigger your action when an attendee chooses to attend your event on a day of the week you specify
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 current date or event date. 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 current date or event date. For example, you can automatically show a specific ticket level before January 30.

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 merchandise field is configured to hide after June 15, this merchandise field will initially appear on the page. After June 15, the field will then be hidden.

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 current date or event date. For example, you can automatically require a specific merchandise field to be completed after December 13.

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 after December 18 at 2:00PM, our system will automatically make the meal choice field not required until December 18 at 2:01PM. Even though the Page Builder has marked this field as required, the action takes precedence. After December 18 at 2:00PM, the field will then become 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 current date or event date. For example, you can automatically select a specific multiple choice option on October 11.

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 on October 3, the session field will remain unselected by default until that date. On October 3, the required sessions will then 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 current date or event date. For example, you can automatically set the value of your text field to "N/A" before November 1.

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" after July 15, the text field will be blank until that time passes. After July 15, 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 current date or event date. For example, you can automatically increase the price of your tickets by 15% for events taking place after July 25.

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 reduce the price of your merchandise from $10 to $5 on July 29, the price of the t-shirt will remain $10 until that date. On July 29, the price will then automatically change to $5.

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 for people who purchase tickets before April 30, and someone purchases two VIP tickets in the same order before that date, 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 current date or event date. For example, you can decrease the capacity from 500 to 400 after September 2.

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 for events taking place before June 30, that limit will only apply when a ticket buyer selects an event date prior to June 30. For events that take place after June 30, 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 current date or event date. For example, you can change the maximum number of tickets allowed per order from 5 to 3 if the date is after July 2.

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 between August 3 and 5, this limit will only take place between these dates.

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 Actions to Show or Hide Fields on Your Page

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

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

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 Date-based Actions That Trigger Based on the Current Date or the Event Date