There are two ways to register people for an eWebinar: point them at the eWebinar-hosted registration page, or install the Embedded form widget on a page you built yourself. Both go through the same registration API and apply the same anti-bot checks; the difference is where the form lives.
eWebinar's hosted registration page
Every eWebinar has a public registration URL at your registration-page subdomain (or on your custom domain). eWebinar designs, renders, and hosts the page — you configure the copy, theme, and form fields inside the editor.
- Best for: teams who want a webinar page without building one.
- Pros: nothing to install; styling is inherited from the webinar's theme; the registration-page UI is maintained by eWebinar.
- Cons: the page lives at an eWebinar URL (unless you have the custom-domain add-on) and you can't layout the surrounding content yourself.
The Embedded form widget
The Embedded form widget is the register form itself, rendered inline inside a page you built. You get the same reCAPTCHA and email-validation that the hosted page has, but the surrounding page is yours.
- Best for: custom landing pages built in your CMS (Webflow, WordPress, HubSpot, etc.) where the form is one section among many.
- Pros: your page, your brand, your analytics — the register action still comes through eWebinar.
- Cons: you're responsible for the rest of the page's design and copy.
Both protect against bots and bad addresses
Using the hosted page or the Embedded form gives you:
- reCAPTCHA to block bot registrations.
- Email verification at registration time, so the addresses you collect have a higher deliverability rate than a plain HTML form would.
When you should not use either
If you want to capture registrants outside of eWebinar (for example from a LeadPages form), you can auto-register via Zapier instead of using the hosted page or the Embedded form.