How to show a registration question only for selected ticket types

1. Map the question to the ticket

Download the ticket-by-question test matrix (Markdown, English)

Write the exact question, why it is needed and who will use the answer. For a harmless example, a ticket with a welcome pack might ask which pack color the holder prefers; a standard ticket without that pack should not need the question. List every included and excluded ticket type by its current name or identifier. Decide whether the answer belongs to the person buying the order or to each ticket holder. Keep the shared form short, and avoid making unrelated attendees answer a question that does not apply to their ticket.

2. Check the actual form control

Look for a question-level ticket-visibility setting, not merely a general form editor. Whova documents Tickets → Ticket Setup → Question Forms → Custom fields, where “Who can see this question?” can target selected attendee ticket types; it says all types see a custom question by default. Eventbrite offers “Show this question for specific ticket types” in its custom-question setup. Its answer-triggered conditional sub-question is a separate feature. Wix Events currently says different questions cannot be displayed by ticket type, although questions can be optional. If your platform lacks the needed control, do not describe an optional question as hidden; choose a supported form route or revise the question plan.[1][2][5]

3. Set the scope and response point

Select only the approved ticket types and set required or optional status deliberately. Confirm whether the platform collects the answer from the buyer once or from each attendee. Eventbrite distinguishes those order-form modes and says its custom questions in the cited flow are asked after the order, before tickets are issued once required information is provided. Other platforms or event settings may place the question elsewhere. Record that point in the journey and the owner who will check responses. Save the question and reopen it to verify that its target types, prompt and answer choices persisted.[2][3]

4. Test every buyer path

Use controlled, non-personal test values. Preview or follow a supported test route with an included ticket, an excluded ticket and one order containing both types. Check who sees the prompt, whether a required answer blocks only the intended path, and whether the question appears before or after the order on your configured form. Repeat on a narrow screen if buyers commonly use phones. If the platform cannot test without a real order, use its documented preview or an authorized test process; do not create a paid order just to inspect a field. Record the actual outcomes, including any unexpected question shown to the wrong type.

5. Verify the saved answers

Finally inspect the organizer response view or a permitted test export. Whova says its response view indicates which ticket types saw a targeted question; Eventbrite documents a custom-question responses report. Confirm the test answer is attached to the intended order or attendee and that the excluded path did not collect a stray answer. Limit access to responses to the team that needs them. If tickets were already sold before this edit, handle the existing cohort separately rather than assuming the new question appears retroactively. Assign an owner for a failed branch and retest before relying on the answers for fulfillment.[1][4]