Choose the counting unit before interpreting a number. Receipts, ticket-product units, registration records, seats, unique participants, purchaser households, issued tickets, check-ins, and merchandise units are related but not interchangeable.

Before you beginConfirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.

Step by step

  1. Open Events → Reports and set the business timezone, date basis, offering, occurrence, event kind, delivery format, status, ticket option, location, and other required filters.
  2. Use receipt or sale date for recognized sales activity, registration date for enrollment conversion, occurrence date for scheduled attendance, and check-in time for operational attendance. Label exports with the chosen date basis.
  3. Read ticket revenue from the linked event_ticket receipt lines and reconcile registration amount totals, discounts, taxes, refunds, cancellations, and transferred registrations to their source sales. A registration status change alone does not move cash.
  4. Read ticket units and seats separately. One full-day product unit may grant one attendee access to two occurrences; a family or group option may create several seats from one ticket unit.
  5. Compare morning, afternoon, and full-day ticket options, then inspect each shared capacity pool. Full-day seats should consume both half-day pools, so adding option counts without understanding allocations can double-count attendees or available seats.
  6. Track capacity, confirmed seats, remaining units, overbook use, waitlist size, offers, acceptances, expirations, and sold-out or reopened periods by offering and occurrence.
  7. Measure unique participants and repeat participants from reusable participant identities. Measure purchaser households from purchaser customers. A returning guardian with a new camper and a returning camper purchased by another guardian are different retention stories.
  8. Analyze attendance as accepted check-ins, unique attendees, check-outs, denied scans, duplicates, void corrections, no-shows, and completion. Check-in rows are append-only evidence, so use the effective result rather than deleting exceptions from the denominator.
  9. Report optional merchandise from its own receipt product lines. Use normal product category, SKU, variant, quantity, price, discount, tax, cost, and inventory fields to answer how many T-shirts, sizes, kits, lunches, or take-home robots were sold.
  10. When merchandise was intentionally included at no extra charge, use an explicit zero-dollar receipt line only if that is the documented fulfillment and unit-tracking design. Keep its quantity out of admission revenue while retaining unit reporting; do not add unrequested merchandise to historical receipts.
  11. Break down by offering, occurrence, session kind, ticket option, product, category, participant type, purchaser or household, new versus repeat, registration source, location, age band where authorized, and attendance outcome.
  12. Export only the minimum columns needed. Exclude medical, emergency, waiver, pickup, exact birth date, ticket credentials, and private answers from routine reporting. Use aggregated age bands or operational flags when they answer the question.
  13. Reconcile a sample from report row to registration, participant, ticket option, receipt line, payment, capacity allocation, ticket, and check-in before distributing the result.
  14. Use the Event reports view or the documented event-report API resource for the privacy-safe reporting slices: financial summary, add-on product and variant units, participant and repeat segments, occurrence selections and attendance, tracks, stakeholders, and allowlisted standard answer dimensions. Protected answers and ticket codes are excluded.
  15. For giant conferences, page or export the full result rather than treating the screen’s first 100 session rows as the complete dataset. Preserve report_key, product_id and variant_id, occurrence_id and occurrence_instance_id, participant identity, receipt line, and lifecycle status as separate join dimensions.

Screen and contract reference

Control or areaWhat it means
Date basisSale, registration, occurrence, or attendance timestamp used for the report period.
Ticket revenueNet sales from linked event_ticket receipt lines after applicable discounts, returns, and refunds.
Ticket unitsCatalog product quantity sold.
Registered seatsSeat count represented by registrations; may differ from ticket units.
Unique participantsDistinct attendee identities in the selected scope.
Purchaser householdsDistinct customers who managed the transaction.
Repeat participantParticipant with qualifying prior registration history.
Capacity consumedUnits applied to every linked pool, not simply ticket quantity.
AttendanceEffective accepted entry and related exit/correction evidence.
No-showConfirmed expected participant without qualifying attendance under the business rule.
Merchandise unitsSeparate receipt-line quantities for shirts, robots, kits, meals, or other products.
Zero-dollar lineUnit-tracking line with no admission revenue; use only when the merchandise is truly included and intended.
Privacy-safe exportReport that omits sensitive participant and credential fields not needed for analysis.
Reporting slicesServer-shaped financial, merchandise, participant, lifecycle, session, track, stakeholder, and allowlisted-answer datasets.
report_keyStable dimension key for an approved standard registration question; not permission to expose sensitive answers.

Expected result

The selected filters reconcile from aggregate to offering, occurrence, ticket product, registration, participant, purchaser, receipt line, capacity allocation, merchandise line, and append-only attendance evidence without mixing counting units or exporting sensitive fields.

Troubleshooting

  • Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
  • Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
  • Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.