Remember: Both pages must also have the Confirmation Page Header Script installed. See Confirmation Page Header for setup instructions.

That's it for setup. The AEvent header script on your registration page automatically reads the matching parameter from the URL and includes it with the registration. No HTML editing is needed.

Append the parameter to your registration page URL for each traffic source. Examples:

Each registrant will be tagged with whatever value appears after origin= in the URL they used.

For more details on query string capture, see How to Capture Custom Fields & Values from the Query String.

For the origin value to appear in your CRM, you need to map the custom field in your integration settings.

You can then use this field in your CRM for:

Beyond your CRM, you can use AEvent's Audience feature to segment registrants by their origin value and trigger different actions for each group.

Once you have audiences for each variation, you can attach different Timeline Actions to each one. For example:

For more on creating audiences, see Introduction to Creating a Custom Audience.

The key idea: each AEvent campaign has its own WTL (Webinar Timeline) value. Your registration page's header script is tied to one campaign by default, but adding ?wtl= to the page URL reroutes that registration into a different campaign — same page, different campaign behind it.

Set up Campaign A and Campaign B as two separate campaigns, each with whatever you want to test (different timeline, emails, presentation, or replay). Make sure both campaigns have an upcoming event scheduled — the override only loads if the target campaign has a next event.

Open Campaign A in the builder and look at your browser's address bar — the WTL is the value shown in the URL. Copy it into a notepad, then repeat for Campaign B. For a full walkthrough, see Looking for your WTL Value?

Install Campaign A's registration header script on your page as normal. With no parameter added, the page registers people into Campaign A.

Take that same page URL and make two versions, one per campaign:

Arm A: https://yourpage.com/register?wtl=CAMPAIGN_A_WTL

Arm B: https://yourpage.com/register?wtl=CAMPAIGN_B_WTL

Anyone who lands via the Arm B link registers into Campaign B instead — the dynamic dates and times on the page automatically switch to Campaign B's next event too. Campaign A keeps working normally.

AEvent does not rotate traffic for you — you point half your traffic at each link. Use your ad platform's built-in URL rotation, a link-rotator tool, or your funnel builder's split-URL feature. To keep a single public link, place a rotator in front of the page that sends each visitor to one of the two ?wtl= URLs.

Visit each link, register a test email, and confirm the registrant landed in the correct campaign (check each campaign's leads). This is the single most important thing to verify before sending live traffic.

Optional — tag each arm: add an origin custom field (Method A or Method B above), for example split_test = a / b, so every registrant carries which arm they came from into your CRM and audiences for easy side-by-side comparison.

Can I do this without adding ?wtl= to my page URL? No — the parameter must be present in the URL when the page loads, because the header script reads it the moment the page renders. There is no AEvent-native traffic splitter. You do not have to hand people two different links, though: keep one public link and place a rotator in front of it. Important — the rotator must redirect to the ?wtl= URL before the page loads. A script that appends ?wtl= after the page has already rendered is too late, and the registration defaults to Campaign A.

Does the split happen on landing, or when someone registers? On landing. When the page loads with ?wtl=B, AEvent renders Campaign B's page and any registration there goes to Campaign B. There is no submit-time random assignment — so this is a 50/50 split of visitors, not of registrants. For measuring which campaign performs better, an even visitor split is exactly what you want: you compare conversion and downstream results between the two arms. Because both arms share the same registration page, registrations tend to come out roughly even anyway. One thing to watch: if the two campaigns' next events are timed very differently, the countdown shown can nudge conversion — keep their event timing comparable for the cleanest test.

Does this affect the join URLs? No. Each registrant's join URL is created per registration and bound to the event they actually registered into. Someone who registers via ?wtl=B becomes a normal Campaign B registrant with Campaign B's join link, emails, and replay — and the same for Campaign A. The WTL only decides which campaign at the moment of registration; after that, each person flows entirely through that campaign's own pipeline, and the two never cross over.

What is the difference between the "Custom Forms" and "Query" field types?

Custom Forms creates a hidden field with a value you hard-code into the HTML. Use this when you have separate pages and want to bake the value directly into the form code. Query creates a field that automatically reads its value from the URL parameter. Use this when you want the value to come from the link the registrant clicked.

Can I split test the webinar presentation itself, not just the registration page?

Yes. Use the campaign-level split test approach with the WTL parameter (see the Advanced section above). Create two campaigns with different timelines or presentations, and split traffic between them using different WTL values in the URL.

Can I send each split-test arm to a different confirmation (thank-you) page?

By default, every registration on a campaign lands on that campaign's single Confirmation Page, no matter which arm the registrant came from. There are two ways to send arms to different thank-you pages:

How many custom fields can I have per campaign?

AEvent supports up to 10 custom registration fields per campaign. This limit is shared across all custom fields (origin tracking, UTM parameters, and any other custom data you capture).

Does this work with evergreen and recurring campaigns?

Yes. Custom registration fields work the same way for live, evergreen, and recurring campaigns. Each registrant is tagged with their origin value regardless of which session they register for.

Can I automate actions based on which page someone registered from?

Yes, in two ways. In AEvent, create Audiences based on the custom field value and attach different Timeline Actions to each audience. In your CRM, build automations that trigger based on the custom field value (e.g., "if page_origin equals facebook, add to Facebook Leads workflow").

What if the registrant's URL does not include the query parameter?

If you use Method B (Query type) and the registrant visits the page without the parameter in the URL, the field will be empty. The registration still completes normally. You can filter for empty values in your CRM to identify registrants who came from an untagged source.

Can I use this with UTM parameters I am already tracking?

Yes. Create separate Query-type fields for each UTM parameter you want to capture (utm_source, utm_medium, utm_campaign). Each one counts toward the 10-field limit. For more details, see How to Capture Custom Fields & Values from the Query String.