Glossary
Quick definitions for the terms used in this guide. The chapter where each is introduced is in parentheses.
Account credit — A money balance on the fan's account in the ticketing system (not Attend), applied against a purchase. Belongs to a ledger and can't cross seasons. (Ch 15)
Account group — A bucket of customer accounts in the vendor's system; Attend reads it via API and uses it for gating (and, in future, discounts). (Ch 14)
Account ID — A fan's identifier in a ticketing system. Every ticket Attend sells must be attached to the buyer's account ID. (Ch 3)
Active program — The one published program currently driving a store. A store can have many published programs but only one active at a time; teams swap it to change pricing/packs/banner. (Ch 16)
Add-on — Anything extra sold alongside the main purchase: parking, merchandise, food-and-drink credit — even tents. Sold as separate events on the vendor. Comes in three types — optional, forced, and informational — plus overflow for extra suite seats. (Ch 9, 13, 23)
All-in price — Base price + service fee, shown to fans as one number. The V3 standard (no breakdown) unless a state law requires one. (Ch 22)
Archtics — One of Ticketmaster's two ticketing systems (the other is Host). Attend's core terminology — class name, price code, ticket type code — comes from Archtics. (Ch 3, 7)
Attend flavor — Informal name for everything Attend layers on top of the raw vendor seats: game packs, subscriptions, discounts, branding. (Ch 5)
Base config — Global per-store settings that don't change when you swap programs (auth token expiry, the team's time zone). Contrast with program config. (Ch 18)
Best available — Selling a seat without naming it: Attend sends a class name + price code + ticket type code, and the system picks any matching seat. Used by Flow, Pass, and add-ons. (Ch 9)
Build Your Own (BYO) — A flex program shape where all events are flat and the fan picks any combination, within a program-wide min/max. (Ch 12)
Class name — A group of seats used to control access — which seller is allowed to sell them. Nothing to do with price. (Ch 7)
Client — Attend's customer: a team (e.g. the Golden State Warriors), not the league. (Ch 2)
Cortex — Attend's internal admin tool, where teams and ops staff configure products (events, prices, discounts, inventory). Fans never see it. (Ch 4, 5)
Crowd Handler — A queueing vendor Attend uses for traffic spikes: during an email-blast on-sale it holds excess visitors in a queue and funnels them in gradually. (Ch 17)
DSN — Ticketmaster's per-client identifier: one DSN = one client = one TM database, and the API rate limit (~120/min) applies per DSN. All of Live Nation shares a single DSN. (Ch 17)
Dummy event — An "event" in the ticketing system with no real game behind it and no barcode, used to record sales of passes and add-ons. (Ch 9)
Event — A specific game or show in the ticketing system; each event links to one manifest. (Ch 6)
Flex — Attend's bundle product (game packs of 3/5/7 games); sells seats and suites; built for conversion. (Ch 4)
Flex program — The top-level thing a team configures for a Flex offer; its shape is BYO, game packs, or (later) predefined packages. (Ch 12)
Flow — Attend's last-minute, single-game product (e.g. a discounted text blast for unsold seats). (Ch 4)
Forced add-on — An add-on the fan can't decline or see priced separately: its cost is baked into the displayed price but transacted as a separate event (e.g. sales tax, parking). (Ch 23)
Full price code — An optional combined code (price code + ticket type code, e.g. C76). Nothing
core depends on it; fetching it adds ~50% API usage, so it's flag-controlled. (Ch 17)
Game pack — A named bundle (3-/5-/7-game) with events mapped in and its own min/max; may use tiers. (Ch 12)
Gating — Controlling who is allowed to purchase a program — by account group, email domain (e.g.
.edu), or a direct email allow/blocklist. (Ch 14)
Informational add-on — A forced add-on with no transaction behind it: the fan is simply told it's included ("comes with 8 parking passes"). Pure display. (Ch 23)
Inventory snapshot — A Premium / Suite-Level per-event pre-computation (available suites, starting price, by suite type) written by a periodic cron (~5 min in current deploys), which the Premium home page reads instead of recomputing live. Not real-time. Plain Flex seat-level inventory is read live (no snapshot). (Ch 18)
Ledger — A per-season record-keeping scope in the ticketing system; events and account credit both belong to a ledger, and credit can't cross ledgers. (Ch 15)
Manifest — A specific layout/template of section/row/seats for a venue. A venue can have several; each event links to one. (Ch 6)
Overflow add-on — Extra seats sold beyond a suite, drawn from a dedicated seat pool
(tbl_suite_overflow_seat_mapping). (Ch 23)
Partial sale — Selling part of a suite instead of the whole block. count-based (define sizes like 2/4/6 — the supported mode; the seats must be consecutive within one row) or block-based (explicit seat blocks — defined but unused). When on, the full suite is hidden unless a partial equal to the full size is added. (Ch 19)
Pass — Attend's subscription product: a ticket to every game, with the seat assigned on game day (not a fixed seat like a season ticket). (Ch 4)
Payment plan — Splitting a purchase into installments, resolved at checkout (charge the first installment instead of the total). Built as a reusable architecture after a client's $25k card authorization cap. (Ch 22)
Predefined package — A flex program shape (not yet built) where the team fixes the exact events and the fan buys the package as-is, optionally with post-purchase add-ons. (Ch 12)
Premium — Attend's product for selling suites online, with a high-end, image-rich experience. (Ch 4)
Price code — A grouping of seats by quality/tier (e.g. PR = premium, GR = general). A seat
belongs to exactly one. (Ch 7)
Pricing rule — The filter that decides which slice of all vendor pricing a given fan sees: a set of allowed (event, price code, ticket type code) combinations, with eligibility conditions (account group, pack, package, event count) and a priority to break ties. Event-level or suite-level. (Ch 21)
Primary market — The first sale of a ticket, on the team's primary vendor. Attend works only here. (Ch 3)
Reference event code — An event code used to fetch inventory; it applies globally (the vendor only lets you fetch one event at a time), not just to that event. (Ch 13)
Revenue share — Attend's business model: teams pay Attend for sales it drives; Attend pays a cut to the ticketing vendor. (Ch 1)
Seat map — The visual picture of a venue's seats (3D or a static image) that a fan browses. It renders a manifest and is tied to the manifest, not the event. (Ch 6, 13)
Seat-hold specific — Selling a seat by naming the exact section/row/seat (plus price code and ticket type code). Used by Flex and Premium. (Ch 9)
Secondary market — Resale of tickets after the first sale (e.g. StubHub). Attend stays out of it. (Ch 3)
Section / Row / Seat — The three coordinates that locate any seat; all ticketing reduces to these. (Ch 6)
SeatGeek — One of the three ticketing vendors Attend integrates with. (Ch 3)
Season ticket — The vendor's own product: the same fixed seat for every game. Contrast with a Pass. (Ch 4)
Starting price — The cheapest currently-available option for an event (stored per event and per suite type in the Premium/Suite-Level inventory snapshot); the "from" price the Premium home page shows. (Ch 18)
Stripe — The payment processor Attend uses to charge fans directly for TM Host sales (and SeatGeek, once integrated). (Ch 10)
Suite — A private hospitality box (sold by both Premium and Flex): real seats grouped to sell as one block — a must-buy-together restriction, not fake seats. (Ch 4, 6, 11)
Suite type — A Premium category above suites (e.g. "Club Level"); images cascade from the type down to its suites. (Ch 11)
TBD / TBA — Event date statuses: TBD = date not yet decided; TBA = decided but not yet publicly announced. (Ch 13)
Team — A sports team (e.g. the Warriors); in Attend, the team is the client. (Ch 2)
Ticket type code — A code under a price code that, together with the price code, sets the actual
price (e.g. PR_A = adult $100). A discount is just a lower-priced ticket type code; a pack selects
one via a pricing rule (no direct pack→code map). (Ch 7, 8, 21)
Ticketing system / vendor — The platform that owns the real seats and barcodes (Ticketmaster, Tickets.com, SeatGeek). Attend sells on top of these. (Ch 1, 3)
Ticketmaster — The largest ticketing vendor; runs two systems Attend treats separately: Host and Archtics. (Ch 3)
Tickets.com — A ticketing vendor owned by MLB; most baseball teams use it. (Ch 3)
Tier — An optional grouping of a game pack's events (e.g. rivalry / mid / easy) with per-tier min/max to force variety. The backend always has tiers — a dummy one when unused. (Ch 12)
Venue — The building (e.g. an arena). Has one or more manifests. (Ch 6)
White-label — Each client gets its own branded version of Attend's product, on its own URL. (Ch 1)