For events that require registration, ticket purchase or other types of payments the combination of the event calendar and the form tool offers a complete solution to automate everything.

In this guide we'll walk you through:

Navigate to Events -> Add New Event (or click on the Add New Event button at the top of the main events list screen).

Add your event description including photos, flyers, etc. in the content section. Use the Advanced Layout Editor to use drag-and-drop layouts with things like multiple columns, image galleries, etc. or just use the standard editor to enter text and images.

Fill out the Event Details and optionally assign the event to a category (social, swim team, etc.). Those can be used to color code different event types on the calendar that is displayed to users.

Hit Publish and your event is now live and will display something like what's shown below to visitors to your site (or choose Save Draft to save your work but not make the event live until you have set up the ticketing form).

For the next step we take advantage of the Member Splash Form Template Library to install a pre-configured event registration form that we can tweak and use. Under the Forms menu click on MS Form Templates to see a gallery of pre-configured forms you can import with one click.

We're going to use the Event RSVP template. Click on the Install Form button and you'll see it toggle to a loading indicator and then back. That's it, the form is now on your site!

Now click on Forms to see all of the forms your site is using, including the one you just installed. The name will be Event RSVP.

While the form shows that it is active (available for use) it is not yet displayed anywhere so nobody will see it yet. First you'll adjust a few things to fit your requirements.

Clicking on the name of the form will take you into the form editor. This is where you can add, edit and delete form fields; change ticket pricing and quantity limits; and more.

Form fields like this one shown below are hidden fields that contain instructions to help guide you in configuring the form. They will never display to users so you can leave them in place or delete as you prefer. This particular one is just reminding that if this form is going to collect payment information then you have to configure the payment feed.

The next form field is the Acct #. When you hover over a field in the form clicking on the third icon (shown in blue) will show you the field settings to the right of the screen.

Acct # is a custom Member Splash field that will automatically populate with the account number of a logged in user. You may have a form that isn't restricted to members -- perhaps your event is open to the public. You can safely leave this field and it will track the account number for those people who are logged in and simply have a blank value for those who aren't.

The third field is a Name field. That is one of the advanced form fields and it supports collecting first and last names as well as (optionally) prefix, suffix and middle name. You'll find the documentation for it here.

The fourth form field is a Phone Number field. It supports options for enforcing things like the phone number format. The template has it set to ###-###-####. You can read about that field type here.

The fifth field, Email, is one you definitely want to include and require. It will be used in the payments feed and any notification emails to send receipts and potentially additional information. It will also allow you to build a list of attendees that you can use for reminders and such. You'll find that field type documented here.

The last few fields handle the pricing, optional quantity limits, and gathering the payment information.

The field labeled # Tickets is a Product field. For this example we'll change the price to $15. You can read about product fields here.

From the field settings under the General tab you'll see options for the Price, to make it Required and more.

If you want to limit the total number of tickets that can be purchased for the event you can scroll down a bit further to the section labeled Perks and set inventory rules for the product. You can get a detailed explanation of that here. In this example we're capping total ticket sales for the event to 250.

Next up is a Subtotal field. This is useful for things like calculating a processing fee (see next field type).

The next field, Processing Fee, uses another Product Field to add an online service fee to the order. In this case the Field Type setting is set to calculation, which allows for dynamically generating a value based on other field settings. If you don't wish to charge one you can simply delete it.

The Total Field simply shows the total amount to be charged, including any processing fee. That field type is documented here.

The next form field is the Credit Card field, which has inputs for collecting the card number, expiration date, etc. This field type is documented here. You'll want to make sure this one is required (denoted by the red asterisk next to the field label -- it is by default).

The next form field, Billing Address, is used by the credit card address verification system to help prevent fraud. It checks that the address on file with the card issuing company matches what the user inputs. Details on the Address field type are here.

The final form field, Captcha, is a security measure to help prevent bot traffic. There is nothing you need to configure for this. The official documents for that are here.

Your form is now set up but there are a few settings you'll need to configure before going live.

Confirmations are what is displayed to the user after successfully submitting the form. For 99% of forms you'll use a single confirmation which will just be a message letting the user now that the entry was successful. This form template uses a basic one. You can have multiple confirmations that get displayed conditionally depending on the form entry values. You can redirect a user to another page after the form is submitted. The various options are documented here.

Notifications are email messages that get sent out when the form is submitted. In this case you might want an email sent to a social chair who is responsible for the event with the order details and a second email sent to the person who submitted the form with the details of their order and possibly some additional instructions. Notifications are documented here.

When you create a notification the first setting is the Name. That's just for internal use so you can easily tell what who the end recipient is. To send entry details to a social chair it might look like this.

For the email subject line and message body you'll likely want to include some or all of the form fields. You can do that easily using the form merge tags. They work just like merge tags in a Word Doc.

Feeds are simply actions that can be configured to happen after a form is submitted. In the case of payments, the feed sends the payment details to our online payment processor to actually run the charge. Your club is likely using Ecrypt to handle payments, but may still be using our legacy platform, Authorize.net. You can tell by looking Member Splash Settings -> Payment Settings.

In this example we're going to use Ecrypt but the settings are the same if you happen to still be using Authorize.net. Go to Settings -> Ecrypt Payments and add a new feed.

In the General Feed Settings give the feed a name or just use the default. It's only for internal reference. For Transaction Type choose One Time Payment and for Payment Method choose credit card.

​Under One Time Payment Settings it will automatically populate with Form Total. Leave that.

Under Billing Details map the form fields to the information that will get sent to the payment gateway.

Hit Save Settings and now your form is fully ready to use!

The last thing to do is to add your form to the event. Go back to the event you created at the start and open the editor. Click on the Add Form button and select your form.

You can choose to display the form title and description. The Enable Ajax button simply means that the form can be submitted without reloading the page that it is on.

You now have a fully functional event ticketing form what will display on to users like so: