TicketingAvailable with Expose
Keep tickets for fans.
At on-sale, bots grab seats and hold them in carts while fans see “sold out”. Label every session in the queue and at checkout, and rate-limit the automation holding your inventory.
For ticketing platforms and venues selling high-demand events.
Where 50,000 tickets went at on-sale
- Tickets on saleTickets on sale: 50,000
- Cart sessionsCart sessions: 120,000
- Tickets held by automationTickets held by automation: 3,000
- Inventory tied upInventory tied up: $240,000
Human 90%Agent 1%Bot 7%Unknown 2%
Where money is affected
Held seats are unsold seats.
Bots hold tickets in carts to resell or to block. Fans give up, and seats released late often go unsold or to resellers.
Agents buying a ticket for a real fan are not the same thing. Expose labels them separately so your rules can tell the difference.
The real picture
On-sale, two ways.
Illustrative example Hypothetical figures; your own numbers will differ.
Your numbers
What it could mean for you.
Replace the example with your own figures.
- Inventory tied up
- $240,000
- Tickets held by automation
- 3,000
Inventory tied up = tickets × share held by automation × ticket price.
Illustrative example Your numbers, not a promise. Savings depend on the decisions you make with the evidence.
An example decision
One cart at on-sale.
- Session
- bot · confidence high
- Cart
- 8 tickets, block C
- Policy
- Rate-limit likely bots
- Hold
- Released to the queue
The seats go back to the fans waiting in line.
How it fits
From evidence to a decision.
- 01
Install the script
Paste the snippet on queue and event pages.
- 02
Pick the profile
data-profile="ticketing" protects carts and checkout.
- 03
Set your limits
Choose how hard to rate-limit likely bots.
- 04
Watch the on-sale
See humans, bots and agents live in HQ.
What your team can do
Act on it, your way.
Rate-limit holds
Slow likely bots adding many tickets.
Release inventory
Return held seats to the queue sooner.
Let fan agents buy
Tag agents buying for a real fan.
Before you start.
Will fans be blocked?
No. People are not challenged by default; likely bots are rate-limited.
What about agents buying for fans?
They are labelled as agents, separately from bots, and can still buy.
Does this stop resale?
No. It limits automated holding at on-sale; resale rules are yours.
What about sessions you cannot classify?
They stay unknown, and are not counted as bots.
Set up for Ticketing
Fans first. Scalpers flagged.
Catch checkout bots during on-sales, with tighter thresholds where it matters.
checkout | Lower thresholds |
Everything else is tagged, never blocked, unless you say so.
What you get
Tighter at checkout
Checkout uses lower thresholds, so automation is caught sooner.
Site profilesA gate on the server
requireHuman guards the purchase route and allows verified agents if you want them.
Verify tokens on your serverLate verdicts reach you
If a verdict changes after checkout, the Debrief webhook tells your server.
Debrief webhookAgents told apart
An agent buying for a fan is labelled Agent, not lumped in with scalper bots.
Verdict
Where the label goes
Other covers
- E-commerceHonest conversion rates. Agents can still check out.
ecommerce - SaaSA clean trial funnel and fewer fake accounts.
saas - Content and mediaReal readership. Agent traffic, named.
content - Fintech and paymentsStep-up instead of deny. The verdict rides on the payment.
fintech - Lead generationA cleaner CRM and honest cost per lead.
leadgen
Available with Expose