Create an Event

Basics

• Event Title: use a unique, plain-language title.
• Event Type: select first; changing it can load different defaults and day settings.
• Single or multi-day: controlled by the chosen event type. Check generated day fields carefully.

Dates, times, and sales window

• Enter each event day in chronological order.
• Enable times only when attendees need them shown.
• Set sales start to delay when booking opens.
• Set sales end before the event finishes. Events Plus may adjust an invalid sales end automatically.
• Sales cut-offs use the event country’s local timezone; the site’s WordPress timezone affects general date and reminder processing.

Venue and capacity

• Use address search when the administrator has configured Google Maps, then verify every populated field.
• Add a public map URL if useful.
• Turn on venue concealment when the exact address must remain private.
• Set how many days before the event the full venue details should be emailed.
• Set capacity to the real maximum. Test guest and multi-day bookings against it.

Organiser, reminders, and price

• Add organiser name and email to display the Message Event Organiser option.
• Set reminder days for ordinary bookings. When venue details are concealed, the venue-release message becomes the key information email.
• Set Cost to zero for a free event.
• For paid events, select whether cost applies per attendee or per attendee day, choose currency, and select Stripe or PayPal.
• Save provider credentials in My Settings, never in the event description.
• Use PayPal Sandbox or Stripe test keys during testing, then switch deliberately to live credentials.

Summary, description, FAQs, and image

• Summary: concise text used on cards and social sharing; keep within 140 characters.
• Full Description: include audience, outcomes, schedule, accessibility, cancellation terms, and what to bring.
• FAQs: answer common questions before launch.
• Featured Image: use a landscape 16:10 image, ideally at least 1200 by 750 pixels, with permission to publish it.

Booking or application form

• Use Standard booking form for straightforward ticketing.
• Use Detailed application form when organisers need additional applicant information.
• An application-only event collects applications rather than behaving like normal ticket stock.
• Add only fields genuinely needed for the event.
• Configure Airtable mapping and Mailchimp opt-in per event only after manager credentials are saved.

Preview

Use the Preview tab to check the events card, event page, image, details, FAQs, organiser contact, and form. The preview is a guide; always test the published page in a separate logged-out browser.

Save and publish

1. Choose Draft while reviewing.
2. Save the event.
3. Open its public URL and make a complete test booking.
4. Check emails, My Tickets, capacity, any payment, and check-in.
5. Return to Edit, choose Published, and save.
6. Share the public event URL, not the create/edit URL.