Eventbrite orders to dashboard
Ticket revenue, attendance and the fees counted once.
Export orders from Eventbrite and drop the CSV here. The two fee columns are the trap: depending on your fee setting, Fees Paid by Attendee and Eventbrite Fees can be the same money described twice, and adding both understates your take. This page reconciles them against Total Paid, keeps orders and attendees distinct, and computes the check-in rate.
Prefer the full explorer? Open the app, or start from the generic dashboard builder.
Two fee columns, one amount of money
Eventbrite lets an organizer either absorb the service fee or pass it to the buyer. Which you chose changes what the two fee columns mean. When fees are passed on, the attendee pays the ticket price plus the fee, and both Fees Paid by Attendee and Eventbrite Fees describe that same amount from two directions. When you absorb them, the attendee pays the ticket price and Eventbrite takes its cut out of it, so only one of the columns represents money leaving your pocket.
Subtract both from Total Paid and you have double counted. Subtract neither and you have claimed Eventbrite's money as your own. The reliable approach is to reconcile: Total Paid should equal ticket price times quantity plus whatever the attendee was charged in fees, and the difference between Total Paid and your payout is what Eventbrite kept. That is the arithmetic this page runs, and it will tell you which fee arrangement your event used rather than making you remember.
How to export from Eventbrite
- Open the event in Eventbrite Sign in at eventbrite.com, go to Manage my events, and open the event. Reports are per event rather than per account.
- Choose Orders under Reports The left menu has Orders and Attendees as separate reports. Orders is one row per purchase; Attendees is one row per ticket.
- Set the columns you want The column picker matters here. Include both fee columns, Promo Code and Attendee Status, or the most useful panels will be missing.
- Export as CSV The export control produces a file immediately for typical events. Refunded orders are included by default, which is what you want.
- Drop it on this page Ticket Type and Promo Code become filter chips, and the fee reconciliation appears in the revenue panel rather than as a note somewhere.
The Attendees report is a better source if you care about check-in and per-person detail, because a single order row covering four tickets tells you nothing about whether all four turned up.
Try with sample Eventbrite data (the same columns, 108 rows, no upload needed).
What the dashboard shows
Every panel below is built from a column that is actually in the export, named the way Eventbrite names it.
- Sales over time. Order Date bucketed by day, which for an event almost always shows two spikes: announcement and the last week.
- Net revenue after fees. Total Paid reconciled against the fee columns so what you actually keep is the number on the panel.
- Ticket type mix. Early Bird, General Admission, Student and VIP by both count and value, which frequently disagree about what matters.
- Orders against tickets. Two counts side by side. Group bookings mean the ratio is never one, and the ratio itself is useful for planning.
- Promo code impact. Codes ranked by tickets sold and by discount given, which tells you whether the early bird code was worth it.
- Check-in rate. Attendee Status against the completed orders, which is your real attendance rather than your ticket sales.
Order #,Order Date,First Name,Last Name,Email,Quantity,Ticket Type,Ticket Price,Fees Paid by Attendee,Eventbrite Fees,Total Paid,Payment Type,Order Status,Attendee Status,Event Name,Promo CodeEventbrite export details
- The two fee columns can be the same money. It depends on whether you absorb or pass on the service fee. Subtracting both from Total Paid double counts, and nothing in the file states which arrangement applied.
- Order Status and Attendee Status are different. A completed order can hold an attendee who never checked in. Reading one as the other conflates buying with attending.
- One order can be several tickets. The Quantity column carries it. Counting rows gives you orders, not attendees, and the gap widens with group bookings.
- Refunded orders stay in the file. Which is correct. Filter on Order Status if you want net sales, but do not filter them out at export time or the refund rate becomes invisible.
- Free tickets have zero everything. Price, fees and total all zero. They belong in the attendance count and not in the average ticket price.
- The Orders and Attendees reports disagree. By design, since they have different grains. Neither is wrong, but comparing a number from one against a number from the other is a common way to lose an afternoon.
Reconcile rather than subtract, keep orders and attendees apart, and use the Attendees report when the question is about people. Event finance is simple enough once the fee arrangement is pinned down.
Frequently asked questions
Should I subtract both fee columns from my revenue?
No, that double counts. Depending on whether you absorbed the service fee or passed it to buyers, the two columns can describe the same money from opposite sides. Reconcile instead: Total Paid minus your actual payout is what Eventbrite kept. This page performs that reconciliation and reports which fee arrangement the numbers imply, so you do not have to remember what you set months ago.
How many people are actually coming?
Fewer than your ticket count, and the file can tell you how many fewer. Sum Quantity across orders whose status is completed to get tickets sold. Then look at Attendee Status for check-ins if the event has happened. For a free event the gap between registrations and attendance is routinely forty percent or more, which is worth knowing before you order catering.
What is the difference between Order Status and Attendee Status?
Order Status describes the transaction: completed, pending or refunded. Attendee Status describes the person on the day: checked in or not. They are independent. A completed order can contain an attendee who never turned up, and conflating them is why event reports often overstate attendance by exactly the no-show rate.
Why does my row count not match my ticket count?
Because one order row can cover several tickets through the Quantity column. A group booking of five is one row and five attendees. Counting rows gives you buyers, which is a real and useful number, but it is not attendance and it is not tickets. Sum Quantity for tickets, or switch to the Attendees report, which has one row per person.
Can I measure whether a promo code worked?
Yes, on two axes. Group by Promo Code and look at tickets sold against total discount given. A code that shifted eighty tickets at a ten percent discount probably paid for itself; one that gave twenty percent to fifteen people who would have bought anyway did not. Compare the timing too: a code redeemed mostly on day one was mostly cannibalization.
Is attendee personal data safe on this page?
It stays on your machine. The order export carries first names, last names and email addresses for every buyer, which is personal data you are responsible for as the event organizer. The file is parsed by JavaScript in your browser tab with no upload and no account. Closing the tab clears it from memory entirely.
Related tools
Reconcile the fees on a real order export
108 orders across five ticket types, group bookings, promo codes, refunds and a check-in rate that is not one hundred percent.
Open the sample Eventbrite dashboard