The registration form

Paste this where the form should appear:

<sw-webinar-form data-webinar-id="ID"
                 data-button-text="Save my seat"
                 style="--sw-webinar-form-button-background: #ff5438"></sw-webinar-form>

The id identifies the webinar; the dashboard hands you the snippet with it in place. The element is drawn by the site tag, so the tag has to be installed on the page (Settings → Site tag) — without it, nothing appears. The page the form is on has to be on a domain your organization allowed (Settings → Site tag → Allowed Domains) — the id alone opens nothing. Nor does anything appear while your organization is not served — suspended, locked, or with no plan: the API answers the form, the A/B test and the site tag’s page view 403 ORGANIZATION_UNAVAILABLE.

An A/B test goes in the webinar’s place, with data-ab-test-id="ID" instead of data-webinar-id: the form is drawn as the webinar the test deals the visitor’s browser, which keeps that webinar for every form and player of the test it meets. The test’s page in the dashboard hands you this snippet too. Both attributes written, the webinar’s stands. While the test is inactive nothing is drawn: the API answers 410 AB_TEST_INACTIVE.

Which fields are on, which are required and the schedule the sessions on offer are computed from come from the dashboard, and changes there show on your page without touching the snippet. Everything else is written on the element — the snippet the dashboard hands you carries what you set in the webinar — and you can change any of it by hand. When you edit the webinar’s form, copy the snippet again.

The form offers the next times of the webinar’s schedule and always shows them in the visitor’s own time zone, their device’s. On a live, a session is one moment for everyone. On an evergreen set, in the dashboard, to use each registration’s time zone, the schedule’s hours are read in the visitor’s own zone instead — a session at 15:00 is at 15:00 wherever they are. That is the webinar’s setting, not the snippet’s: a snippet that still carries data-use-webinar-registration-timezone (or data-use-attendee-timezone) still draws, and the attribute is ignored.

Sparkwebinar does not accept registrations more than 90 days ahead, so the form offers only times within them: a date or a time further off is not shown until it comes within 90 days, and a form left open brings it in as it does. With nothing within them, the form says no session is available, as it does with none left.

Attribute	What it does
data-schedule-limit	How many sessions it offers at most. Absent, 3.
data-hide-required-mark	Required fields do not show the *.
data-<field>-label, data-<field>-placeholder	A field’s words, for name, email, phone, schedule, timezone. Empty, none.
data-button-text	The button’s words.
data-fields-order	email,name: these first, in this order, the rest after.

The look is the --sw-webinar-form-* custom properties, set on the element or on anything around it: the font family and text colour, the labels’ colour, weight, size, case and spacing, the fields’ background, text and border colours, weight, size, corners and shadow, the button’s colour, text colour, hover colour, weight, size, case, spacing, corners and shadow, and the form’s own background and corners.