Skip to main content

Ticket-Specific Conditional Elements

Collect the right information from the right attendees—automatically

Raagini Sarkar avatar
Written by Raagini Sarkar
Updated this week

Ticket-Specific Conditional Elements allow admins to ask custom questions based on the specific ticket, bundle, or sponsorship a purchaser selects.

Instead of showing every attendee the same set of questions, you can configure the system to display additional fields only when relevant—streamlining the checkout experience while ensuring you collect all necessary event details.

This is especially helpful for events that include multiple ticket tiers, sponsorship packages, or attendee experiences with different requirements.

How it works

Each ticket (or bundle) has its own configuration panel where you can add custom attendee fields.

When editing a ticket, you will see a section titled:

Custom fields for attendees

Collect additional information from attendees. These fields will be shown when attendees provide their details.

By clicking + Add Element, you can add fields such as:

  • Text fields

  • Dropdowns

  • Checkboxes

  • Paragraph responses

  • Required or optional questions

These fields will only appear for purchasers who select that specific ticket type.

Where to configure ticket-specific fields

  1. Navigate to your Event's Tickets tab.

  2. Click on the three dots to edit the ticket you would like to select (e.g., Early Bird Ticket, VIP Ticket, Sponsor Table)

  3. Scroll down to Custom fields for attendees

  4. Click + Add Element

  5. Configure your field:

    • Field label

    • Field type

    • Required or optional

  6. Save your changes

Each ticket can have its own unique set of questions.

Important behavior notes

  • These questions are collected per attendee, not just per purchaser.

  • If someone purchases multiple tickets, the system will collect responses for each assigned attendee.

  • The purchaser does not need to be the attendee (for example, an executive assistant may purchase tickets on behalf of others).

  • Fields only appear when the associated ticket is in the cart.

This ensures a clean checkout experience without overwhelming users with irrelevant questions.

Why use Ticket-Specific Conditional Elements?

Different ticket types often represent different experiences, benefits, or access levels. Asking the same questions for every ticket can create friction and confusion.

Ticket-Specific Conditional Elements allow you to:

  • Keep checkout simple

  • Improve data accuracy

  • Avoid unnecessary follow-up emails

  • Reduce manual list management

  • Improve event logistics

Sponsorship-Level Information Collection Use Case

A corporate gala offers sponsorship packages that include:

  • Company logo placement

  • Program recognition

  • Reserved table seating

For sponsorship tickets, you can add conditional fields such as:

  • Company Name

  • Logo Upload

  • Sponsor Recognition Name

  • On-site Contact Person

  • Preferred Table Name

These questions will only appear when a sponsorship-level ticket is selected—keeping general admission checkout streamlined.

This prevents:

  • Collecting sponsor-only information from general attendees

  • Manual follow-up for branding assets

  • Delays in sponsor recognition materials

Dietary Preferences for Meal-Included Tickets

An event offers:

  • General Admission (no meal)

  • Dinner Ticket (includes plated meal)

  • VIP Experience (includes premium dining)

You can add dietary preference fields only to tickets that include meals:

  • Dietary restrictions

  • Vegetarian/Vegan selection

  • Allergy information

This ensures:

  • Meal counts are accurate

  • Catering is streamlined

  • Attendees without meals are not confused by unnecessary questions

This is particularly helpful for hybrid or tiered experiences where not all attendees receive the same benefits.

Tier-Based Experience Details (VIP Access or Special Sessions)

An event offers:

  • General Admission

  • VIP Backstage Access

  • Workshop Add-On Ticket

VIP tickets may require:

  • T-shirt size

  • Security information

  • Preferred session time

  • Special access waivers

Workshop tickets may require:

  • Session selection

  • Skill level

  • Equipment preference

By attaching these fields only to relevant tickets, you create a clean and intelligent checkout flow where:

  • Attendees only see questions tied to their experience

  • Event organizers receive precise logistical information

  • On-site check-in runs smoothly

Best Practices

  • Keep required fields limited to essential logistics.

  • Use clear, descriptive field labels.

  • Test checkout flows for each ticket type before launch.

  • Avoid duplicating questions across tickets when not necessary.

  • Use ticket descriptions to explain why certain information is being collected.

Ticket-Specific Conditional Elements allow you to design a smarter event registration flow—one that adapts dynamically to what participants are purchasing.

Whether managing sponsorship details, meal preferences, VIP access, or session selection, this feature ensures your team collects the right information at the right time—without overcomplicating checkout.

If you have questions about Ticket-Specific Conditional Elements, schedule a support call with our success team.

Did this answer your question?