You can put your AEvent registration form on almost any page builder or custom-coded site, and it will still populate live session times, swap in dynamic dates, and register people into your campaign. The trick is that AEvent's embed is TWO pieces of code, not one, and both have to be in place for the form to work.
Overview
Your AEvent campaign generates two blocks of code for every registration form: the Form Registration Code (the form itself) and the Header Script (a small loader that goes in your page's <head>). This guide covers where to find both, where each one goes on the popular page builders, how to show only the next available session, and how to confirm it all works on your live page.
If you use GoHighLevel, start here for the concepts, then see our Go High Level Page Builder Setup and GoHighLevel guides for the GHL-specific screens.
Prerequisites
An active AEvent account on any plan.
A campaign already created in your AEvent dashboard.
Edit access to the external page where the form will live (page builder or custom site), including the ability to add code to the page's header/tracking-code area.
Step 1: Open your campaign's registration code
From your dashboard, open your campaign and click Code in the left sidebar, then select the Registration sub-tab. You will see two code boxes side by side: Form Registration Code on the left and Header Script on the right.
You should see: two boxes labeled Form Registration Code and Header Script, each with its own Copy button.
Step 2: Pick your page builder first
Before you copy anything, set the Page builder Type in the top-right of the Code panel. Click it and choose your builder from the list (ActiveCampaign, ClickFunnels, GoHighLevel, Groovepages, Hubspot, Kajabi, Kartra, Leadpages, OntraPort, SamCart, Basic HTML, and more), then click Update. This matters because the generated code is tailored to how your builder handles template tags.
Why it matters: AEvent's dynamic date and time values are template tags. For most builders (GoHighLevel, ClickFunnels 2.0, Shopify, ActiveCampaign) the tags use a single brace, like {!webinar-webinar1id}. For WordPress, the tags use a double brace, like {{!webinar-webinar1id}}. Choosing the correct builder generates the right brace style, so the tags resolve to real dates instead of showing up as literal text.
You should see: the Page builder Type label now shows the builder you selected, and the code in both boxes updates to match.
Step 3: Paste the Form Registration Code
Click Copy on the Form Registration Code box, then paste it into an HTML/embed element on your registration page where you want the form to appear. Keep the field names intact (for example name="webinarid") so the loader can find and populate them.
You should see: a registration form with your fields (name, email, and a session selector) appear in your page builder's editor.
Step 4: Paste the Header Script into your page's head
Click Copy on the Header Script box and paste it into your page's header/tracking-code area. This script is the loader that swaps AEvent's template tags for real session times and IDs at page load. Without it, the tags stay as literal text and the form cannot register anyone.
Where the header code goes depends on your builder:
GoHighLevel: go to your funnel's Settings > Tracking Code > Head. Add it at the funnel level (not just inside a single HTML element).
WordPress: add it to the page's
<head>using your theme's header option or a header-injection plugin. Remember WordPress uses double-brace tags.Webflow / custom-coded sites: paste it inside the
<head>tag of the page, in your page or site-wide head settings.ClickFunnels, Kajabi, Kartra, Leadpages, and other builders: use the page's header/tracking-code or custom-code-in-head setting.
You should see: the header code saved in your builder's head/tracking-code area for the registration page.
Step 5: Show only the next session (optional)
By default a multi-session campaign renders a session selector (a dropdown) in the form so registrants can pick a time. If you want to offer just one time, you can present a single next-available session as text instead of a dropdown. The loader auto-trims empty session slots, so a form built with several slots will only display the sessions that are actually scheduled.
You should see: the session selector shows only real, upcoming sessions, with any empty placeholder slots removed automatically.
Step 6: Verify on the live published page
Publish your page, then open the live public URL in a browser. Do not test in your builder's preview or editor mode. The Header Script only runs on the published page, so the builder preview will almost always show unresolved tags even when everything is set up correctly.
The live published registration page: the session selector is populated with real resolved dates. This example uses the radio field type; a dropdown looks the same but as a select menu (see the field-type note in the Troubleshooting section).
You should see: real session dates and times in the dropdown or on the page, and a successful registration when you submit a test entry.
Troubleshooting
The form shows blank or literal tags like
{!webinar-webinar1}: the Header Script is missing or not being detected on the published page. Confirm you pasted the Header Script into the page's head/tracking-code area (not just an on-page HTML element), that it is saved at the correct level (for GoHighLevel, funnel-level Settings > Tracking Code > Head), and that you are viewing the live published URL, not the builder preview.Only two options appear in the session dropdown: this is expected. The loader auto-trims empty session slots, so the dropdown only shows sessions that are actually scheduled.
Radio buttons instead of a dropdown (or vice versa): the field type is set in your AEvent Form Builder (select vs radio). Change it there and re-copy the Form Registration Code.
Broken images or missing icons on your form: you likely copied the AEvent hosted-page HTML instead of the generated embed. Use the Form Registration Code and Header Script from Campaign > Code > Registration, and make sure your Page builder Type is set correctly.
For the concept overview and the JavaScript popup alternative, see Registration Form Code, Header, and Integration with your Page.