# Run an A/B test for your event | Ticket Fairy Guides

1. [Ticket Fairy](https://www.ticketfairy.com/)
2. [Guides](https://www.ticketfairy.com/guides)
3. Run an A/B test for your event

Setting up an event

# Run an A/B test for your event

Compare event pages or checkout answers, split visitors between versions and find which one brings in more ticket sales or revenue.

For:  Testing which event page or checkout message sells more tickets

Takes:  10 minutes

- [Open Experiments for the event](#step-1)
- [Name the test and choose what success means](#step-2)
- [Choose how many visitors take part](#step-3)
- [Choose the event pages to compare](#step-4)
- [Add the checkout answers to compare](#step-5)
- [Create the draft, then start it when it is ready](#step-6)
- [Compare the results before you conclude the test](#step-7)

## What you need before you start

- You have an owner or admin role for the event.
- For an event-page test, create at least one alternative page for this event first. Your current event page remains the control version.
- Choose one question to answer, such as whether a different event page brings more ticket sales or whether checkout answers increase revenue per visitor.

1. ## Open Experiments for the event

   Open your event, choose **Experiments**, then choose **New experiment**. The list shows where each test runs, its goal and whether it is a draft, running, paused, concluded or archived.

   You need an owner or admin role for this event. If Experiments is not in your event menu, ask an owner or admin to give you access.
          ![Ticket Fairy Experiments section showing draft, running, paused and concluded event tests](https://www.ticketfairy.com/embeds/posters/marketing-experiments--list.png)    Experiments, tests for an event page and checkout.
2. ## Name the test and choose what success means

   Enter a name your team will recognise. Under **Where it runs**, choose **Event page** or **Checkout**. Under **What you are optimising for**, choose **Conversion rate** when you want more visitors to buy, or **Revenue per visitor** when the value of each visit matters more. Enter your expectation if you want to record why you are running the test.

   Your expectation is a note for your team. It does not change how visitors are divided or how the results are calculated.
          ![Ticket Fairy experiment editor set to compare two event pages by conversion rate](https://www.ticketfairy.com/embeds/posters/marketing-experiments--event-page-setup.png)    Experiments, an event-page A/B test.
3. ## Choose how many visitors take part

   Enter a whole number from 0 to 100 under **Share of visitors in the test**. The weights divide only those visitors between the control and your variants. With 80% of visitors in the test and equal weights of 1 and 1, 40% see the control, 40% see the variant and the remaining 20% see your normal event or checkout without joining the results. With weights of 1 and 2, the second version receives twice as many test visitors as the first.

   A visitor stays with the same version throughout the test. This gives them a consistent experience when they return during the same visit.
4. ## Choose the event pages to compare

   For an event-page test, the control shows your current event page. Give the other variant a clear name, then choose one of this event's alternative pages. Choose **Add a variant** to compare another alternative page in the same test.

   An event-page test cannot run on an RSVP event because there is no ticket sale for this test to measure. Preview visits and embedded event pages do not join the test.
5. ## Add the checkout answers to compare

   For a checkout test, the control leaves checkout unchanged. In each variant, enter at least one question and answer. Buyers assigned to that variant see the answers below the pay button in Ticket Fairy checkout. Add more questions or variants when you have a distinct set of answers to compare.

   Checkout questions in an experiment appear in Ticket Fairy's hosted checkout. They do not change an embedded checkout or a checkout built with the React SDK.
          ![Ticket Fairy experiment editor comparing checkout questions and answers](https://www.ticketfairy.com/embeds/posters/marketing-experiments--checkout-questions.png)    Experiments, questions shown below the checkout pay button.
6. ## Create the draft, then start it when it is ready

   Choose **Create experiment**. You can reopen a draft to change its name, goal, visitor share or variants. When every version is ready, choose **Start**, review the confirmation and choose **Start experiment**. Starting saves any unsaved draft changes before the test goes live.

   Starting locks the experiment setup. For an event-page test, you can still edit your main event page, and you can still edit or delete alternative pages elsewhere in the dashboard. Once a test has started, do not edit or delete a page it uses, even while the test is paused. Conclude the test before changing those pages. The setup stays locked even if you pause it. Only one event-page test and one checkout test can run for an event at the same time.
          ![Ticket Fairy confirmation shown before an experiment starts and its setup is locked](https://www.ticketfairy.com/embeds/posters/marketing-experiments--start-confirmation.png)    Experiments, confirmation before a test starts.
7. ## Compare the results before you conclude the test

   Open **Results** to compare visitors, conversion rate, conversions, revenue and revenue per visitor for every version. A conversion means a visitor placed at least one paid order after seeing a version. More orders during the same visit do not add more conversions. Revenue stays separated by currency. The updated time tells you when the figures were last calculated.

   For a conversion-rate test, **Clear result** means the difference from the control is statistically significant. The dashboard marks a variant as the winner only when its conversion rate is both higher and statistically significant. For a revenue-per-visitor test, compare that figure for each version; the dashboard does not add an automatic winner badge. Choose **Conclude** when you have enough evidence to make your decision. A concluded test keeps its results and cannot resume.
          ![Ticket Fairy experiment results comparing visitors, conversions, conversion rate and revenue for two event pages](https://www.ticketfairy.com/embeds/posters/marketing-experiments--results.png)    Experiments, results for each version.

## Or have it done for you

Fai can create and edit a draft, start or pause a test, conclude it and compare the results. She reads the latest version first and asks you to approve every change. You can do the same work in the Experiments section of the dashboard.

### In your dashboard, with Fai

Find my event and help me create an A/B test. Ask what I want to test, whether it should run on the event page or checkout, and whether conversion rate or revenue per visitor matters most. Show me the complete draft and visitor split before asking me to approve it. Do not start it until I approve that separately

## Questions you might have

What is the difference between the control and a variant?:  The control is the event page or checkout you already use. A variant is the alternative page or set of checkout answers you want to compare with it.

What happens to visitors outside the test?:  They see your normal event page or checkout and do not appear in the test results. Set the visitor share to 100% when you want every eligible visitor included.

Can I run an event-page test and a checkout test together?:  Yes. An event can have one running event-page test and one running checkout test at the same time. Pause or conclude the running test before starting another test on the event page or in checkout.

Can I change a test after it starts?:  You cannot change the experiment setup after it starts. For an event-page test, you can still edit your main event page, and you can still edit or delete alternative pages elsewhere in the dashboard. Once a test has started, do not edit or delete a page it uses, even while the test is paused. Conclude the test before changing those pages, then create a new test for your next version.

What happens while an experiment is paused?:  Visitors see your normal event page or checkout. The results already collected remain available, and resuming continues the same test.

Why does the result say Not enough data yet?:  The test has not recorded enough visitors and conversions to compare that variant reliably with the control. Keep it running and check again after more visitors have taken part.

Does one conversion mean one order?:  No. A conversion means a visitor placed at least one paid order after seeing a version. If they place more orders during the same visit, the result still counts one conversion.

Can I use an event-page experiment for an RSVP event?:  No. Event-page experiments measure ticket sales, while an RSVP event takes registrations instead. You can run this test on an event that sells tickets.

Can I delete an experiment?:  You can delete a draft before it starts. Once it has started, conclude it and archive it so your team keeps the result and the history of what buyers saw.

Can Fai run an A/B test for me?:  Yes. Fai can create and edit the draft, start or pause it, compare the results, conclude it and archive it. She asks you to approve every change and reads the latest version before acting, so a teammate's newer change is not overwritten.

## Where to go from here

- [What else you can do with Ticket Fairy](https://www.ticketfairy.com/event-ticketing/features)
- [See how visitors find your event page](https://www.ticketfairy.com/guides/see-how-visitors-find-your-event-page)
- [How do you answer a custom ticket sales question?](https://www.ticketfairy.com/guides/answer-custom-ticket-sales-questions)
- [Make your event invitation-only](https://www.ticketfairy.com/guides/make-an-event-invitation-only)
- [Password-protect your event](https://www.ticketfairy.com/guides/password-protect-your-event)
- [Sell tickets by personal invitation](https://www.ticketfairy.com/guides/sell-tickets-by-personal-invitation)
- [Unlock hidden tickets with an access code](https://www.ticketfairy.com/guides/unlock-hidden-tickets-with-an-access-code)
- [Approve orders before buyers receive tickets](https://www.ticketfairy.com/guides/approve-orders-before-buyers-receive-tickets)
- [Schedule when your event goes live](https://www.ticketfairy.com/guides/schedule-when-your-event-goes-live)
- [Create a reusable event template](https://www.ticketfairy.com/guides/create-a-reusable-event-template)
- [Set up ticketing for a multi-day festival](https://www.ticketfairy.com/guides/sell-a-multi-day-festival)
- [Sell parking, camping and merchandise with your tickets](https://www.ticketfairy.com/guides/sell-add-ons-with-your-tickets)
- [Group your tickets into categories](https://www.ticketfairy.com/guides/group-your-tickets-into-categories)
- [Issue reusable event passes to crew and artists](https://www.ticketfairy.com/guides/issue-entry-passes-to-your-crew)
- [Every Ticket Fairy guide](https://www.ticketfairy.com/guides)

## Do this on your own event

Create your account, build your event and follow the steps in your own dashboard. You do not need to book a sales call.

  [Create a free account](https://manage.ticketfairy.com/welcome) [Book a demo](https://www.ticketfairy.com/event-ticketing/book-a-demo)

---

This page is on Ticket Fairy, a ticketing, marketing and operations platform for live events and the venues that host them: festivals, club nights, concerts, conferences and tours, and night clubs, beach clubs and concert venues. It grows revenue with fan rewards that turn an audience into a sales channel, and runs the money side with payments and payouts, Vault business banking, and working capital advanced against ticket sales. [How Ticket Fairy ticketing works](https://www.ticketfairy.com/event-ticketing) · [Ticket Fairy for AI assistants](https://www.ticketfairy.com/llms.txt)