Pre-queue registration asks shoppers to verify an identity, an email, a login, or a phone number, before the sale opens, and gives each verified person one place in line. Bots that cannot verify do not get a queue number at all, which beats trying to spot them after they are already in line.
Why the gate has to move earlier
A queue that opens to everyone at the same moment is a queue that bots have already won. The bots are faster, they run in parallel, and they hold more places than any human can. By the time the queue spots them, the damage is done: the places are taken, the inventory is gone, and the real customers are staring at a sold-out page. The gate has to move earlier, to before the drop opens, where the bots have to verify an identity to get a place at all.
DataDome measured the scale in a midnight ticket sale: 31 percent of the waiting-room traffic was bots, and one in three spots went to a bot before real customers had a chance. That is not a rounding error. It is a third of the inventory, gone to accounts that were never going to use the tickets. A queue that lets everyone in and then tries to sort them out is a queue that has already lost a third of its stock.
Related reading on this site: Home and Shopify Drop Bot Defense: The Queue, the Challenge, and the Cancel cover the neighbouring problems in more depth.
One place per identity
Registration ties the queue place to a verified identity, and the rule is one place per identity. The identity can be an email address, a login, or a phone number, but it has to be verified before the sale opens, and it has to be one place. A bot farm that wants a hundred places has to verify a hundred identities, and that costs time and money per account. The cheap bots drop out. The determined ones pay more for every place they take.
The verification has to be real, not a checkbox. An email verification that sends a code and waits for it back is a real check. A login that requires an existing account with a purchase history is a real check. A phone number that gets an SMS code is a real check. A checkbox that says I am not a robot is not a check, it is a speed bump, and the bots have already learned to drive over it.
What registration costs you
Registration adds friction, and some shoppers will not bother. That is the tradeoff, and it is worth naming honestly: a queue that is easy to join is a queue that is easy to game, and a queue that is fair is a queue that asks something of the shopper. For a scarce drop, fairness usually matters more, because an unfair queue loses customers permanently. A shopper who loses a drop to a bot does not come back for the next one.
The way to keep the cost low is to open registration early and keep it open long. A registration window that runs for a week before the drop gives every shopper time to verify, and it gives the system time to check the identities. A registration that opens an hour before the drop is a registration that only the bots will complete, because the bots are the ones watching the clock. Early and long is the version that works.
Frequently asked questions
What is pre-queue registration?
A step before the sale where shoppers verify an identity, usually an email address, a login, or a phone number, and receive one queue place per verified identity. Unverified traffic never enters the queue.
Does registration stop bots?
It stops the cheap ones, which are most of them. A bot farm has to verify an identity per queue place, and that costs time and money per account. It does not stop a determined operator with many verified identities, but it raises the price of every place they take.
Will registration hurt real customers?
It adds friction, and some shoppers will not bother. The tradeoff is between a queue that is easy to join and a queue that is fair. For a scarce drop, fairness usually matters more, because an unfair queue loses customers permanently.
How is registration different from a CAPTCHA at entry?
A CAPTCHA tests whether the visitor is human at the moment they join. Registration tests identity before the sale opens, and ties the queue place to that identity for the whole session. The two work together: registration limits places per person, the challenge checks the visitor is human.