18 — Sales and analytics

← Handbook · Previous: Exports and reporting

What it is

Event Analytics shows what your events have earned: in total, over any period, and event by event. Find it from My Events with Event Analytics on an event card.

The four figures

You Received: what your ticket sales leave you after our fee, card processing and any refunds. It's what reaches your payouts. The arrow compares it with the period before.
Tickets Sold and the number of orders.
Avg Order: what a typical order was worth, and how many tickets it held.
Ticket Sales: what buyers paid, less refunds, before fees — with the two fees named apart underneath, because most of what comes off a sale is Stripe's card processing (about 2.9% + 30¢) rather than the COME TOGETHER fee. On a $6,751 event at 10¢ a ticket, that's $209.42 to Stripe and $6.30 to us.

Below them, a chart has one line per event. Click an event's name to hide or show its line. The chart rescales, so a big event doesn't flatten the smaller ones.

What you control

Period: Today, Last 7 Days, Last 28 Days, Year to Date, or a custom range.
Event: all your events, or one. Archived events are listed and still count.

How it behaves

Only paid sales count. Free RSVPs and orders discounted to $0 earn nothing, so they don't appear. Unfinished checkouts don't count either.

A sale counts on the day it was placed, in your event's time zone. An evening sale shows on that evening, not the next day.

Refunds lower the day of the original sale. If you refund an order from last month, last month's figures go down. A day can even show below zero: card processing and our fee aren't returned when you refund, so a sale you gave back in full costs you those fees.

Orders refunded in full aren't counted as orders. Their fees still come off You Received.

Card processing is exact once the payment settles. For a short while, or for older orders, it's an estimate. When any figure includes an estimate, the page tells you how many orders it applies to.

The event report

Every event has a Event Report, from its page. It's written to be read after the night, and it's the page to send anyone who asks how it went.

Tickets out and who turned up. The attendance figure counts scanned tickets against tickets issued. If nothing was ever scanned it says so rather than claiming nobody came.
How it sold. The running total of tickets over time, with the moments marked: when each tier ran out, and when you emailed or announced something. This is where you find out whether that post did anything.
How the room filled. Arrivals in fifteen-minute steps, from the first scan to the last, with the busiest quarter hour named. Useful for staffing the door next time.
Tickets by tier, including when each one sold out.
Where they came from (below), and your crowd: buyers, how many had been to one of your events before, tickets per order, and how many want to hear from you.

Money on this page follows the same rules as everywhere else, and is only shown to people who can see your takings.

Where your buyers came from

The report lists the sites that sent people to your event page — Instagram, a blog, a search — with how many visits each sent and how many of those bought.

Name your own links. Add ?utm_source= to the end of a link and whatever you put there becomes the label: ?utm_source=story_friday in your Friday story, and the report will tell you what that story did.

What's counted: visits, not people. We don't keep any record of someone who looks and doesn't buy — no profile, no identifier, no extra cookie. A buyer's order records which source they arrived from, which is what lets the page show what converted.

Looked, then bought

Above it, the report shows the whole way through: page opens (every time the page was opened), unique visits, reached checkout and bought — each with what share of the step above it got there. It's the answer to "plenty of people looked, so why so few sales": you can see exactly where they stopped.

Unique visits are not people. We count one per browser per day, so someone who looks on their phone and again on a laptop is two, and two friends on the same wifi using the same browser can be one. It's the right figure for "was that 300 opens from 40 browsers or from 280", and we don't claim anything finer, because doing so would mean identifying the people looking.

Counting started on 20 September 2026, so events before then show nothing.

When your tickets sell

Analytics (from My Events) also shows, across all your events:

When your tickets sell — by hour of the day and day of the week, on your own clock. It names your busiest hour and night. Use it to time a post or open a tier. It counts orders, not tickets: a group buying four is one decision.
Your crowd — how many people have bought from you, how many came back for more than one event, and how many want to hear about the next one.

Elsewhere

Event cards on My Events show each event's revenue: paid orders, less refunds.
An event's Orders page shows the same figure, plus orders, tickets and check-ins.
Exports give you every ticket in a spreadsheet (see Exports and reporting).

Who can see it

Owners, Admins and Managers see revenue. Other roles don't see the takings anywhere: not on cards, the Orders page or Analytics.

Good to know

For payouts, use Stripe. Analytics tells you how your events sold. Your Stripe dashboard is the record of what was paid into your bank account, and when.

Figures for a past period can change if you refund someone later. Re-check before closing your books.

Promoter figures are counted differently. A promoter's page shows what they brought in, with refunds listed separately, so it won't match these totals exactly.

If something here does not match what you see on screen, the screen is right and this is out of date — tell us.