A same-URL split test on a VSL (video sales letter) page: 70% of visitors keep seeing the current page (the control) and 30% see a long-form version, while the ads keep pointing at one unchanged link. You set it up in the page's events, publish it, and read the result on purchases, with statistical significance computed for you.
New to A/B testing? Read the full guide first: split testing landing pages under one URL covers why one URL matters for paid traffic, sample sizes and how to judge a test. Unfamiliar term? The glossary explains it in a sentence or two.
You need two versions of the page: the one that runs today and the variant. In this tutorial they are the demo brand's Vitality VSL — control and Vitality VSL — long-form.
1Open the page's events
In Pages, search for the page your ads already point to and click its lightning icon (Page Events). The canvas opens with a Funnel Entry Point: every visit to this page starts there.

2Add a Split Test node
Click Add Node and pick Split Test. It arrives with two Traffic Distribution nodes, one per variant, at 50/50. The name fields are empty for now; you fill them in step 4.

3Connect the entry point to the split
Drag the two variant nodes apart so the graph reads left to right. Then drag from the Funnel Entry Point's output pin (the connector on its right edge) to the Split Test's input. From now on every visit goes through the split.

Faster way: drag from a node's output pin and release on empty canvas. The node picker opens, and the node you pick is created already connected to that output. Step 5 uses it.
4Name the test and set the traffic split
Give the test and each variant a name you will recognise in the report, such as A — control and B — long-form. Then set % of traffic, the traffic split: type 70 on the control and the other variant takes the remaining 30. New visitors are assigned in a fixed rotation that follows those percentages, not a random draw, so the split holds from the first visits.
Sending most traffic to the page that already sells limits the cost if the variant is worse, but it is slower. The 30% arm collects visitors at 3/5 the pace of a 50/50 arm, so reaching the same number per variant takes 1.67 times as long. The bigger control arm makes up part of that: for the same statistical power, a 70/30 test needs about 1.2 times the total traffic of a 50/50 test.

5Point variant B at the new page
Drag from variant B's output pin and release on the canvas. In the picker, choose Load Another Page: it is created already connected. Select the long-form page. Variant A has nothing after it, so its visitors keep seeing the current page.

6Publish
Click Publish. The Split Test node now shows the test as live, with Pause test and View results, and each variant gets a Mark as Winner button.
What counts as a conversion: a purchase. The report divides the sessions that bought by all sessions for each variant, and each order is credited to the variant the buyer was shown. The metric a winner is picked on is Primary Metric in the Split Test node's Advanced Settings (Winner Selection tab), Conversion Rate by default.

7Read the result
Open Split Tests and click Results on your test, or View results on the node. A new test needs traffic first, so the clip shows the same two pages after a 30-day run on the demo brand, split 65/35 (the report shows the traffic each arm actually got, 66.5/33.5):
- A (control): 5,493 sessions, 181 purchases, a conversion rate of 3.30%
- B (long-form): 2,764 sessions, 112 purchases, 4.05%
Conversion Comparison shows B at +23.0%, and Statistical Significance marks it Not Sig.: the p-value is 0.079, and the confidence interval for the difference runs from −0.12 to +1.63 points, so it includes zero.
B is ahead, but a test this size can't confirm a lift like that. Detecting 3.30% → 4.05% at 95% confidence and 80% power takes about 9,900 sessions per variant (check it in the sample size calculator). At this page's 275 or so sessions a day, that is about 10 weeks at 50/50. So plan the sample before launch, run the test to it, or test a bigger change that needs fewer visitors. The split testing guide explains how to plan it.
Min Sample Size per Variant (Advanced Settings, 1,000 on this test) is not that number. It is only the point below which the report flags a result "interpret with caution". Set it to the sample your test actually needs.

Common mistakes
- Leaving the entry point unconnected. The split never runs, and every visitor sees the control.
- Changing the ad at the same time. Change one thing per test, or you cannot tell what moved the result.
- Stopping at the first good-looking p-value. Decide the sample size before launch with the sample size calculator and enter it as Min Sample Size per Variant in the Split Test node's Advanced Settings (ElasticFunnels flags results until each variant reaches it). Run at least one full business cycle, and judge the result at the planned sample size, not the first time p dips below 0.05.
- Judging on clicks. Clicks to the checkout don't pay. Read buyers (the Customers column) and Net EPC per variant: the Results page shows both in the variant table, and Net EPC again in the EPC Comparison card.
- Building the variant at a new URL for the ads. That edits the ads and resets their learning. Keep one URL and let Load Another Page swap the content.
Keep going
Why same-URL testing matters for paid traffic, and how many visitors a test needs: Split testing landing pages under one URL. Everything the split test engine does, including section-level tests: landing page split testing. Letting an AI agent read the results and propose the next test: AI A/B testing. Plan the sample before launch: A/B test sample size calculator. Terms explained: the glossary. All tutorials: the Academy.