Virtual conference registration page: fields, layout and capacity
Quick answer: A virtual conference registration page should show the dates with time zone, the agenda by track, the speakers and the cost before the form, then ask only for name, email, session choices and access needs. Set a cap or waitlist if your platform license limits attendance, and keep the confirmation email purely transactional.
- Show dates, hours, time zone, agenda by track, speakers and cost before the form.
- Ask only for name, email, session choices and access needs; label every field.
- Google's event rich results do not cover online-only events, so the page must stand on its own.
- Set a registration cap or waitlist if your license limits attendance.
- Keep the confirmation email transactional and send promotion separately.
Why registration matters more for a conference
For a one-hour webinar, registration is a name and an email. For a virtual conference, the registration page does three jobs at once. It sells a multi-session program, it sorts people into sessions or tracks, and it collects the information you need to run the event well, such as access needs and time zone.
Search behaves differently for online conferences too. Google's event rich results do not support virtual-only events: its documentation says virtual experiences with no real-world component are not supported and that events must take place in a physical location (Google event structured data). A fully online conference will not get the event listing treatment a ticketed in-person show might, so the page itself, its title and its links carry the weight. If your conference is hybrid, Google also asks that each event has its own unique URL.
What to put above the form
Visitors decide in the first screen. Give them:
- The promise. One sentence on who it is for and what they will leave with.
- Dates, daily hours and time zone, with a second zone for your largest audience if they differ.
- The agenda by track. A short grid of session titles. Link to the full agenda rather than pasting it all.
- Two to four speaker photos with names and roles.
- Cost and access. Free or paid, and whether sessions can be watched later.
- One registration button or the form itself, visible without scrolling on a phone.
Traffic will come from flyers, banners and emails; virtual conference promotion covers those pieces. Every one of them should land here, not on a homepage.
Which fields to ask for
Ask for what you will use, and nothing else.
- Name and email. Many platforms count attendees by unique email address, so one person with two addresses can count twice.
- Session or track choices. A short checklist lets you size rooms and send track-specific reminders.
- Time zone, only if your system cannot detect it.
- Access needs. The W3C's event accessibility checklist asks organizers to find out speakers' and participants' accessibility requirements (W3C Making Events Accessible). An optional free-text question works.
- Optional: organization and role, if sponsors or your sales team will use them, and you say so.
Label every field. W3C form guidance says to provide labels for all form controls, place them above or to the left of fields (to the right for checkboxes), and keep labels visible on mobile because most users need them (W3C form labels tutorial).
Building the page in six steps
- Write the promise and the agenda grid before touching the page builder.
- Draft the form with the fields above, and remove anything you cannot name a use for.
- Set capacity rules. Decide whether you need a cap, a waitlist or approval. Microsoft Teams events let organizers set how many people can register, require manual approval, add a waitlist and set registration start and end times.
- Write the confirmation page. Repeat the dates and time zone, add calendar buttons, and tell people where the join link will arrive.
- Write the confirmation email. Keep it transactional: details, join link, calendar file. Under the FTC's CAN-SPAM guidance, a message whose subject line or opening content is promotional is treated as commercial, which brings in extra requirements.
- Test on a phone. Register yourself, pick two sessions, and check the confirmation, calendar entry and reminder.
Worked example: a library consortium's two-track conference
Picture a made-up consortium of public libraries running a one-day virtual conference for staff, with one track on digital services and one on community programs.
Its page opens with the promise, "One day of practical sessions for library staff, from e-lending to teen programs," then the date with Eastern and Central times. Below that sits a two-column agenda grid and four speaker photos. The form asks for name, work email, a checkbox for each track, and one optional question: "Do you need captions, an interpreter or materials in advance?"
The consortium's platform license has a fixed number of seats, so the program manager sets a registration cap and a waitlist instead of letting sign-ups run over. The confirmation page repeats the date and has calendar buttons for Google, Outlook and Apple. The confirmation email contains only the event details and join instructions, and the consortium sends its newsletter promotion separately.
Costs and time
A focused registration page takes about a day to write and build in most page builders, plus time for a mobile test. Platform costs depend on how attendance is counted. On Zoom Events' pay-per-attendee plan, unique attendees are counted by email and each attendee above your prepaid seats costs $2.50. Free events on that plan can register more people than expected, but paid events cannot oversell, and once the license's attendance limit is reached, no further unique attendees can join.
Mistakes to avoid
- Hiding the time zone or the daily hours below the form.
- Long forms. Every optional field you add costs sign-ups; ask the rest after registration.
- Placeholder text instead of labels. Placeholders vanish as people type and are hard to read.
- No plan for capacity. If your license caps attendance, set a cap or waitlist before the page goes live.
- Promotional confirmation emails. Keep the confirmation transactional and send marketing separately.
- Expecting a Google event listing for an online-only conference.
For comparison, see the shorter pattern used in virtual event registration and landing pages and the hands-on format in online workshop registration pages.
How BrightStage AI handles registration
BrightStage AI gives every event registration and thank-you pages that you can split-test with A, B and C versions, so you can compare two promises or two layouts on real traffic. "Suggest" buttons fill event fields such as the title and description with AI, at 1 credit per click. After someone registers, reminders go out by email, text and web push on desktop and Android, and a Join window lets them join in the browser or install the app. Registrants can also flow to AWeber, Mailchimp, GetResponse, Klaviyo or Kit through key-based connections. For help with the copy itself, see how to write landing page copy with AI.
Sources
- Event (Event, EventSeries) structured data (Google Search Central)
- Labeling Controls (W3C WAI Forms Tutorial)
- Making Events Accessible: Checklist for meetings, conferences, training, and presentations (W3C WAI), 2022-08-31
- CAN-SPAM Act: A Compliance Guide for Business (FTC)
- Using the Zoom Events Pay-Per-Attendee plan (Zoom Support)
Frequently asked questions
What should a virtual conference registration form ask?
Name, email, which sessions or tracks the person plans to attend, and an optional question about access needs. Add organization or role only if you will use it and say why.
Will my virtual conference show up in Google's event listings?
Probably not if it is online-only. Google's event structured data documentation says virtual experiences with no real-world component are not supported.
How do I handle a virtual conference that fills up?
Set a registration cap and a waitlist if your platform supports them. Teams events, for example, let organizers cap registrations, require approval and run a waitlist.
Can I add promotions to the registration confirmation email?
Keep them out of the subject line and the opening. The FTC treats a message with promotional subject lines or leading content as commercial, which brings in CAN-SPAM requirements.
Related playbooks
- Virtual event registration and landing pages: a build guide →
- Online workshop registration form and landing page: what to include →
- Virtual conference flyer, banners and ads: how to promote a conference →
- Virtual conference platforms: software for large groups and avatars →
- How to host a virtual conference: planning steps and hosting services →
- All Virtual conference playbooks →
Written by Alan Magliocca, founder of BrightStage AI and AIVX Labs (Podavinci LLC). Written with AI assistance and checked against the linked sources. Follow along: LinkedIn · YouTube · TikTok · X · Facebook · Instagram · Skool community
