Overview #
Registration v2 (Reg v2) is a major upgrade to the registration experience, delivering a more stable, streamlined, and user-friendly experience. This document outlines the key improvements and new capabilities.
Release approach: Reg v2 will be introduced gradually on an app-by-app basis using a controlled feature toggle, if you would like to make the switch to Reg V2, please speak to your Account Manager.
New Features #
- Draft registration:
- Registrants are now saved as a draft the moment they fill in the essential fields (email, first name, last name), even before they complete and submit the form.
- A draft record is immediately visible in the CMS under a new ‘Draft’ status.
- The registrant’s URL contains a token, so they can bookmark or refresh the page without losing their progress.
- If a user returns to the form and enters their email again, they will be prompted to either resume their existing draft or start over.
- Draft users can be targeted with emails (e.g. “You left our form – come back and finish registering”).
- The CMS will also show when a draft was last updated, so admins can tell whether someone is actively filling in the form or has abandoned it.
- Improved Error Visibility:
- Error handling on the registration form has been significantly improved to make it much clearer for guests when something needs to be corrected.
- Errors are now more prominently displayed, including a warning indicator at the top of the form.
- When a guest has added one or more guest tickets with incomplete details, a clear indicator shows which guest form contains an error – no more hunting through every guest one by one.
- Image & Document Uploads for All Registration Flows:
- Previously, image and document uploads were only available on private registration flows. This restriction has been removed.
- Any registration flow, public or private, can now include image or document upload fields.
- This makes it much simpler to collect profile photos or supporting documents without needing to set up a private registration.
- Public Decline Page:
- Guests can now decline an invitation without needing an authenticated invite email.
- A dedicated public decline page is available that anyone with the link can access.
- Guests enter their details and submit to register their decline.
- This page can be linked from a homepage, a generic email, or anywhere else – it does not need to be an authenticated link.
Registrant Dashboard and Reporting:
The Registrant Dashboard now provides enhanced visibility into the registrant journey, along with improved filtering capabilities and expanded export options for easier reporting and management.
- Visible conversion rate when the registration is using invite emails.
- Live updates on the registrants page in the CMS.
- Better connectivity between pages on the CMS:
When returning from registrant, ticket, transactions etc. – it will take you back to the previous location.
What Has Changed #
- Conditional Ticket Mappings:
- Ticket mappings can no longer be set directly on the ticket picker component in the form builder.
- Mappings (sessions, groups, tags) are now configured in two places: on the Ticket Type Edit page (a new dedicated section), or on the Response Mappings page, where all mappings can be viewed and managed together.
- Mappings set via the form (old method) were applied at the point of initial submission. The new mappings are applied only after payment is confirmed (or after an invoice is accepted), preventing partially-paid registrants from being incorrectly placed into groups or sessions.
Ticket & Conditional Mappings: The location and timing of mappings has changed. - Action required on migration: When migrating an app to v2, all existing ticket mappings will need to be re-created in the new location.
- The Completed Registrations page has been removed, and the stats panel on the registrant page is improved with the ability to filter the table by status, group, payment status and question/response.
- Everyone Group Visibility:
- In Reg v2, a registrant is added to the ‘Everyone’ group as soon as they create a draft. Sections gated on ‘Everyone’ will be visible from the very start of the flow. If you need to conditionally show content, use a more specific group or session mapping instead.
- Email Verification Error Page:
- When an email verification link fails (e.g. because it has expired), the guest will now see a helpful page with options to take action.
- The new error page includes a button to resend the verification email.
- There is also a button to contact the event organiser.
- This is particularly important during the v1-to-v2 migration window: any verification links sent before the switch will no longer be valid after migration, but guests can self-serve a new link without needing admin intervention.
- Transactions:
- Each transaction now records each step a guest took through the payment flow (e.g. entered Stripe, cancelled, chose invoice, cancelled, etc.).
- This makes it significantly easier to diagnose payment issues and understand where a guest dropped off.
- Filtering by status remains available.
When a person has tickets in their basket, the review responses will now be collapsed to improve visibility of the current basket and price before continuing.
- Guest Management:
- Deleting a guest is now instant on the front-end form.
- Deleted guests are not permanently removed, they are marked as cancelled in the CMS and can be restored by an admin.
- Guests can no longer register additional guests themselves.
- Guest ticket assignment improvements such as the ability to assign more than one ticket to a single guest.
Switching from Reg v1 to Reg v2 #
To migrate an existing registration flow to Reg v2, please contact your Account Manager.
Important Notes #
- V1 Verification Links After Migration: Any email verification links sent to guests before migration will stop working once the app is switched to v2. Affected guests will land on the new error page rather than a broken link. From there, they can request a fresh verification email via the front-end form. No admin intervention is needed guests can self-service this.
- CSS Considerations: Styles targeting standard form fields (inputs, labels, buttons) are likely to survive. Styles targeting structural or layout elements, such as the guest toolbar or section wrappers, are at higher risk of breaking. Please reach out to a support member via live chat and they will be happy to help rectify any changes.
- Ticket Mappings: When migrating an app to v2, all existing ticket mappings will need to be re-created in the new location. Your old ticket mappings will be available to view for reference in the CMS, but they will be greyed out.
