Registration
Overview
An overview of the registration options in Zuddl
A single, configurable entry point for every attendee, speaker, sponsor, or team member. Each setting is built to collect only the data you need, route people down the correct path, and hand clean records to every downstream modules.
Flow builder
A drag-and-drop canvas where you lay out each registration step—Form, Ticketing, Add-ons, Order Summary, Thank-You—in any order. Visual arrows show every branch, so complex logic stays readable. This allows organizers to design sophisticated journeys without developer help. For example, employees jump straight to the thank-you page; external guests come to Ticketing, then an approval queue. By adding an **approval step **in the flow lets you review registration request manually to approve or reject them.Custom fields
Beyond default contact data, add text, number, date, URL, dropdown, multi-select, rich-text, country, or session picker fields. Mark any field hidden for back-office use, assign default values, or pre-fill via URL parameters. These options make the registration form a data pipeline, not just a gate. Sales, marketing, and logistics receive exactly the attributes they need—no follow-up emails.Conditional logic
Show, hide, or make a field required based on previous answers. A “Phone number” appears only if a registrant opts for SMS updates; dietary restrictions surface when “In-person” is chosen. The shorter the form, the higher the completion rate, and thus, zero manual cleanup of irrelevant data.Branching
At any step, split the flow into two or more branches that later rejoin. Each branch can contain its own steps, fields, and tickets. You can use branches when you have multiple audience types and don’t want to clone the entire flow. For example, VIP invitees bypass ticket purchase; general public continues to payment.Ticketing
Set price, quantity, sale windows, and tier visibility. Hide or lock tickets, require a coupon, or gate them behind invite lists and domains. Ticket purchase happens mid-flow, so payment and profile data merge into a single record. Ticketing and payment live inside registration, so there is no second checkout URL, no mismatched analytics, and reconciled financials from day one.Invite lists
Upload a CSV of pre-qualified emails, set optional guest limits, and let the system validate addresses in real time. You decide whether invitees can bring plus-ones. For example, a sponsor passes a VIP list; each invitee may bring one colleague, but extra tickets are blocked.Capacity controls
Define a hard cap on total registrations. When the cap hits, choose to stop new sign-ups, reroute to manual approval, or hold entries on a waitlist.Email-domain restrictions
Block consumer emails like Gmail, allow only corporate domains, or upload an allow/deny list. The rule enforces itself at the first keystroke, so registrants immediately know whether they qualify. This is especially useful for customer-only briefings, partner summits, or internal town-halls with external speakers.Skip-ticketing URL
Append?ticket_id=…&coupon=…&skip_ticketing=true to any Flex landing page. The flow pre-selects a ticket, applies a coupon, and bypasses the Ticketing process. For example, field-marketing emails can deep-link to “Free VIP Pass” without exposing coupon codes publicly.