Dynamic Require-Not Require Actions allow you to automatically change whether a field is required or optional based on specific conditions on your event registration page. This gives you greater control over the form experience, ensuring you collect the right information at the right time.

For example, you can create an action where if someone selects a VIP Registration option, a Sessions field that’s usually optional becomes required, ensuring VIPs select their breakout sessions in advance. Whether you're gathering extra info for specific registration options, customizing the form experience for different groups, or streamlining the registration process, Require-Not Require Actions help you require the right questions at the right time.

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.

Example Use Cases

Require a multiple choice field when someone selects your General registration option
Don't Require a custom question on your page after a specific date

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

First, add the trigger field(s) (if applicable) where you want to require or not require your field(s). Below includes some example triggers that you might want to utilize.

Create Actions Triggered by the Date

In RegFox, you can create actions that trigger based on the current date! For example, you can not require your Sessions field if the date is after January 31.

Note: Date-based actions are triggered by the current date when the registrant signs up for your event. If you edit the registration after the action date has passed, the action will still apply as long as the registrant originally signed up before that date.

For example, if you choose to require a field for those who register before January 25, this field will remain required for a registrant who signed up on January 5, even if you edit their registration on March 11.

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 require/not require the field(s) on a specific date
- The Is Between option will require/not require the field(s) between specific dates
- The Is Before option will require/not require the field(s) before a specific date
- The Is After option will require/not require the field(s) after a specific date
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions are met

Create Actions Triggered by the Registrant's Date of Birth

If using the Date of Birth field, you can create actions that trigger based on the registrant's date of birth. For example, you can not require a parental waiver field if a registrant is over 18.

On the left-hand side, select Date of Birth from the dropdown
Select one of the following options and add the desired date and time
- The Is Completed option will require/not require the field(s) when someone adds their date of birth
- The Is Not Completed option will require/not require the field(s) when someone does not add their date of birth
- The Date is Before option will require/not require the field(s) if the registrant's date of birth is before a specific date you set
- The Date is After option will require/not require the field(s) if the registrant's date of birth is after a specific date you set
- The Date Is option will require/not require the field(s) if the registrant's date of birth is a specific date you set
- The Day of the Week option will require/not require the field(s) if the registrant's date of birth is on a day of the week that you specify
- The Age Less Than option will require/not require the field(s) if the registrant is younger than the age you set
- The Age Greater Than option will require/not require the field(s) if the registrant is older than the age you set
- The Age Is option will require/not require the field(s) if the registrant is the age you set
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Create Actions Triggered by the Number of Registrants in an Order

If using our Group Registration feature, you can create actions that trigger when someone registers a specific number of people in an order. There are two different types of actions that you can use in RegFox.

The Registrants in a Transaction option is triggered when someone registers a specific number of people that you define. When triggered, this action applies to all registrants in the order.

The Specific Registrant option is triggered when someone registers a specific number of people, but the action only applies to the specific registrant(s) you designate.

For example, if a user sets an action to require a Text Field for Registrants 3 and over...

Registrants in a Transaction: RegFox will require the text field for all registrants in the order. Registrants 1, 2, and 3 will all be required to enter text into this text field
Specific Registrant: RegFox will require the text field only for Registrants 3 and over. Registrants 1 and 2 will not be required to enter text field into this text field

On the left-hand side, select Registrants in a Transaction or Specific Registrant from the dropdown
Select one of the following options and add the value/date to the field below
- The Greater Than (Registrants in a Transaction option) option will require/not require the field(s) if a registrant registers a group larger than the number you set in a single order
- The Less Than (Registrants in a Transaction option) option will require/not require the field(s) if a registrant registers a group smaller than the number you set in a single order
- The Is (Specific Registrant) option will require/not require the field(s) if a registrant registers a group of the exact size you set in a single order
- The Date is Between (Specific Registrant) option will require/not require the field(s) if the registrant is registering between specific dates
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Pro Tip: If you want to trigger an action for a specific registrant in the group using the Specific Registrant option, we recommend entering the same number in both fields.

For example, to require a specific field only for the second registrant, we recommend selecting the Is (Specific Registrant) option and entering 2 to 2 in the text fields that appear.

Create Actions Triggered by the Tracking Link a Registrant Uses

If using our Tracking Link feature, you can create actions that trigger when someone uses a specific tracking link. For example, you can automatically require a Company text field if a registrant uses your tracking link.

On the left-hand side, select Tracking Link from the dropdown
Select your desired option and select the tracking link(s) you want to target
- The Is option will require/not require the field(s) if a registrant uses the tracking link you select
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Create Actions Triggered by the Inventory of Your Event or the Registration Option Someone Selects

In RegFox, you can create actions that trigger based on the registration option someone selects. For example, you can automatically require additional fields if a registrant chooses the VIP registration option.

Pro Tip: You can target the entire Registration Options field with Actions, or target a specific selection within the Registration Options dropdown. Targeting the Registration Options field will offer different actions than selecting a specific registration option in the dropdown.

On the left-hand side, select the Registration Options field or select the specific registration option you want to target from the dropdown
Select your desired option, and add a value/quantity to the field below if needed
- The Is Completed option (Registration Options field only) will require/not require the field(s) when a registrant selects any registration option
- The Is Not Completed option (Registration Options field only) will require/not require the field(s) when a registrant doesn't select any registration option
- The Value Contains option (Registration Options field only) will require/not require the field(s) when a registrant selects a registration option containing a value you enter
- The Value Ends With option (Registration Options field only) will require/not require the field(s) when a registrant selects a registration option ending with a value you enter
- The Selection Is option(Registration Options field only) will require/not require the field(s) when a registrant selects a specific registration option you select
- The Selection Is Not option (Registration Options field only) will require/not require the field(s) when a registrant doesn't select a specific registration option you specify
- The Is Selected option (specific registration option only) will require/not require the field(s) when a registrant selects the specific registration option you specify
- The Is Not Selected option (specific registration option only) will require/not require the field(s) when a registrant doesn't select the specific registration option you select
- The Remaining Inventory Is option will require/not require the field(s) when the remaining inventory of a registration options field or an individual registration option reaches the level you set
- The Inventory Sold Out option will require/not require the field(s) when the inventory of your registration options field or an individual registration option is sold out
- The Quantity Sold Is option (specific registration option only) will require/not require the field(s) when the your registration option reaches a specific number of sold registrations
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Create Actions Triggered by a Registrant's Custom Selections on the Registration Page

In RegFox, you can create actions that trigger based on a registrant's selections. For example, you can automatically require a follow-up question if a registrant selects that they have dietary restrictions.

On the left-hand side, select the custom field option you want to target
Select your desired option
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Create Actions Triggered by a Registrant's Email or Other Text Inputs

In RegFox, you can create actions that trigger based on a registrant's email or other text they enter on the registration page. For example, you can automatically not require a multiple choice field if a registrant's email contains regfox.com.

On the left-hand side, select Email or the Text Field from the dropdown
Select one of the following options and add a value to the field below if needed
- The Is Completed option will require/not require the field(s) when a registrant enters text on the field
- The Is Not Completed option will require/not require the field(s) when a registrant doesn't enter text on the field
- The Value Is Exactly option will require/not require the field(s) when a registrant enters the exact text you specify
- The Value Is Not Exactly option will require/not require the field(s) when a registrant doesn't enter the exact text you specify
- The Value Contains option will require/not require the field(s) when a registrant enters text containing the value you specify
- The Value Ends With option will require/not require the field(s) when a registrant enters text ending with the value you specify
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Create Actions Triggered by a Coupon Code

In RegFox, you can create actions that trigger based on a coupon code that a registrant uses. For example, you can automatically require your merchandise field if a registrant enters the coupon code MERCHANDISE.

On the left-hand side, select Coupon Code from the dropdown
Select one of the following options and add a value to the field below if needed
- The Is Completed option will require/not require the field(s) when a registrant enters a coupon
- The Is Not Completed option will require/not require the field(s) when a registrant doesn't enter a coupon
- The Value Is Exactly option will require/not require the field(s) when a registrant enters the exact coupon code you specify
- The Value Is Not Exactly option will require/not require the field(s) when a registrant doesn't enter the exact coupon code you specify
- The Value Contains option will require/not require the field(s) when a registrant selects a coupon code containing the value you specify
- The Value Ends With option will require/not require the field(s) when a registrant selects a coupon code ending with the value you specify
- The Is Valid option will require/not require the field(s) when a registrant enters a valid coupon code
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Create Actions Triggered by the Payment Method a Registrant Selects

In RegFox, you can create actions that trigger based on the payment method someone selects. For example, you can require an Address field if a registrant selects your cash/check payment method.

On the left-hand side, select the payment method you want to target
Select your desired option
- The Is Selected option will require/not require the field(s) when a specific payment method is selected
- The Is Not Selected option will require/not require the field(s) when a specific payment method is not selected
Click the + button if you would like to add multiple triggers
- If you add multiple trigger conditions and would like for all of them to be met in order for the action to take place, be sure to check the box that states: All of these must be true
- If this checkbox is not selected, the require-not require action will occur if any one of the conditions is met

Add Your Require-Not Require Action

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

Pro Tip: It is important to know that actions run from top to bottom. So if you have multiple actions in your RegFox 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.

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 registration 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 RegFox 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 registrants. This link will not accept real registrations 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 RegFox 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 Dynamically Require or Not Require Fields On Your Page