Glossary

The words Convova uses, defined once. How things work is in the Guides.

People and accounts

Person: anyone with an email address in Convova, signed in or not.
Account: a person who has signed in at least once.
Onboarding: the one-time profile step after the first sign-in.
Profile: what a person shows others: name, title, organization, bio, avatar, links.
Super admin: a Convova operator with access to every event, and to a host's pages as a member of it.

Host: the company, community, or person that runs events.
Owner: a host member who can create and publish events, manage payments, and manage members.
Member (of a host): a person who can manage the content of every event the host runs.
Host page: the public page of a host: name, logo, description, published events.
Suspended: a host that Convova has stopped from creating, publishing, or selling.

Event: a conference, summit, or meetup run by one host.
Draft: an event only its host and members can open.
Published: an event anyone can open.
Archived: an event hidden from attendees, with everything kept.
Event page: the public page of a published event.
Event member: a person added to one event only, as admin or staff.
Admin (of an event): an event member who can manage the event's content.
Staff: an event member who can run the desk and read the event's lists, and nothing else.

Session: one item on the schedule, with a start and an end time.
Contributor: a person on the program, such as a speaker or a panelist. Content, not an account.
Organization: a company or group on the program, such as a sponsor or an exhibitor. Content, not an account.
Tag: a label on sessions, contributors, or organizations that groups them into sections of the program.
Visible: shown on the event page. Hidden items stay in the dashboard.

Ticket: one admission to an event, held by one person.
Attendee: a person who holds a ticket to an event.
Ticket type: the label a ticket carries, printed on the badge. Also called the badge label.
Source: where a ticket came from: store, invite, walk-in, or the platform an import came from, Luma or Eventbrite. A send does not change it.
Valid: a ticket that admits someone.
Revoked: a ticket that admits nobody.
Unclaimed: a valid ticket not yet made someone's own.
Claimed: a valid ticket that is its holder's for good.
Claim: making a ticket yours.
Send: giving an unclaimed ticket to someone by email.
Accept: taking a ticket that was sent to you.
Cancel (a send): withdrawing a send before it is accepted.
Invite: a host issuing a ticket to an email address.
Import: bringing tickets sold on Luma or Eventbrite into an event.
Walk-in: a ticket the desk issues to someone at the door.

Store: the tickets and add-ons an event sells through Convova.
Product: something for sale: a ticket product or an add-on.
Ticket product: a product that issues a ticket of one type.
Add-on: a product bought on top of a ticket, such as a workshop seat.
Price: what a product costs, optionally within a window such as early bird.
On sale: a product that can be bought right now.
Quantity: how many of a product can be sold.
Capacity: the most live tickets an event can have, from every source; checked when the store sells.
Promo code: a code that gives a discount. Called a coupon in the dashboard.
Checkout: the page where a buyer picks tickets and add-ons and pays.
Hold: the reservation of a buyer's units while they pay.
Order: one purchase: units, amounts, buyer, payment.
Buyer: the person an order belongs to.
Receipt: the record of a paid order, from Convova by email and from Stripe as a page.
Invoice: the invoice Stripe issues for a paid order.
Refund: money returned to the buyer by the host through Stripe.
Store share: the share of each store sale that Convova keeps.

Free event: an event with no priced ticket, up to the free cap.
Free cap: the most tickets a free event can have.
Full event: an event that pays a fee.
Base fee: what a full event pays once, at publish.
Growth block: the batch of tickets a full event is charged for as it grows.
Yearly plan: a host's yearly fee that covers every event it publishes instead of per-event fees.
Card on file: the card a host saved at Stripe for fees and the plan.
Payments page: where a host manages its plan, its card, and its Stripe connection.

Pass: what an attendee carries on their phone for one event: QR code and tickets.
QR code: the code on the pass that identifies a person for one event.
Badge: the printed card with a person's name, title, organization, and QR code.
Desk: the check-in station staff run.
Check-in: a record that a ticket admitted its holder.
Announcement: a message from the host to everyone attending.
Question: a private message from an attendee to the event's admins.
Connection: two people at an event, made when one scans the other's badge.
Saved: a session an attendee marked to find again.
Liked: a session an attendee marked as good.

Dashboard: where hosts and event members run things.
App: where attendees are: events, tickets, orders, the pass.
Public site: the pages anyone can open: homepage, pricing, event pages, host pages, checkout.
Public API: how a host's own website reads a program and sells tickets.
API key: a key that lets a host's own registration form add attendees to an event.