Don't Look Back in Error: Oasis Sold Out 42 Stadium Shows Without a Single Public Onsale

Oasis sold every ticket for its 42-date Live '27 tour without holding a public onsale at all. Fans had to register by 17 September, were picked at random, and received a personal code valid for one city and one of nine windows across 25 to 27 September. Every date sold out. Some approved buyers were still stopped by bot detection.

That last sentence is the one worth pinning above your desk, because it is the part every organiser will eventually meet. The tour is a stadium rock act rather than a trade show, but the architecture is the same architecture a conference uses: a registration layer in front, a payment layer behind, and a quiet assumption that the two of them are talking to each other.

What did Oasis actually build?

A lottery with a locked door. There was no general onsale and no separate public presale, which BroadwayWorld reported alongside the full sold-out date list. Registration was the only public route to a ticket.

Fans registered in advance and could name up to three preferred cities. Successful registrants were randomly assigned exactly one. Each of them got a personal, non-transferable code that worked for their assigned city and their assigned window only, and the email address on the buyer's Ticketmaster account had to match the address used at registration. For the UK shows that produced nine separate selling windows spread over a Friday, a Saturday and a Sunday rather than one enormous simultaneous scramble, with a slice of inventory at each price level allocated to every window.

The registration itself ran on Openstage, whose Ticket Unlocks product page describes exactly this shape: fans register on a branded page the organiser controls, registrations are screened using "identity and behavior signals" to filter bots and large-scale resellers, selected fans get personalised access to the ticketing partner, and the organiser afterwards sees who redeemed and who did not.

The demand signal arrived early enough to change the tour. Oasis expanded Live '27 from 38 shows to 42 before a single ticket had been sold through the process, which means the decision rested on registration volume rather than on completed purchases. That is a genuinely useful thing to be able to do, and it is the strongest argument for the whole design.

So why did approved fans still hit a bot blocker?

Because the two gates were never introduced to each other. TicketNews reported that some selected buyers, holding valid codes, ran into error loops, failed payments and messages telling them their browsing had been paused because of unusual behaviour.

Those messages come from Ticketmaster's standard fraud and bot detection, which its own help documentation says can trigger on repeated refreshing or clicking, on traffic from a network shared by many people, on VPNs and privacy tools, and on browser extensions. The Live '27 event pages told buyers to switch those things off before the window opened, which is a reasonable instruction and also a quiet admission that the second gate did not know the first gate had already cleared you.

So the buyer had registered, survived a screening process built to remove automated and fraudulent sign-ups, been selected, received a unique code, and logged in on a matching email address. Then a separate system, run by a different company, assessed their clicking speed from scratch.

Registration did not remove the friction. It decided who was allowed to experience it.

What the registration was also doing

Openstage sells Ticket Unlocks as bot defence, and it also sells it as an audience asset. Its published material promises registration counts by city before an onsale, identification of fans likely to travel or to buy premium access, and the capture of email, SMS, location, demographics and purchase history so that "every on-sale builds on the last". Its Oasis Live '25 case study claims 99.95 per cent of tickets reached real fans.

None of that is sinister and all of it is on the record, but it reframes what the gate is for. A queue turns demand into a number. A registration layer turns demand into a list of named people you can contact next year. For a touring act that is a marketing asset. For a conference organiser it is simply your database, which you already had, which is why the B2B version of this story is less about acquisition and more about drop-off.

What this means for event organisers

Three things, and none of them require a stadium.

First, every gate has a conversion cost, and the costs stack. If you run registration, then conditional routing, then a payment step with its own fraud rules, you have three places to lose a delegate who was going to pay you. Test the whole chain end to end as one journey, not three features. Attendee routing is worth building precisely because it lets you send people down shorter paths, not longer ones.

Second, you need to be able to see who was stopped. Openstage's pitch includes redemption data for a reason: knowing who was invited and did not buy is the difference between a follow-up campaign and a shrug. If your registration tool and your checkout are different systems, insist on being able to reconcile the two lists. On this tour, the question of how many legitimate buyers were caught by security interventions is still open, which is a bad place for an organiser to be.

Third, a sell-out is the moment your platform's pricing model shows its hand. Nine windows, 42 stadium shows and a registration list in the millions is an extraordinary amount of transaction volume, and on a percentage-based platform every one of those transactions is revenue for two businesses. Only one of them booked the venue.

Where eventcloud sits in this

Honestly, a little to the side of it. eventcloud does not run ballots, virtual waiting rooms or fan-verification screening, so a stadium onsale of this shape is not what it is built for. It is an in-person registration and ticketing platform for conferences, trade shows, summits and corporate events, where the gate is a registration form and an access code rather than a lottery.

What does carry across is the money. A seat on eventcloud is $125 a month, flat, with unlimited events, unlimited tickets and unlimited registrations on it, and payments run through the organiser's own Stripe account. The price is the same whether a window moves 500 registrations or 50,000, because your sell-out is not a billing event.

The honest edges, since they matter more than the pitch. You pay per user, and you can start with one. There is no white-label add-on to buy at any price, and the enterprise page sets out how branding is handled instead. eventcloud does not do virtual or hybrid events. If most of your programme happens on a screen with a production gallery behind it, Bizzabo or vFairs will serve you better.

If the registration layer is the part you are rethinking, our event registration tools are the place to start, and the pricing page shows what a busy year costs, which is the same as a quiet one.