Reading an alert card

When a monitor finds tickets it posts one card per find. The card is built to be read on a phone in about three seconds, because that is usually all the time you have. Here is a real layout, with every field explained underneath.

What arrives in Discord

A mock, not a screenshot: the same fields the engine actually sends, drawn in the browser so it stays honest when the card changes.

Field by field

Title

Found ticket(s) for <event> - the event name exactly as the site spells it, so you can search for it there without guessing.

Thumbnail

The event image from the listing. Useful for telling two fixtures apart at a glance.

Venue

Venue and city. Worth a look on multi-venue tours where the same event name repeats.

Date

Kick-off or doors, sent as a Discord timestamp: your client renders it in your own timezone, with a relative line underneath ("in 6 months"). If you are reading it abroad, that is why it does not match the venue's clock.

Price

The range across everything in this card, low to high. A single listing shows one number. Prices are face value as listed, before the site's own fees.

Quantity

Reads searched for N — the quantity this monitor is set to — and, where the site publishes one, the per-person ticket limit. It is what the monitor asked for, not a total of what it found.

Heading line

The first line of the card, for example 3 Tickets Found (Primary): how many listings are in this card, and which market they came from. Primary is the box office, Resale is another fan's listing, and a mixed card says Primary + Resale.

Listing lines

One per listing, numbered #1, #2, and so on, in the order the site returned them. A card holds up to ten; beyond that it says how many more there were, because Discord will not take a longer message.

Footer

Platform and the event id. Paste that id into a new monitor to watch the same event without hunting for the URL again.

Reading a listing line

#1  Clock End Upper (CU4)  •  Row 12  •  Seats 114-115  •  Qty 2  •  £72.00  •  Adult

• Block (code) - the human name of the stand or section, with the site's own code in brackets. The code is what the seat map uses, so it is the reliable half.
• Row - as printed. Some venues letter rows, some number them, and a few do both in different stands.
• Seats - the seat numbers in the listing. A range is contiguous; a comma separated list is not, which matters if you need to sit together.
• Qty - how many tickets in that listing. Many sites will not let you buy in a way that leaves a single seat stranded, so a Qty of 3 may only be sellable as 3, not 2 + 1.
• Price - per ticket, not the total.
• Resale and Buy - a resale listing says so at the end of the line and carries a Buy link straight to that listing. Primary listings have neither; use the card title, which links to the event page.
• Missing row or seats - general admission has neither, so those parts of the line simply are not there. It is not a gap in the data.
• Ticket type - in italics. This is the one people miss. Adult is unrestricted. Members only, Season ticket holder, Young Adult, Junior and Concession all have conditions, and buying the wrong one gets the order cancelled at the turnstile rather than at checkout.

What the card does not tell you

• Whether it is still there. The card records what existed at the moment we saw it. On a busy release a listing can be gone in seconds.
• Fees. Booking and delivery fees are added at checkout and vary by delivery method.
• Whether you are eligible. Ballot, membership and away-scheme restrictions live on your account, not on the listing.

Duplicate cards

You get one card per new find. If the same listing is still there on the next poll, it is not re-posted. A second card for a block you have already seen means the quantity, price or seat numbers changed, which is usually a partial release.

Something here wrong or missing? Tell us, and we will fix the page rather than just answer the message.