How to Setup a Split Test

Creating A/B Page Variants in Humblytics

A/B (or split) testing lets you compare two versions of a page and prove—statistically— which one performs better. Humblytics makes the workflow dead‑simple: pick a goal, drop in two URLs, choose how visitors are assigned, and hit Start Experiment.

---

Step‑by‑Step Instructions

1. Start a New Experiment

In the left hand menu choose Split Testing and click Start New Experiment.

2. Set Your Testing Goal

Choose what success looks like for this test. Humblytics offers two main goal types:

Conversion Goals:

Goals	What it Tracks
Form Submission Event	Tracks when users complete specific forms (newsletter signups, contact forms, etc.)
Click Event	Tracks when users click specific buttons or links (CTAs, downloads, etc.)
Page View Event	Tracks when users visit specific pages or trigger custom page view events
Purchase Event	Tracks successful purchases or transactions (ecommerce conversions)

Page Goals:

Goals	What it Tracks
Reach Destination Page	Tracks when users visit a specific internal or external page

Destination Page Goal Setup

The Reach Destination Page goal tracks when users navigate to a specific page. This goal type supports both internal and external destinations:

Internal Pages (Same Domain) For pages on your own website, simply enter the page path:

• /thank-you - tracks visits to your thank-you page

• /pricing - tracks visits to your pricing page

• /signup - tracks visits to your signup page

External Pages (Different Domain) For pages on external domains, enter the complete URL. Important: This only registers as a conversion if the user visits the external page directly from your site.

✅ Tracks: Your site → External page ❌ Doesn't track: Your site → Third-party page → External page

Examples of external destination pages:

• https://checkout.yourdomain.com/complete - separate checkout domain

• https://calendly.com/yourcompany/meeting - external booking page

• https://app.thirdparty.com/signup - external signup flow

Simply enter the full URL in the destination page field when setting up your goal.

Advanced: Cross-Domain Event Goals

For more complex cross-domain tracking scenarios, you can use cross-domain events as split test goals instead of simple destination page tracking. This is especially useful when:

• You need to track specific interactions on external sites (not just page visits)

• The conversion flow involves multiple steps across domains

• You want to track custom events that happen after reaching an external page

How It Works:

1. Set up cross-domain event tracking on the external site using Humblytics.trackPageView(), Humblytics.trackFormSubmission(), or Humblytics.trackClickEvent() with the domain parameter

2. Create a split test and choose the appropriate event goal type (Page View Event, Form Submission Event, or Click Event)

3. Specify the event name that matches your cross-domain tracking implementation

Example Scenario: Instead of tracking just "reached checkout page" you can track "completed checkout process" even if the checkout happens on an external domain:

// On external checkout domain
window.Humblytics.trackFormSubmission("checkout-complete", {
  domain: "yourmainsite.com",
});

Then set your split test goal to track the "checkout-complete" form submission event.

Benefits of Cross-Domain Event Goals:

• Track the actual conversion action, not just page arrival

• Handle complex multi-step external flows

• Maintain attribution across domain boundaries

• Get more precise conversion data

For complete setup instructions, see our Cross-Domain Tracking & Whitelisting guide.

3. Name Your Experiment

Give it a clear and specific name (e.g., "Home Page Hero — Image vs Video"). This helps you find and report on it easily later.

4. Add Your Variant Pages

You'll need two (or more) live pages:

• Control (A): Your current version.

• Variant (B, C, etc.): The version you want to test.

Steps:

1. Build your variants in your site builder (e.g., Webflow, Framer, WordPress).

2. Change one key element only (headline, image, button color, etc.).

3. Copy the live URLs for each page.

4. Paste them into Humblytics under:

• Control URL

• Test Variant URL(s)

Optional: Add notes or your test hypothesis to stay organized.

5. Set Visitor Assignment

Option	How It Works	When to Use
Allow Visitor Overlap	Assignment happens on every session—a repeat visitor could see different versions on different visits.	High‑traffic sites, short tests, early ideation phases.
No Visitor Overlap	Assignment happens once per user (sticky)—they always see the same version.	Brand‑sensitive flows, long funnels, or when you need behaviour consistency.

6. Apply Optional Restrictions

• Geo Targeting: Run tests for specific regions or countries.

• Audience Filters: Exclude certain traffic types (e.g., only test on mobile or organic traffic).

7. Launch the Experiment

• Review everything

• Click "Start Experiment"

• Humblytics will begin splitting traffic—no extra code or setup needed!

---

Frequently Asked Questions

How do I build variant pages in Webflow, Framer, or custom‑coded sites? • Webflow: Duplicate the page, update content, publish. • Framer: Duplicate the Frame route, edit, publish. • Custom‑coded (React/Next.js, Rails, Laravel, plain HTML): Copy the page template or branch, adjust the element you're testing, deploy it at a unique path (e.g., /home‑alt).

Keep the Humblytics global script in the <head> so tracking continues seamlessly.

No extra tracking snippets are needed—Humblytics' global script captures all variants automatically.

What if I need to pause or edit a live test? Navigate to the Split Testing list, click the ••• menu, and choose Stop. Data collected so far is preserved.

Will the test slow down my site? No. Humblytics routes visitors server‑side after initial request; the 36 kb script is defer‑loaded and never blocks rendering.

---

Happy testing! Measure, learn, and iterate with confidence using Humblytics.