Before you launch an event: registration setup checklist

Run through this checklist before you share an event registration link publicly. It covers ticket and product pricing, registration links, custom questions, confirmation emails, workflows, payments, and a live test transaction, for both the Create and manage ticketed and RSVP events beta and the legacy form-based flow described in Event Registrations with Forms. Items marked (beta) apply to the Events beta; items marked (legacy) apply to the form-based flow.

Event type and pricing

Wrong prices and wrong ticket types are the most common launch-day problems, so confirm every pricing setting first.

(beta) Confirm the event type is Ticketed or RSVP as intended. Ticketed and RSVP cannot be switched after the event is created; if the type is wrong, create a new event.
(beta) Open each ticket type on the Tickets tab and check the Ticket name, Pricing method (Fixed price or Free), Price, Quantity, and Sale period. Sale period times use the event timezone, so confirm that timezone too.
(legacy) Open the registration form and check every attached product and its selection type: Single Selection or Multiple Selection.
Check every coupon: Discount percentage, Active period, and Usage limits, including any restriction to specific ticket types (beta).

Forms and fields

Registration questions collect the details you need from attendees, so walk the form exactly as a registrant would.

Check the required fields and every conditional-logic path in the form builder.
(legacy) Check the form success message or redirect that registrants see after submitting.

Registration links

An outdated or copied link is the easiest way to send attendees to the wrong event, so test the link before sharing it.

Open the registration link yourself in a private or incognito browser window and confirm the event name, date, and pricing shown are the current event, not a previous event's link.

Confirmation emails and notifications

Each flow keeps its email settings in a different place, so check the one that matches your event type.

(legacy) Check the form's Email notification recipients (staff) and Auto responder (the submitter) on the form's Notifications tab.
(beta) Check the event notifications under Settings → Notifications: For attendees (registration confirmation and reminder emails) and For organizers (new-registration alert and Daily Summary Email).
Check every confirmation email's content matches the correct event, especially if the form or event was copied from a previous one.

Workflows

A workflow with a missing or broad trigger filter can send the wrong event's emails or run for registrations it should ignore, so verify each trigger and run a test.

Check workflow trigger filters for Form Submitted, Payment Received, Order Submitted, or the beta Event Registration trigger: confirm each is filtered to the correct form, product, or event.
Check each workflow is Published, not Draft.
Run a test registration in both a matching and a non-matching scenario to confirm each workflow runs only where it should.

Payments

Confirm the payment connection and run a real test transaction before attendees hit checkout.

(legacy) Confirm the Payment or Sell Products element on the form is connected to the correct payment gateway.
Confirm the account is in the right mode: Test Mode for payment forms, or the beta event's Live mode setting. When Live mode is off, the event runs in test mode and no real payments are processed.
Submit a test transaction and confirm the payment appears under Payments → Transactions with the correct order details and Order ID. See Testing Payment Forms for test cards and mode details.
Confirm the contact record updated as expected in the contact's Activity section and Contact Details page.

These last two items prevent the two most visible mistakes: a broken layout on a phone and a live charge while you are still testing.

Preview the public event page or form on desktop and mobile. The beta public-page editor provides a real-time preview with desktop and mobile views.
Switch from Test Mode to Live Mode before sharing the link publicly, so real registrations are charged and recorded.