What is the difference between ticket bots and scalpers?

A scalper is a person or business that buys tickets to resell them at a profit. A ticket bot is software that buys at scale. Some scalpers buy by hand, and some individual buyers use bots for their own purchases. A defence has to address the automation and the evasion of purchase limits, whoever is behind them.

The two terms describe different things: one is a business model and the other is a tool. Scalping, also called touting, existed long before online sales. A scalper needs access to tickets at face value and a market where demand exceeds supply. How the tickets are obtained is a separate matter.

Many scalpers work without software. They employ people to buy across several devices, hold many payment cards and memberships that give presale access, and use friends' and relatives' details to multiply purchase limits. Professional brokers may hold season tickets or have arrangements that give them inventory directly. None of this involves a bot, and bot detection alone does not address it.

Bots are the tool that lets a small operation act like a large one. One attacker with the right software can run hundreds of sessions, each with its own account and address. The same software is sold or rented to others, so the person using it may have little technical skill. Some buyers who only want tickets for themselves use these tools too, because they believe it is the only way to get through.

The law in several places follows this distinction. Rules that target bots, such as the US BOTS Act, prohibit getting around a ticket seller's security measures and purchase limits. The Federal Trade Commission has described that law as covering circumvention by people as well, for example through fake identities. Rules on resale itself, such as price caps or disclosure duties, are separate and vary by country. Ask counsel which apply to your events.

For a ticket seller, the distinction shapes the response. Automation is addressed with detection, queue design and protection of the purchase APIs. Evasion of limits, by hand or by software, is addressed by linking accounts through device, payment and address. The resale incentive is addressed with ticket delivery, transfer and resale policies. Measuring each separately helps: the share of sessions that were automated, the share of orders linked beyond the limit, and the share of tickets that appeared on resale sites.

How Kairal helps

Session linking connects recorded devices, IPs and sessions to the user IDs your integration supplies. Compare those visits with your own account and order records before acting; a device match does not establish that two people are the same person.

Session linking