AEvent does not have a built-in split testing feature, but its custom registration field system makes it straightforward to track which page, funnel, or traffic source each registrant came from. This gives you the data you need to compare performance across variations.
Two methods are available:
Method A: Hard-Coded Hidden Value. Best when you have two different landing pages or funnels. You embed a different value on each page.
Method B: Query String Capture. Best when you use one page but send traffic from different sources. The value is pulled from the URL automatically.
Both methods tag each registrant with an origin value that flows into your CRM and into AEvent's audience system, so you can filter, segment, and compare results.
Method A: Hard-Coded Hidden Value
Use this when you have two (or more) separate registration pages and want to tag each one differently.
Step 1: Create a Custom Registration Field
Open the campaign you want to split test.
Go to Registration settings.
Click Add Registration Field (top right).
Name the field something descriptive. Examples:
page_origin,split_test,lead_source. This name is for your internal tracking only; registrants will not see it.Select Custom Forms as the field type.
Click Add.
Step 2: Copy and Customize the Form Code
Go to the Code tab in your campaign.
Copy the Registration Form code.
In the HTML, locate the hidden input field near the bottom. It will look something like this:
<input type="hidden" name="customtag" value="">
For Page A, set the value to identify that page:
<input type="hidden" name="customtag" value="page-a">
For Page B, paste the same form code but change the value:
<input type="hidden" name="customtag" value="page-b">
Embed each version on its respective landing page using an HTML element or code block in your page builder.
Remember: Both pages must also have the Confirmation Page Header Script installed. See Confirmation Page Header for setup instructions.
Step 3: Test Your Setup
Register through Page A using a test email.
Register through Page B using a different test email.
Check your CRM or AEvent lead records to confirm each registration carries the correct origin value (
page-aorpage-b).
Method B: Query String Capture
Use this when you have one registration page but want to track different traffic sources, ad campaigns, or link variations.
Step 1: Create a Custom Registration Field
Open the campaign you want to track.
Go to Registration settings.
Click Add Registration Field (top right).
Name the field to match the URL parameter you want to capture. For example:
origin,utm_source, orsource.Select Query as the field type.
Click Add.
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.
Step 2: Send Traffic with Different URL Parameters
Append the parameter to your registration page URL for each traffic source. Examples:
Facebook ads:
yourpage.com/register?origin=facebookEmail campaign:
yourpage.com/register?origin=email-promoGoogle ads:
yourpage.com/register?origin=googlePartner referral:
yourpage.com/register?origin=partner-john
Each registrant will be tagged with whatever value appears after origin= in the URL they used.
Step 3: Test Your Setup
Visit your registration page with a test parameter:
yourpage.com/register?origin=test123Complete a test registration.
Check your CRM or AEvent lead records to confirm the origin value
test123was captured.
For more details on query string capture, see How to Capture Custom Fields & Values from the Query String.
Mapping the Field to Your CRM
For the origin value to appear in your CRM, you need to map the custom field in your integration settings.
Go to Integrations in your campaign settings.
Click the Settings gear icon on your CRM/ESP integration.
Under Custom Fields, click Create Single Field and select your origin field.
AEvent will create the corresponding field in your CRM and pass the value on every new registration.
You can then use this field in your CRM for:
Filtering contacts by origin to compare conversion rates
Building automations (e.g., "if origin equals facebook, add to Facebook Leads workflow")
Reporting on which traffic source produces the highest attendance and engagement
Analyzing Your Results in AEvent
Beyond your CRM, you can use AEvent's Audience feature to segment registrants by their origin value and trigger different actions for each group.
Create an Audience Based on Origin
In your campaign, go to the Audience tab.
Click Create Audience.
Set the condition: Custom Field > [your field name] > matches >
page-a(or whatever value you used).Save the audience.
Repeat for each variation (
page-b,facebook, etc.).
Use Audiences for Different Actions
Once you have audiences for each variation, you can attach different Timeline Actions to each one. For example:
Send a different follow-up email to registrants from Page A vs Page B
Apply different CRM tags based on traffic source
Track attendance and engagement rates per audience in your analytics
For more on creating audiences, see Introduction to Creating a Custom Audience.
Advanced: Campaign-Level Split Tests
If you want to test entirely different webinar presentations, timelines, or email sequences (not just different registration pages), you can run two separate AEvent campaigns and split traffic between them.
Using the WTL Parameter
AEvent's wtl (Webinar Timeline) parameter lets you override which campaign a registration goes to, even from the same page.
Create two campaigns with different timelines, emails, or presentations.
Find each campaign's WTL value (see Looking for your WTL Value?).
Send half your traffic to:
yourpage.com/register?wtl=CAMPAIGN_A_WTLSend the other half to:
yourpage.com/register?wtl=CAMPAIGN_B_WTL
Each group registers into a different campaign with its own timeline, email sequences, and post-event actions. You can then compare performance between the two campaigns in your analytics.
Tip: You can combine WTL with an origin field (Method B above) if you also want to track traffic source within each campaign.
Tips and Best Practices
Name fields clearly. Use descriptive, lowercase names with underscores:
page_origin,lead_source,utm_source. Avoid spaces or special characters.Keep values consistent. Decide on a naming convention upfront (e.g.,
facebooknotFBorFacebook Ads). Inconsistent values make filtering difficult.Maximum 10 custom fields per campaign. Plan your fields carefully. You can track origin, UTM source, UTM medium, UTM campaign, and more, but they share the same 10-field limit.
Use Dynamic Confirmation Page URLs to route registrants from different sources to different confirmation pages. See Dynamic Confirmation Page URL.
Test before launching. Always register through each variation and verify the origin value appears correctly in your CRM and AEvent lead records before sending live traffic.
Frequently Asked Questions
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.
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.