Pro Tip: Actions run from top to bottom. If you have multiple actions on your page, actions toward the bottom can override actions above them. You can reorder your actions at any time, and we highly recommend previewing and testing your page before publishing to make sure all of your actions work together the way you intend.

Note: For Reserved Seating pages, actions can target fields outside of the Reserved Seating venue, but cannot target the venue itself. This means you cannot use actions to change the price of seats, hide seats, or adjust the capacity of your venue.

Note: Volume discounts are based on the quantity selected within a single ticket level, not the total number of tickets in the order. For example, you can apply a discount when someone buys 4 or more General Admission tickets. However, if someone buys 3 General Admission tickets and 1 VIP ticket, the action will not trigger because neither ticket level reached the required quantity.

Pro Tip: The Greater Than option triggers when a ticket buyer selects more tickets than the number you enter. To discount orders of 4 or more tickets, enter 3.

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 $5 discount and someone purchases 4 General Admission tickets, the total discount on the order will be $20.

Pro Tip: The Date trigger is based on the date the ticket buyer purchases tickets. A ticket buyer who purchased during your early bird window will keep that pricing, even if you edit their order after the deadline.

Note: This action is only available for date-based pages. It uses the date the ticket buyer chooses to attend your event, not the date they purchase. To change pricing based on the purchase date, use the Date trigger. Click here to learn how to set up this kind of discount.

Note: This action requires a tracking link to be set up on your page first. Click here to learn how to create tracking links.

Pro Tip: The Remaining Inventory Is option is based on how many tickets are left, not how many tickets have been sold. Remaining inventory starts at your available inventory before any tickets are sold and counts down by one with every ticket sold.

Note: The Tickets trigger looks at the total remaining inventory across your entire event, not a single ticket level. To base the price change on one ticket level's inventory, select that ticket level from the dropdown instead and choose its Remaining Inventory Is option.

Note: Here is how to enter the range if you want to trigger the action based on the first tickets sold or the last tickets available.

Pro Tip: Price change actions only apply while the condition is met. Once your remaining inventory moves outside the range you set, your tickets return to the standard price set in the page builder.

Pro Tip: Actions automatically assume the opposite is true. If a question is set to show when a ticket level is selected, it will be hidden until that ticket level is selected. If a question is set to hide when a ticket level is selected, it will show until that ticket level is selected.

Pro Tip: This action hides tickets based on the current date. To hide tickets based on the date an attendee selects to attend your event, use the Ticket Date Selection trigger instead.

Note: Once a ticket level has accepted orders, we strongly recommend hiding the ticket level instead of deleting it. Deleting a field from your page also deletes the attendee information tied to that field.

To hide the ticket level immediately, set up a hide action with a Date trigger and select today’s date. This prevents buyers from selecting that ticket level for new orders while preserving the information from existing orders.

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 signed up before that date.

Note: Once a ticket level has accepted orders, we strongly recommend hiding the ticket level instead of deleting it. Deleting a field from your page also deletes the attendee information tied to that field.

Pro Tip: Actions automatically assume the opposite is true. When you set a ticket level to show only when a code is entered, it will be hidden by default. You do not need a separate action to hide it.

Note: This action is only available for date-based pages with time slots enabled. The Ticket Date Selection trigger is not available for Standard Pages or Reserved Seating pages.

Pro Tip: Actions automatically assume the opposite is true. When you hide a time slot on a specific date, that time slot will continue to show on every other date.

Pro Tip: If you are using a date-based page, the Set Capacity Limit event will only appear if all ticket levels share the same dates and/or time slots.

If your ticket levels use independent dates and/or time slots, the Set Capacity Limit action will not be available for your page.

Note: Actions can only lower the capacity below the default set in the page builder. If you need a higher capacity on certain dates, increase the default capacity in the page builder and then use actions to reduce the limit on all other dates.

Note: This action is only available for date-based pages with time slots enabled The Set Capacity Limit event will only appear if all ticket levels share the same dates and/or time slots.

If your ticket levels use independent dates and/or time slots, the Set Capacity Limit action will not be available for these triggers.

Pro Tip: Capacity actions only apply when the condition is met. Every time slot that does not meet the condition will use the standard capacity set in the page builder.

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.