Skip to main content
Events template

Event Ticket Form template

Collect attendee details and hand the order to a verified payment checkout. Copy the accessible markup, adjust the fields, and publish it with Core Forms.

Rendered

What your visitor sees

Plain semantic HTML rendered through the same default form theme Core Forms applies on the front-end. Try it — this demo confirms inline and sends nothing.

Demo only. On your site, the same markup wires into the normal Core Forms action loop — email, Slack, Google Sheets, webhook, whatever you configure.

Source

The HTML behind it

Copy this block, paste into Core Forms → Add New Form → Fields tab, save. Field names map to merge tags automatically in your action templates.

<p><label for="et-name">Attendee name</label><input id="et-name" name="NAME" type="text" autocomplete="name" required aria-required="true"></p>
<p><label for="et-email">Email</label><input id="et-email" name="EMAIL" type="email" autocomplete="email" required aria-required="true"></p>
<p><label for="et-type">Ticket type</label><select id="et-type" name="TICKET" required aria-required="true"><option value="">Choose a ticket</option><option value="standard">Standard</option><option value="student">Student</option></select></p>
<p><label for="et-qty">Quantity</label><input id="et-qty" name="QUANTITY" type="number" min="1" max="6" value="1" required aria-required="true"></p>
<p><button type="submit">Continue to payment</button></p>

When to use it

What this event ticket form template is for

Use it for a simple paid event when the ticket options fit in one form and seat inventory is enforced.

This version asks only for information needed to complete that job. Prevent overselling with a submission or inventory limit, and issue the ticket only after verified payment.

The markup uses explicit labels, useful autocomplete values, and fieldsets for grouped choices. You can edit every line instead of working around a locked template schema.

Every field, and why it's there

FieldTypeRequiredWhy it's there
Attendee name text Yes Printed or stored on the ticket.
Email email Yes Receives ticket and event notices.
Ticket type select Yes Maps to a price or product.
Quantity number Yes Controls seats and total.
Setup

From this HTML to a working form

  1. 1

    Create the form from a template

    In Core Forms, add a new form and choose the Event Ticket Form starting point, or paste the HTML below into code mode.

  2. 2

    Remove what you will not use

    Delete unnecessary fields, update the labels and choices, then set the success message to explain what happens next.

  3. 3

    Test the whole path

    Submit the form with realistic data. Verify validation, the saved submission, notification email, autoresponder, and any integration action.

Make it yours

Three upgrades worth considering

Show fields only when needed

Keep the first view short and reveal follow-up questions from an earlier answer.

Use conditional logic →

Route the submitted data

Send the result to email, a CRM, a spreadsheet, or a signed webhook after validation.

Explore integrations →

Check the funnel

Measure starts, successful submissions, and field drop-off after the form has real traffic.

Use form analytics →
FAQ

Event Ticket Form template questions

Is this event ticket form template free to copy?

Yes. The HTML on this page is free to copy and adapt. Core Forms is required only if you want its WordPress submission handling, inbox, actions, analytics, and other plugin features.

Can I change or remove fields?

Yes. The form is plain HTML. Remove any field you cannot justify, rename fields before collecting data, and keep every label associated with its control.

Does the template save submissions in WordPress?

Core Forms can save successful submissions in its WordPress inbox. Storage is a per-form setting, so you can disable it for forms whose data should not be retained.

Can the form send a confirmation email?

Yes. Add an autoresponder action, map its recipient to the submitted email field, and state what the person should expect next.

How should I test it?

Use realistic valid data, missing required data, a malformed email address, keyboard-only navigation, and a narrow mobile viewport. Also verify every configured action and redirect.

The template is free. The plumbing is the product.

Core Forms turns this HTML into stored submissions, spam-filtered email, and 30+ integrations. Use CFLAUNCH for 20% off.