Run a split test on your lander
Change a headline, button or image in the visual editor and show it to part of your traffic, without re-uploading.
On this page5 sections
A content test changes text, images or sections on the live page for a share of visitors, and compares registrations against the original. To test two uploaded designs against each other instead, use a version test.
- A published version of the lander. The editor works on the live page.
- Enough traffic to learn something. Bottega won't call a winner before each variant has at least 100 sessions, and a test usually needs at least a week so every weekday is counted.
- No other test running on the same page. Only one test can run per page at a time.
Name the test
Say what changes, like “Hero headline, result vs pain”. Add a Hypothesis if you like, then select Continue.
Choose Content
Select Continue.
Pick the page and the goal
Page is the page to test, usually Main page (/). Goal is what counts as a win. Pick Registrations in most cases, CTA clicks for pages that send people elsewhere to register, or Bonus claims to test the WhatsApp bonus.
Select Create and open editor
Bottega sets up the Original and Variant B with a 50/50 split. Nobody sees Variant B until you start the test.
The editor shows your live page. Make sure Variant B is selected in the tabs at the top, then click anything on the page. Switch between desktop and mobile with the device buttons, and use Interact when you need to click through the page normally, for example to open the form.
Change text
Double-click text on the page to type over it, or edit it in Text in Variant B on the right.
Swap an image
Click the image, then pick another image from your upload or paste a link in Image in Variant B.
Hide a section
Click the section and turn on Hide in Variant B to test a shorter page.
Save
Every change is listed under Changes in Variant B, where Revert undoes one. Select Save in the bar at the bottom.
To test more ideas at once, add another variant with the + next to the variant tabs and set the shares under Traffic split. They must add up to 100%. More variants need more traffic before a result is clear.
Select Start test at the top of the test page. The status changes from Draft to Running.
- Each visitor is placed in one variant and keeps seeing it on return visits for 90 days.
- The change is made on the server before the page is sent, so visitors never see the original flash first.
- Bots always see the original and aren't counted.
- Pause shows everyone the original until you select Resume.
Avoid editing a variant after the test starts. Saved edits reach visitors within a minute and mix into the same results. For a new idea, finish the test and start another.
| What you see | Why | What to do |
|---|---|---|
| “Not in the page's HTML (probably added by a script), so visitors won't see this change.” | The element is created by a script after the page loads, so the server can't change it. | Change it in your files and upload a new version instead. |
| A note that the element matches several elements in the HTML and only the first one changes | Several elements look the same to the editor. | Give the element an id in your HTML, or accept that only the first one changes. |
| “Another test is already running on this page.” | One running test per page. | Pause or finish the other test first. |
| “Every variant needs at least one change.” | A variant is identical to the original. | Open the variant and make a change, or delete it. |
Read next
Something here out of date? Tell us and we'll fix the guide.