Ask before payment only what you need to issue the ticket: name, email, ticket type and anything legally required. Ask after payment everything you need to run the event: dietary needs, session choices, accessibility, job title for the badge. Every extra field before the card step costs you completions; every field after it costs you nothing but a reminder email. Eventbrite added the after-payment option on 14 September 2026; Humanitix, Cvent and Swoogo already had a version of it, and Ticket Tailor asks everything up front.
Why the timing of a question matters more than the question
A registration form is a negotiation. The attendee wants the ticket and you want the data, and the payment step is where the balance of power flips. Before it, the attendee can leave without losing anything, so each question is a small tax on their patience. After it, they have already committed money and time, and finishing a short form is the path of least resistance. The same twelve questions produce a different completion rate depending on which side of the card step they sit.
This is not a hypothetical. Checkout abandonment work across ecommerce keeps finding the same two culprits, forced account creation and long forms, and event registration inherits both. A question the buyer cannot answer on the spot (which workshop track, which dietary code, their colleague's badge name) is a question they will answer tomorrow, which in a pre-payment form means never. Move it after the receipt and it becomes tomorrow's task rather than today's excuse.
What belongs before payment
Anything without which the ticket cannot legally or practically exist. That is the buyer's name and email, the ticket type and quantity, a marketing consent tick where your jurisdiction requires it, and the terms acceptance. If the ticket is named and non-transferable, the attendee name per ticket belongs here too, because a badge printed for "Guest 3" is a queue at the desk later.
The test is simple: if the answer changes whether you can sell them the ticket, ask it now. Age restrictions, membership numbers that unlock a member rate, a purchase-order number your finance team insists on for corporate bookings, an exhibitor's stand choice that determines the price. Those questions are part of the transaction, not an addition to it.
What belongs after payment
Everything that helps you run the day rather than sell the seat. Dietary requirements and allergies. Accessibility needs. Session or workshop preferences. Company, role and the exact spelling they want on the badge. T-shirt size. How they heard about you. Whether they want to be listed in the attendee directory. None of these change the price, and all of them are easier to ask once the attendee has stopped worrying that the form is a trick to make them abandon.
The trade-off is completion. A post-payment form is optional in practice even when it is marked required, because the attendee already holds the ticket. Your fallback is a reminder sequence and a plan for blanks: a default meal, a badge that prints from the buyer name, a session allocation on the door. If a blank answer would break your event, it was a before-payment question wearing the wrong label.
Which platforms let you split the form
This is the part that has changed in the last fortnight, so it is worth being precise. The table records what each platform's own documentation says today about where questions can sit and whether they can branch. Cells are deliberately plain; the links in the text carry the sources.
| Platform | Questions before payment | Questions after payment | Branching on an earlier answer | Questions limited to a ticket type |
|---|---|---|---|---|
| Eventbrite | Yes, any order by drag and drop | Yes, required or optional, since 14 September 2026 | Not part of the September update | Yes |
| Humanitix | Yes | Yes, any question can be asked post-checkout | Yes, conditional questions on a previous answer | Yes |
| Ticket Tailor | Yes, buyer questions plus per-ticket attendee questions | No, the checkout form is asked at order time | No | Yes, attendee questions per ticket type |
| Cvent | Yes | Not verified for this article | Yes, conditional logic and question tracks | Yes, by registration type |
| Swoogo | Yes | Not verified for this article | Yes, multi-level logic on Enterprise | Yes |
| eventcloud | Yes, one form per ticket group, fields in any order | No, the form is completed at registration | No | Yes, a different form per ticket group |
Eventbrite's product updates page is the source for its September change: organisers can now see where each question appears, drag questions into order, and set required questions both before and after payment. Humanitix's help centre documents checkout questions that can be limited to ticket types, made required or asked post-checkout, plus conditional questions that only appear when an earlier answer matches. Ticket Tailor's checkout form guide describes buyer questions on the global form and attendee questions assignable to specific ticket types, all collected during checkout. Cvent's support site covers conditional logic and different question tracks by registration type. Swoogo's pricing page lists unlimited conditional logic on every plan and reserves multi-level conditional logic and unlimited visibility rules for Enterprise, which is the kind of ceiling worth reading twice before you sign.
Run the Whole Event From One Platform
Ticketing, registration, promotions and check-in together, so the plan and the tools finally match.
Does asking more questions cost more?
On most platforms the questions are free and the answers are not, because the answers arrive attached to a paid registration. Eventbrite charges 3.7% plus $1.79 per paid ticket plus 2.9% processing, so a $50 ticket carries $3.64 in platform fees before card costs, which is $1,820 at 500 tickets, $18,200 at 5,000 and $182,000 at 50,000, however many questions you ask. Humanitix's 2.1% plus $0.99 lands at $1,020, $10,200 and $102,000 on the same numbers. Cvent and Swoogo sit behind quotes and a per-user licence respectively, with Swoogo's Professional tier at $11,800 a year for one full user and unlimited registrations.
eventcloud is priced per user, at $125 a month per seat, with unlimited events, unlimited tickets, unlimited registrations and unlimited attendees on that seat and payments through your own Stripe account. So the year costs $1,250 at 500 registrations and $1,250 at 50,000, and a free visitor registration with ten questions on it costs exactly what a paid delegate pass with two questions does, which is nothing extra. The honest edges: you pay for each team member who needs a login, there is no white-label add-on to buy because that capability sits with Enterprise customers, and Stripe's processing fee is Stripe's, never included. Where the form design saves you money is not the platform fee but the desk on the day: an answer captured at registration prints straight onto the badge and shows on the check-in screen, so nobody is transcribing a spreadsheet at 7am.
A form layout that survives contact with real attendees
Start from the badge and work backwards. Whatever is printed on it (name, company, role, ticket type) must be captured somewhere, and if the platform cannot ask after payment, it must be asked before, kept short, and validated as people type so a typo does not become a reprint. Keep the before-payment form to five fields or fewer for consumer events and eight for B2B, and put the marketing consent where the law wants it rather than where the designer does.
Then group the after-payment questions by who needs the answer. Catering needs dietary answers by a fixed date, so give that section a deadline and a reminder. The programme team needs session choices, which can be optional with a sensible default. The badge team needs the spelling confirmed, which is a one-line "is this right?" on the confirmation email. If your platform has no post-payment stage, the same grouping still works: put the must-haves first, the nice-to-haves last and marked optional, and attach a different form to each ticket type so a speaker is never asked which workshop they are attending. Our guides on the questions worth asking and on showing different questions to different attendee types go deeper on the content of the form; this piece is about its timing.
Who this is not for
eventcloud does not do conditional form logic. If your registration depends on branching, where answering "exhibitor" reveals six stand questions and answering "press" reveals none, Humanitix, Cvent or Swoogo will serve that design better; eventcloud's answer is a separate form per ticket group, which covers the common case and not the exotic one. eventcloud does not do virtual or hybrid events either. If most of your programme happens on a screen, Bizzabo or vFairs are built for that and this platform is not. And if you sell a few hundred low-priced tickets a year, a per-ticket platform with a free tier will usually cost less than any seat, however well the form is laid out.
If your event lives or dies at the door rather than the onsale, the registration form is the most valuable piece of software you own, and the timing of each question is the cheapest conversion lever you have. See how a form per ticket group works on eventcloud's registration page, or compare the fee arithmetic on the pricing page.