Purpose

Collect the information your event team genuinely needs without making signup unnecessarily difficult.

Choose where to ask the question

• Use Questions at signup for a question that should be asked once per attendee, whether the person buys a ticket or signs up for free.
• Use Questions for this ticket for a question tied to each ticket of one specific type.
• Use a bundle checkout question when the answer belongs to a bundle order instead of an event attendee.

Do not ask the same question at more than one level unless the duplication is intentional.

Plan the form

For each answer, decide:

• who needs it and why;
• whether it is required;
• whether free text is necessary;
• whether a fixed option list will produce cleaner operations and reporting;
• how long the answer should be retained;
• whether it is sensitive personal data that should not be collected here.

Step by step: add event-level questions

1. Open Events and select the event.
2. Open Forms.
3. Under Questions at signup, select Add question.
4. Enter the question text.
5. Choose the question type: Text, Dropdown, Yes / No, or Number.
6. Turn on Required only when signup must not finish without an answer.
7. For a dropdown, add at least two options.
8. Move questions into the order guests should see them.
9. Use Preview to review the flow.
10. Select Save questions.
11. Confirm Questions saved.

If the event still uses an old form, use Convert to questions. The existing questions and collected answers remain intact.

Add ticket-specific questions

1. Open the event’s Tickets view.
2. Find the ticket type.
3. Open its question editor.
4. Add only questions that apply to that ticket type.
5. Save the questions.
6. Test an order containing that ticket type.

Ticket-specific questions are asked per ticket. This matters when one buyer purchases several tickets.

Write questions that work operationally

• Prefer a dropdown for teams, meal choices, sizes, or other known options.
• Use Yes / No for a clear binary decision.
• Use Number only when calculations or numeric sorting are useful.
• Use free text for information that cannot be represented safely by fixed choices.
• Avoid combining several decisions in one question.

Test before publishing

1. Preview the questions in Connect.
2. Complete the real signup or checkout flow with a test attendee.
3. Test every required field and dropdown option.
4. When ticket-specific questions exist, test multiple tickets in one order.
5. Confirm the answer is attached to the intended attendee or ticket.
6. Verify that operational staff can interpret the exported value.

Review and export answers

1. Return to Forms.
2. Open Answers.
3. Review the answers shown for tickets and registrations.
4. Select Download CSV to export one row per attendee with question and option labels.
5. Store and share the file according to your organization’s privacy rules.

Change questions during signup

Avoid changing answer meaning after responses exist. Adding a new question does not retroactively answer it for earlier attendees. Renaming options can also make old and new responses difficult to compare.

Record material changes and tell the operational team which registrations were created before and after the change.

Troubleshooting

The form cannot be saved

Finish the questions marked as needing attention. Every question needs text, and dropdown questions need at least two options.

An answer appears more than once

Check whether the question is ticket-specific and the buyer purchased several tickets.

The export is missing a person

Confirm that the person completed registration and that you are reviewing the correct event. An invitation or unfinished order is not a completed attendee response.