In development. This is on the roadmap and not available yet. The guide is here so it is ready the day it ships.
Marketing & Automation

Test Two Versions of a Page

Show visitors different headlines and calls to action, then see which version actually sells more tickets.

3 min readUpdated 2026-07-29

Two people can describe the same event in two honest ways, and only one of them fills the room. A kirtan night can be framed as an evening of chanting and community, or as a chance to settle a restless mind — both true, but they don't pull the same visitors toward the ticket button. Page testing on BrightStar settles that argument with visitors instead of opinions. You write more than one version of a headline or a call to action, visitors are split between the versions, and you find out which one actually turns interest into tickets sold, rather than guessing which wording sounds better to you or to whoever is standing over your shoulder when you write it.

How a test works

You define the variants yourself — a different headline, a different call to action, a different way of framing what the gathering is. BrightStar assigns each visitor to one variant and keeps them with it, so a person who lands on your retreat page sees the same wording whether they buy right away or come back that evening to finish deciding. That consistency matters more than it looks: if a visitor's experience shifted partway through their decision, you would have no way of knowing which wording actually shaped it. Their behaviour — whether they go on to buy a ticket — gets recorded against the specific variant they were shown, and that link between a wording choice and an outcome is the entire reason the test is worth running.

What to change, and what to leave alone

The headline and the call to action are the highest-leverage places to start, because between them they carry most of a visitor's decision to buy or move on. But it's important to change one of them at a time. If the headline and the call to action are both different between two variants, and one variant sells more tickets, you have no way to say which change caused it — the wording that actually mattered and the wording that was just along for the ride look identical in the results. A test only tells you something usable when the only difference between the two versions is the one thing you're trying to learn about.

Running a test you can actually trust

A useful test has a shape to it. Skipping a step is usually how organizers end up with a result that feels meaningful but isn't.

  1. 1Pick one element — the headline or the call to action — and hold everything else on the page still.
  2. 2Write two honest versions of that one element, each one a real description of the gathering, not a stretch.
  3. 3Let visitors be split and assigned to a version automatically, so no one's experience changes mid-decision.
  4. 4Wait until each version has drawn real traffic before you look at the comparison — a handful of visitors on either side isn't a result yet.

Reading the result

The measure that matters is conversion, not traffic. A variant that pulls in more clicks because its headline is more provocative can still lose, if fewer of those visitors go on to actually buy a ticket. Picture a festival gate page that promises something dramatic — it might draw curious clicks from people who were never going to attend, while a plainer, more accurate description sells more tickets to people who were already close to deciding. Conversion tells you which wording matched the people who complete a purchase, not which wording is more attention-grabbing in isolation. A page that gets looked at is not the same as a page that gets someone through the door.

It's tempting to check the numbers after a day and call a winner, especially when one version pulls ahead early. But a small early lead across a handful of visitors on each side is noise, not a result — it's how organizers talk themselves into a change that doesn't actually help. Let the test accumulate real traffic on both sides until the gap between them means something, then act on what the numbers show once they've settled, not on what they showed on the first day.

Common questions

Can I A/B test my BrightStar event page?

Page testing on BrightStar lets you write more than one version of a headline or call to action and split visitors between them, then compare which version leads to more ticket sales. Each visitor is assigned one variant and stays with it, so what gets measured is a consistent experience rather than a page that changes under them.

Read more

The reason each visitor stays locked to one variant is that mixed exposure would make the comparison meaningless — you'd never know whether a purchase was influenced by the headline they first read or a different one they saw later. Keeping the experience consistent per visitor is what makes the difference between the two versions attributable to the wording itself, rather than to chance or confusion.

What should I test first on an event page?

The headline and the call to action are the highest-leverage places to start on a BrightStar page, because they carry most of the decision. Test one thing at a time — if two elements change at once, a difference in ticket sales cannot be attributed to either of them.

Read more

Changing more than one element at once is the most common way a test stops being useful, even when it produces a clear-looking winner. If the headline and the call to action both differ between versions, a stronger result tells you that something worked, not which of the two changes worked — so the lesson you take away for next time is a guess again, not a finding.

How do I know which version won?

By conversion rather than traffic. A BrightStar page test records visitor behaviour against the variant that visitor saw, so the comparison is which version turned visits into ticket sales. A variant that attracts more clicks but sells fewer tickets has not won.

Read more

Clicks tell you about curiosity — someone was interested enough to look. A completed ticket purchase tells you about commitment — someone decided this gathering was worth showing up for. A headline that's more dramatic can win on the first measure and lose on the second, which is exactly why conversion, not traffic, is the number worth trusting.

How long should I run a page test?

Long enough that the difference is not noise. A small early lead across a handful of visitors on each side tells you nothing reliable, and acting on it is the most common way organizers talk themselves into a change that does not help. Let the test accumulate real traffic before you call it.

Read more

Early results are volatile because a few visitors can swing a percentage wildly in either direction — a handful of unrelated purchases can make either version look like the clear winner. The gap between versions needs enough traffic behind it to stop bouncing around before it means anything, which is a matter of patience more than a fixed schedule.

Ready to get started?

Create your first event on EveryEvent Rio de Janeiro — it’s free.