Plain-language guide
Shared words make planning a ticket and fan offer easier. These definitions are practical starting points for artists, managers, promoters, and venues discussing a launch together.
An artist-branded checkout is a purchase flow presented in the artist’s own visual and editorial context rather than as an anonymous event listing. It can place the ticket, offer, and relevant information in one recognisable destination.
In practice: For a tour team, this means the language around a show can match the campaign and make clear what a fan receives with their order.
A bundle combines a ticket with an additional item or entitlement, such as a digital download, a piece of merchandise, or access to an exclusive experience. The components and their delivery terms should be described before payment.
In practice: A bundle may give a release, tour date, or fan moment a useful structure beyond admission alone.
Direct-to-fan describes a relationship in which an artist or their team can communicate and transact with fans through a controlled channel. It does not remove the need for venues, promoters, or service partners; it clarifies who is stewarding the fan relationship.
In practice: Teams often use direct channels for announcements, presales, follow-up, and future releases.
A digital add-on is a digital item included with, or offered alongside, a ticket purchase. It can be audio, video, artwork, written material, or another downloadable or viewable asset.
In practice: Its value is clearest when the fan understands when it arrives, where it can be accessed, and whether it is tied to a particular show.
Fulfillment is the work of getting every promised item or entitlement to the purchaser after an order. It includes digital delivery, inventory handling, shipping coordination, status updates, and support for exceptions.
In practice: Planning fulfillment before a campaign launches helps teams distinguish an instant digital delivery from a physical item that needs an address and dispatch window.
Opt-in fan data is information a fan has agreed to share for a stated purpose, commonly including an email address and marketing permissions. Consent language, storage, and later communications should align with applicable privacy requirements.
In practice: A usable record lets a team segment messages by city, purchase, or interest without treating ticket access as permission for unrelated contact.
Primary ticketing is the original sale of admission inventory authorised for an event. It covers the ticket creation, purchase, payment, delivery, and entry terms that establish the first ticket-holder record.
In practice: When an additional fan offer is attached, teams should decide whether it is part of primary checkout or a separate journey.
Redemption is the step in which a purchaser claims or opens an item included in their purchase. A redemption flow may use a link, account, code, or verified email to connect the entitlement to the right person.
In practice: Clear instructions and a support path matter when fans buy for someone else or change email addresses after checkout.
A revenue share is an agreed method for dividing qualifying revenue between parties after the costs and deductions defined in the agreement. It is different from gross sales because the calculation depends on the stated base.
In practice: Before launch, teams can document eligible costs, taxes, refunds, reporting cadence, and the point at which revenue is recognised.
A secondary ticket is a ticket offered after its original primary sale, usually through resale or transfer. The rules for whether bundles, digital items, and purchaser benefits follow a transferred ticket should be explicit.
In practice: This avoids uncertainty when the attendee and the original purchaser are not the same person.
A ticket-holder record is the operational profile connected to an admission purchase and its delivery state. Depending on consent and system design, it may hold contact details, order references, show information, and redemption history.
In practice: Support teams use this context to resolve access questions without asking a fan to reconstruct the entire transaction.
White-label ticketing is ticketing technology presented under a client’s brand while another organisation provides the underlying platform or operations. The arrangement can vary widely in checkout ownership, data access, payment handling, and event controls.
In practice: A practical evaluation asks which party manages each part of the sale and what exports or permissions are available afterward.
Want to see these ideas in a working flow? Explore the product tour, read what we do, or bring a specific question to our FAQ.