I've reviewed a lot of event landing pages in client portals over the years. Most of them fail in the same 2 or 3 ways.
A HubSpot event landing page needs three things above the fold to convert: the date and time, a form under four fields, and a thank-you page that does something. None of that is about design. The page is usually pretty enough. What's missing is one of those three, and it's rarely obvious to whoever built it.
So here's the full build, in HubSpot, the way I'd do it for a client. If you want the wider picture first, running events in HubSpot is a separate guide.
The page has one job
Get a registration. Everything on the page either helps that or gets in the way.
A visitor decides in seconds. They need 3 answers fast: what is this, when is it, and is it worth my time. Put all 3 above the fold, with the form or a button that jumps to it.
The amount of scrolling between a visitor and the form should embarrass you slightly. I keep seeing event pages that open with a full-screen hero image and a brand statement, date buried 3 scrolls down, and every one of those scrolls gets paid for in registrations, because closing a tab is easier than hunting for a date.
What changes by event format
The job stays the same whatever the format. Where it splits is the header block.
For a webinar you want a format badge, the platform, and the date and time with a timezone. And don't put the join link on the page itself. That goes in the confirmation email once someone's registered, otherwise you've just published your Zoom link to anyone who finds the page. I've seen it done.
In-person is mostly geography. Venue name, full address, something about parking or access. "Arrive from 6pm, event starts at 6:30" saves you a dozen emails asking whether people can get in early. A map embed helps too, assuming it points at the right building, which I mention because I've had to fix one that didn't.
Hybrid needs both, plus a format choice on the form, because "attending in person" and "watching from a laptop in Reading" are different registrations with different logistics behind them, and if you skip the choice you'll end up finding out who's coming which way from a spreadsheet someone builds by hand after the fact.
Get the format wrong here and everything downstream inherits the confusion. Confirmation email, reminders, the day itself.
The build, step by step
1. Start from a landing page, not a website page
In HubSpot, create a landing page rather than a website page, and strip the header and footer modules. Every link that leads away from the form is a door out of the room, and a standard site nav is 5 or 6 doors, wide open.
2. Write the header block first
Event name, one line on why it matters, date and time with timezone, format, and location or platform.
For webinars, the timezone matters more than you'd think. I've watched a UK company lose a chunk of US registrants who assumed EST and found out at 2pm that they'd missed it. Nobody complained, either. They just didn't register for the next one.
If you run events for a European or global list, write the timezone out in full rather than trusting people to convert it in their head. "3pm BST / 10am ET" costs you 4 words.
3. Build the form
Three fields: name, email, company. Stop there unless sales genuinely needs more.
HubSpot's own research backs this up. A 2024 HubSpot study measured roughly a 4% drop in conversion per additional form field, and separate benchmark data shows the real cliff sits between 5 and 7 fields, where each one costs closer to 3 points. That's the whole argument for stopping at three.
If most registrants are already contacts, turn on progressive profiling and let HubSpot swap in new questions for known people instead of asking everyone from scratch. While you're in there, add hidden fields for source and campaign tracking. Attribution reporting gets a lot easier when you capture that at registration instead of reconstructing it afterward from wherever the data half-lives.
4. Add the body content
Agenda with rough timings. Speakers with real photos, not a LinkedIn export from 2019 if you can help it. A short paragraph on who the event is for, which does more filtering work than any amount of copy about how great it'll be.
Don't bolt on a fake urgency banner, "only 3 spots left," if that isn't true. It reads as true the first time and as a lie every time after, once someone notices the same banner on your next 4 events.
5. Create the thank-you page
The most skipped step, and the cheapest win.
It should confirm the details and hand over an add-to-calendar link. One next step too, a related resource or a speaker's LinkedIn, nothing more than that. HubSpot won't generate the calendar file for you, so create an ICS file and link it here and in the confirmation email. There are free ICS generators online if you don't want to hand-build one, or your event tooling may already produce one per event.
Keep this page's messaging in sync with the confirmation and reminder emails that follow it. A confirmation email that contradicts the thank-you page 30 seconds later undoes whatever you just got right on the page.
6. Check it on a phone
Half your traffic, sometimes more, arrives from a LinkedIn post or an email, on mobile. The form, the date, and the register button all need to survive a small screen on a real connection, not just a wide desktop preview.
HubSpot's preview does this in 2 clicks. People still skip it. Tap targets that feel fine on a laptop trackpad turn into 3 attempts on a phone, and most people quit somewhere in the second.
7. Set the social image
When the page gets shared, the og:image is the ad. A branded card with event name, date, and speaker faces, sized at 1200x630, will outperform whatever HubSpot picks by default from the page. Set it explicitly in the page's social settings rather than trusting the auto-pull.
Before you hit publish
Once, on a client site, the confirmation email went out with last month's Zoom link still in it. Nobody caught it until a registrant did. The team had checked the page 3 times. The email, never. Different asset, different editor, same event.
Worth a 10-minute pass before anything goes live:
- Submit the form yourself and check the confirmation email and thank-you page match
- Open the ICS file and confirm the date, time, and timezone are right
- Check the page on a phone, not just HubSpot's preview pane
- Confirm the og:image renders when you paste the link into Slack or LinkedIn
After the event, the page still exists
Set a reminder for this, because nobody remembers it on the day.
Once the event's done, the page should redirect to the recording, swap its form for a "watch on demand" version, or point at the next event. A live registration form for something that happened last Tuesday is a small, ongoing credibility leak, and search engines will keep sending people there for months.
On-demand pages are quietly productive. A webinar page that keeps converting registrations for 6 months afterward often beats the live number, which is a strange thing to say out loud but I've watched it happen enough times to trust it.
The part that gets old fast
One page, built carefully, takes a couple of hours. Fine.
Then it's every event. Clone the page, the form, the thank-you page, the confirmation email. Rename all of them. Update the date in 5 places, the timezone, the speakers. The cloning itself is quick, 10 minutes maybe. The mistakes are what cost you, and they're always the same mistake: one asset in the chain still holding last month's details.
At a handful of events a year, you live with it. Past that, it's worth automating. This is what we built EventEngine for: you create the event record in HubSpot and it generates the landing page, registration flow, and comms from that single source, so the date only exists in one place and can't drift. It runs on HubSpot Professional and Enterprise, at $249/month with a 30-day free trial, though the page-generation piece specifically needs Content Hub Pro, not just any Professional subscription.
Either way, build the manual version at least once. You'll know exactly what your event pages need, and what any tool you buy later should actually be doing for you.
Common questions
Does a HubSpot event landing page need site navigation?
No. Build it as a HubSpot landing page, not a website page, and strip the header and footer modules. Every link that isn't the registration form is an exit. A page with 6 nav links open is 6 ways for someone to leave before they register.
How many fields should a HubSpot event registration form have?
Three: name, email, and company. HubSpot's own research found conversion drops sharply once a form passes 5 fields, with roughly a 4% loss per additional field. Ask for anything else later with progressive profiling instead of upfront.
What should the thank-you page after registration do?
Confirm the event details, hand over an add-to-calendar (ICS) link, and offer one next step, like a related resource or a speaker's LinkedIn profile. A blank "thanks for registering" page wastes the one moment someone's actually paying attention.
Does an in-person event need a different landing page than a webinar?
Mostly the same page, different header block. In-person needs a venue name, address, and parking or access notes instead of a platform badge. Hybrid events need both, plus a way for the registrant to pick a format on the form itself.
What happens to a HubSpot event landing page after the event ends?
It shouldn't keep collecting registrations for something that already happened. Redirect it to the recording, swap the form for an on-demand version, or point it at the next date. A live form for a past event is a small, ongoing credibility problem.
