This feature is coming soon that will apply to new events.
If you want it for your existing event, please reach out to our customer support team to activate it.
Unified Buyer and Holder Information
Registering for an event shouldn't mean typing the same information twice. Until now, attendees filled out a Registration step for the buyer, then an Attendee Details step for each ticket holder, even when the buyer and the holder were the same person.
The unified registration flow combines both into a single Attendee Information step. Attendees buying for themselves enter their details once, and those buying for others can add each holder's details on the same page. Checkout drops from four steps to three.
This article covers what's changing, how the new step works, which events get it, and what to check before switching an existing event over.
What's changing
The unified flow merges the Registration and Attendee Details steps into one page, so the checkout path goes from four steps to three.
Registration Steps | Classic flow (4 steps) | Unified flow (3 steps) |
Step 1 | Select tickets | Select tickets |
Step 2 | Registration (buyer details and additional information) | Attendee Information (buyer and holder details together) |
Step 3 | Attendee Details (holder details) | Checkout |
Step 4 | Checkout | — |
In the Classic flow, the buyer's name, email, and buyer-level questions (such as CC Email and Cell Phone) are collected on the Registration page. Holder questions are collected separately on the next page.
In the Unified flow, the buyer's own information and their ticket's holder questions appear together under Your Information, followed by forms for any additional ticket holders.
How the Attendee Information step works
After selecting tickets, attendees land on a single Attendee Information page that asks them to provide the required information for each attendee.
Choose who you're registering for. The Registering for dropdown in the Your Information section lets the buyer indicate whether they're registering for themselves and others, or others only if there are multiple tickets in the order.
If there's only 1 ticket, the buyer can indicate whether they are buying the ticket for them or form someone else.
Fill out Your Information. The buyer's assigned ticket is shown under Your Ticket, followed by their First Name, Last Name, Email, and any buyer and holder questions you've set up, such as Cell Phone or Address. If the attendee is logged in, their name and email are filled in automatically.
If the buyer is purchasing a ticket for themselves, they have the enter their information only once and the form will include all the questions to be asked for attendees depending on the ticket type the chose. If there are multiple tickets in the order, their ticket name appears below Your Information, and if there are multiple ticket types in the order, they can choose which ticket is assigned to them.
If there's only 1 ticket in the order, the Your Information label disappears and shows their ticket name on top.
If the buyer is purchasing for someone else / others, they still have to enter their information and none of the attendee fields will appear in the Your Information section. There is also a note that they are not listed as an attendee for this order.
Add details for other ticket holders. When the order includes tickets for other people, a section for each additional holder appears on the same page. The sections can be collapsed or expanded.
Once all required fields are complete, the attendee clicks Continue to review and pay.
Note: the Copy Information from option copies all the information from the selected user, except for the email address if Unique Emails are enabled in the event.
Which events use the unified flow
Which flow your event uses depends on when it was created.
Event | Default flow | How to get the unified flow |
Created before the release | Classic (4 steps) | Contact the Accelevents team to enable it |
Created after the release | Unified (3 steps) | Nothing to do; it's on by default |
Existing events won't change on their own. Your current registration pages keep working exactly as they do today, so nothing breaks for events already on sale.
Turning on the unified flow for an existing event
The unified flow can't be switched on from the Admin Console. To enable it for an existing event, reach out to Accelevents Support or your Customer Success Manager and include the name or URL of the event you'd like to switch. Our team will turn it on for you in the backend. If you created a new event and you want the classic flow, you can also request to switch it to classic.
Before you send the request for the unified flow, review any custom scripts on your registration page (see the next section), since they may need to be replaced.
⚠️ Important: Existing Custom Scripts May Not Work
If you switch an existing event to the unified flow, custom scripts on your registration page may stop working.
The unified flow is a new page with a different structure, so scripts built for the classic Registration and Attendee Details steps won't carry over automatically.
This affects any script that relies on the classic page layout, such as conversion and analytics tracking tied to a specific step (Google Tag Manager, Meta Pixel, LinkedIn Insight Tag), scripts that fire when an attendee reaches or completes the Registration or Attendee Details step, and scripts that read, pre-fill, or validate specific form fields.
To switch without losing tracking or functionality:
Take stock of your current scripts. List every script added for the event's registration page and note what each one does.
Prepare new scripts for the unified flow. Update or rewrite each script to work with the Attendee Information step. Your Customer Success Manager can help you identify what needs to change.
Request the switch. Contact Accelevents Support or your CSM to enable the unified flow.
Add the new scripts and test. Replace the old scripts, then run a test registration to confirm tracking and any custom behavior work as expected before promoting the event.
💡 Tip: Create a duplicate event and have the unified flow enabled in that event, then test your new scripts in that event. This way you're not disturbing any flows, especially if registration is already open.