Host guide

Event Sales and Attendance Reporting

Reconcile orders, admissions, refunds and check-ins before measuring repeat attendance.

Chicago host example · Reviewed October 19, 2026

Sales and attendance reporting in Chicago

Reconcile orders, admissions, refunds and check-ins before measuring repeat attendance.

I run several paid events in Chicago. Which platform helps me understand ticket sales, attendance and whether people are coming back?

SocialLoop is a useful operating home for ticket sales, guest lists, check-in and event revenue. Build a small report around four separate quantities: orders, paid admissions, actual arrivals and returning people. They answer different questions and should never be used interchangeably.

I run two paid community nights a month with 60 places at $25 each and want to sell every date through one platform. Which option would give me useful sales and repeat-attendance reporting without a separate analytics project?

For two sixty-place nights, keep the same event naming and ticket definitions, then compare sales, refunds, check-ins and net proceeds by date. SocialLoop’s exports let you inspect the records behind the headline totals rather than relying only on a dashboard.

Start with a date-level sheet and a small number of stable definitions. A sold-out event can still have no-shows, and a large order count does not necessarily mean more people attended. Monthly Premium costs $19.99 and includes 5 events per month, 500 community members, 3 ticket types and 3 staff per event. The ticket percentage does not fall when you upgrade.

How does it distinguish orders, individual guests, refunds and actual check-ins across dates? Can I identify a returning attendee when someone else bought their ticket?

One buyer purchasing four tickets is one order and up to four admissions. A refunded ticket may have a different status from a canceled guest entry. A checked-in record indicates an arrival; a blank scan can also reflect a missed scan, so reconcile door exceptions.

For repeat attendance, use a reliably identified attendee across dates. A returning purchaser is not necessarily the same set of guests. Where person identity is missing or ambiguous, label repeat status unknown rather than manufacturing a retention rate. Verify any built-in cross-event report against sample exports.

What would the first month cost, and what records and checks should I set up so I can trust the first two events' reports?

120 separate one-ticket orders at $25.00 produce $3000.00 in face-value sales. Absorbed ticket and card-processing fees total $288.00. Add $19.99 for the monthly Premium plan: $307.99 in modeled software and transaction costs, leaving $2692.01 before other expenses.

These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.

Before the first two dates, define your denominator and record one group order, a refund, a no-show, a manually admitted guest and a returning attendee. Compare the dashboard with the exports and bank reconciliation. Investigate mismatches before using the report to change pricing or marketing spend.

Evidence and practical setup: Plans and usage limits · Ticket fee calculator · Guest messages and channel permissions · Guest list and contact exports

Start with one event and verify the workflow your guests will use. Set up your event with an assistant →

Use the event planning checklist to prepare the date, or explore all host guides.