Give Every Campaign Its Own Page and Keep the One That Sells

Send Each Audience to a Page Made for Them

An extra landing page, called an alternative view in your dashboard, is a second page for the same event at its own address. Give one to a stage or a genre, a sponsor's listeners, an artist's fans or one ad campaign, and each audience lands on a page that speaks to them. Every order is still an order for your event, from the same ticket types and the same capacity, so your door list, payouts and reports stay together.

Note what each page is for in its purpose field, so your team knows which one went to the sponsor and which one runs behind the Instagram ads. Buyers never see it. Each page has an address ready for your ad, email or sponsor post, and a preview so you see what buyers will see before your event is published.

Choose an extra page when the audience is different and the night is the same. When a night has its own capacity, its own door list or its own payout, it works better as a separate event, which you can duplicate from this one.

• Alternative views: extra pages for the same event
• Its own address: ready to copy into an ad, email or post
• Purpose: a note for your team, never shown to buyers

• Create extra landing pages for your event

Change the Name, Dates and Artwork for Each Page

Give a page its own event name, dates, venue details, flyer, background, logo or description, and leave everything else as your main event page shows it. A sponsor page can carry the sponsor's name and artwork, and an artist page can lead with the headliner. Each page carries a flyer and a description in each of your event's languages.

• Its own name and dates: speak to the audience the page is for
• Its own artwork: flyer, background and logo for each page
• Every language: a flyer and description for each one

• Build an Event Page That Turns Visitors Into Ticket Buyers

Offer Each Audience the Right Tickets

Each page sells the ticket types you pick, such as a sponsor ticket only the radio listeners can buy, or the bass stage tickets for the bass stage crowd. Show in main event decides whether a ticket also appears on your main event page or belongs to that page alone.

A page can sell a ticket nobody else sees, such as a listener price or a crew rate, while every ticket still draws on your event's capacity and reports.

• Tickets for each page: the ticket types that page sells
• Show in main event: keep a ticket on your main event page too

• Set up ticket types

See Which Page and Which Link Sold the Tickets

The Alternative Views tab of your Performance report shows the tickets and revenue from each page beside Main Event, so you know which campaign or sponsor brought in the most. For the posts, emails and posters that send buyers to the same page, a tracking link for each one lets you compare the visits, orders and revenue each link earned.

Each tracking link has a short address and a QR code for posters and flyers, and the table opens with your busiest link first. Copy table puts the whole table on your clipboard for a spreadsheet.

• Sales by page: tickets and revenue for each page and the main event
• Tracking links: clicks, orders and revenue for each placement
• Download QR: the same link on a poster or flyer

• Track which promotion sells your tickets
• Know How Your Tickets Are Selling at Any Moment

Test Two Event Pages Against Real Buyers

Two versions of an event page can both look right, and only one of them sells more tickets. Test a new flyer, a different description or a line-up page against the page you use today. Your current page is the control, each extra landing page can be a variant, and every visitor keeps seeing the version they first saw.

Choose Conversion rate when the question is how many visitors buy, or Revenue per visitor when the question is how much each visit is worth. Then choose how many of your visitors take part. Everyone outside the test sees your normal event page, so you can start small and widen the test once you trust it. Weights split the test visitors between versions, so a weight of two gives a variant twice the visitors of a weight of one.

• Your extra pages as variants: one or more pages against your current one
• Weights: how the test visitors split between versions
• Share of visitors: from a small sample to every visitor

• Run an A/B test for your event

Test the Answers Buyers See at Checkout

A buyer at the pay button may still have one question, such as whether they can transfer a ticket or what happens if the date moves. Add those questions and your answers to a checkout variant, and they appear below the pay button for the buyers in that variant. The results show whether answering them brings in more revenue.

Each variant carries its own questions and answers. The control leaves checkout as it is, and you can add more variants to compare different sets of answers in the same test. A checkout test and an event page test can run on the same event at the same time.

• Answers below the pay button: where buyers make up their mind
• More than one variant: different sets of answers in one test

• Get the Details You Need From Every Buyer and Lose Fewer Sales

Keep the Winner With Confidence

Results shows the visitors, conversions, conversion rate, revenue and revenue per visitor for every version, with the time the figures were last updated. In a conversion rate test, Ticket Fairy marks a variant as the winner once its lead over the control is statistically significant, so you know the difference is real before you act on it.

A paused test shows visitors your normal page and keeps the results you collected, and resuming carries on the same test. Once you have your answer, conclude and archive it, and the results and the record of what buyers saw stay with the event for your team. Send every visitor after that to the version that sold, and start a new test for your next idea.

• Winner badge: shown once the lead is statistically significant
• Every figure for every version: visitors, conversions, revenue and revenue per visitor
• Concluded tests kept: what buyers saw and how each version did

Ask Fai to Build Pages and Run Your Tests

Tell Fai, the assistant inside your dashboard, which audience a page is for, and she creates it with its own address, name, dates, description and tickets, including whether each ticket stays on your main event page. Tell her what you want to test, and she drafts the experiment, shows you the versions and the visitor split, and starts, pauses or concludes it when you say so.

Fai asks you to approve every page and every change before she makes it, and reads the latest version of a test first, so she never overwrites a teammate's newer change. She can list your extra pages, change or delete one, and compare the results of a running test in plain words. Flyers and backgrounds for a page go up from the dashboard.

• Pages drafted by Fai: address, name, dates, description and tickets
• Tests run by Fai: drafted, started, paused and concluded
• You approve each change: nothing starts until you say so

• Get Your Ticketing Work Done by Asking Fai