Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Dynamic Checkout: Checkout Form Rules

Based on the ticket, offer, or giving level a user chooses during checkout, some fields can be set as shown, hidden or made required.

  • To start entering rules using Dynamic Checkout click on Checkout Options, and then select Dynamic Checkout under the Conditional Checkout option. 

Screenshot 2024-08-05 091543

  • On the Dynamic Checkout page click Click Here To add new rule button to start entering rules.

two

  • On this page you can start entering your rules using the fields shown.

three

  • In the Match tab you will have the option of choosing ANY or ALL depending on how you want to match your Rule.
  • If you choose Any, then the rule will be applied when the user selects "any" of the items you select in the checkout selection items list in this rule.  
  • If you choose All, then the rule will be applied when the user adds all of the items you have selected in the checkout selection item list.

four

  • In the Checkout Selection Tab you have the option of choosing one, more items. The list will have all your tickets, offers or giving levels to choose from.
  • The selection(s) indicate when this particular rule will be applied.  Think of this selection as your "trigger" for this rule.

five

  • In the Action tab there are a few options. You can make the fields in Action selections, to either Show, Hide, Make Required or Make Optional.

six

  • In the Fields in Action Tab, make a selection/s of the fields that you want to show, hide, make required or make optional.

seven

Example

  • In the example below the Rule states, All Register tickets will have Cell Phone, State and Street as required fields in the checkout form.
  • The donor who chooses to purchase the Register ticket in the checkout will have these fields show as Required. Click Save once the rule is ready to be set.

eight

  • To add more rules click on Add Rule as shown below.

nine

  • In the second rule example it states Any group tickets 3/$10 or Single tickets that are purchased will have Cell phone, Meal preference, State and Street fields as required fields.

ten

  • When the form is shown to the purchaser, as the user makes various selections, if there are any rules detected based on the selections, these rules will apply.
  • If there are clashing rules on visibility of a field, e.g. one rule wants to show a field, and another rule wants to hide it, then the field will be shown.
  • If there are clashing rules on required level of a field, e.g. one rule wants to make it required, and another rule wants to make the same field optional, then the field will be set to be required.

 

Need Additional Help?

We're here to assist you in any way we can. Don't hesitate to reach out to support@betterunite.com

Let's go do some good.