Registration & formsEmbeddable form

Embeddable form

You can embed an event’s registration form on your own website instead of sending visitors to the hosted Novex page. The embedded form posts straight into the same registration list.

When to use this

Use the embed when you want registrations to happen in the flow of your own site — on a landing page, a campaign site, or inside your CMS — while still collecting into Novex.

There are two related public surfaces:

  • Embedded registration — the event form rendered for embedding via /r/<tenant-slug>/<event-code>/register/embed.
  • Standalone form token — a tokenized form URL (/f/<tenant-slug>/<form-token>) you can link or frame directly.

How to embed

The Public registration card on an event: the registration form's own link with a Copy button, and beneath it an "Embed on your website" panel holding a two-line snippet — a div carrying the tenant and event codes, and a script tag — with its own Copy button.

The snippet is a <div> carrying your tenant slug and the event code, plus one script tag. Copy it from here rather than typing it — the event code has to match exactly.

  1. Open the event’s Registration settings and find the Embed option.
  2. Copy the embed snippet (an <iframe> pointing at the embed URL).
  3. Paste it into your website’s HTML where you want the form to appear.
  4. Publish your page. Submissions appear in Registrations just like hosted sign-ups.

Tips & limits

The registration form as it renders inside the embed: salutation, full name, email, company, job title, country, mobile number, city, ticket type, a marketing-consent tick, a "Verify you are human" challenge, and a Save my seat button — no site header or footer around it.

The embedded form renders on its own, with no page chrome around it, so it drops into your layout. It carries the same built-in fields and the same human-verification step as the hosted page.

  • Sizing: give the iframe enough height for the longest state of the form (validation messages add height). Test on mobile down to small screens.
  • Branding: the embedded form carries your event branding; make sure the surrounding page styling doesn’t clash.
  • One form per event: the embed reflects the same fields as the hosted page, so you only maintain the form in one place. The built-in required fields — including job title and company — are enforced here exactly as they are on the hosted page.
  • Confirmation: after submit, the embedded flow shows its own confirmation state rather than navigating your whole page away.

Next