Your event

Reports

Read-only views over the event's own data, each one downloadable.

Every report downloads as a file.

The index has two lists. Your reports holds the ones saved on this event, each row showing the question it asks and its current answer. Built in holds the ones that come with Tito. A built-in appears once the records it reports on exist, so coupon usage waits until the event has a promotion code.

The built-in list is divided under five headings: Money, Who’s coming, What’s left, Invitations and Check-ins. Each one counts the reports under it. The headings appear once the event has reports under more than one of them.

On an event selling in more than one currency, every money report reads one currency at a time, starting with the event's own. Taken in switches between them. Amounts in different currencies are never added together. The custom report can also group by Currency.

The search field at the top narrows both lists, and builds a report from what you type. Type what you want to know and the report that answers it appears under the field, shown under Your question with the parts of the question as labels: what it looks at, what it's narrowed to, how it's broken down and the dates it covers. Every part can be changed once the report is open. With JavaScript switched off, Enter still finds the same report.

You can search by your event's own words: ticket types, promotion codes, audiences, check-in lists, the questions you ask and the answers those questions offer. So are the four kinds of record a report can be about, the ways each one breaks down, and the date ranges.

A word the search can't place is listed under the row rather than dropped. A word with two meanings, such as a ticket type and a promotion code that share a name, is offered both ways under Which did you mean?. Adding a word that settles it, such as tickets or orders, gives you the single answer.

The search field appears once the index has three reports.

A report appears only if you're allowed to read what it counts. A colleague who can't open the attendee, invitation or check-in sections doesn't see those reports either.

Pending income

Pending income lists money that's been committed and not yet collected: bank transfers awaiting payment, and checkouts that were never finished. It measures against The day it was started, and covers all time.

Clear the Pending label above the table and the same report widens to every order over the same window.

Income and deductions

Income and deductions lists the money one line at a time, from what was asked for to what's left once tax and fees are paid:

• Gross, before anything comes off, which is what the orders charged, with any discount added back on.
• less discount codes, naming the codes that were redeemed.
• less refunds, with how many orders were refunded in full or in part.
• Collected from buyers, which is the two lines above taken off the gross.
• less tax you’ll remit, at the rate each line was sold at.
• less payment fees, what Stripe or PayPal charged to take the money.
• less Tito’s fee, which appears only on accounts we charge one.
• Net of tax and fees.

Above it, four figures: Collected, Net of tax and fees, Tax to remit and Still pending. Below it, Month by month gives the same money a month at a time, in Gross, Deductions, Tax, Fees and Net. Select a month to see the orders behind it.

Select Collected on the event overview to open this report over all time. The report leads with that same figure, and the ledger under it shows the gross the figure came from.

Only orders that took money are in the ledger. An order still awaiting payment is counted in Still pending and nowhere else. Tax comes from the rate recorded on each line when it was sold, so changing a rate today never rewrites what an old month says.

Canceling an order takes it out of every line, including one that had been marked paid. If you collected for it another way, you refund that yourself.

Fees arrive from your payment provider once a payment settles. Until then the payment has no fee recorded, and the fee line says how many payments it is short by.

We work out the tax on these sales and show it here. You file and pay it yourself.

The report covers only the money that moved through Tito. It isn't what reaches your bank, and it doesn't know what your event cost to run.

The date range and Measured against work as they do in Sales over time, below. Select Download for the month table as a file, over the range you're reading.

If you arrive here from a discount code, the ledger covers that code only. Select the ✕ on it to go back to the whole event.

Availability

Availability is the stock view: everything the event sells on one page, with how much of it is taken and how much is left. It covers ticket types, session offerings, items and donations, each under its own heading. The report appears once you've put something of your own on sale.

Every row has four numbers:

• Quantity, how many you put on sale. ∞ means there's no limit.
• Issued, units on paid orders.
• Pending, units held by orders that haven't paid yet.
• Left, the quantity less everything taken, or ∞ where there's no limit.

Pending counts as taken. A pending order holds its stock until it pays or expires.

If the event runs portal stores, a fifth number appears. Via portals is how much of the row's taken stock went out through a portal. It's a share of what's already counted, so a row with 40 taken and 12 via portals issued 28 the ordinary way. Select a Via portals figure for a breakdown portal by portal, with its own Download.

A row shows None left when it's all gone, and Off sale when you've closed it. Off sale wins. A ticket with price tiers between two windows reads Off sale too. Donations have no quantity to run out of, so they report what's been given.

The four figures above the table are the event's totals. Session offerings are left out of Issued and Pending, because a place at a session comes from a ticket already counted under tickets.

Rows link to the thing's own page, where you can change that number. Select Download for the same table as a file.

Sales over time

Sales over time is the one report you set up yourself, and the only one with a time axis. It groups the event's orders into rows, and each row gets its order count, ticket count and gross. There's a Total line under the table.

• Group by chooses what a row is: Day, Week, Month, Audience, Status or Discount code.
• The date range opens on Last 30 days, with Last 7 days, Last 24 hours, This month and All time as the alternatives. An event that finished a while ago opens empty until you widen the range.
• Custom range appears under those five, for a window they don't cover. Fill in From, To or both, then select Apply date range. Both days are counted in full, in the event's own timezone. One date on its own leaves the other end open. The five presets move with the clock, so a saved report using one covers a different stretch each time you open it. A custom range holds the dates you set.
• Measured against sets which day an order counts on: The day it was paid, or The day it was started. Payment is the default. An order that never paid has no paid day, so it's missing.
• Filter narrows what gets counted, by Status, Audience, Discount code or Payment. Each of those then opens on its own values, with how many orders each would leave you.

Payment and Status ask different questions. Paid orders only keeps every order that took money, whichever day the report measures against. Filtering to the Paid status keeps the orders at that status now. A refunded order did take money, so Paid orders only keeps it and the Paid status doesn't.

Select any row to see the Order lines behind it: every line of every order in that group, with the buyer, the item, the quantity and the amount, a page at a time.

Select Download for the same table as a file, in CSV, XLSX, or PDF where the PDF service is available. The download follows whatever the page currently shows, and adds three columns the table leaves out: discounts, refunds and net.

The whole report lives in the page's address. Paste the URL and a colleague gets the exact view.

Attendees

Pick Attendees and the same controls count people instead of money. Group by offers Ticket type, Day, Week and Month, plus one entry for every choice question this event asks. One selection gives you a report of that question's answers.

Answers to your questions on the index opens this report on one of the questions already, and Group by moves it to the next one. A report grouped by a question is named after that question. The row appears once the event asks a choice question and has attendees.

To go straight to one question, search the Reports index for its name.

Each row gives its head count and its Share of the total. People who left the question blank get their own row, No answer. Select a row for the people behind it, with the email address you'd write to.

Filter narrows the same way it does on orders, by the same things you can group by. Filter to No answer, then select a row for the people to chase.

Questions with a fixed set of answers are the ones you can group by: Pick one, Pick any, Yes or no and Checkbox. The list offers the questions you ask of attendees. Three kinds are left out, because one answer covers more than one person, or somebody other than the attendee gave it:

• A question about an item, answered once per item ordered. The breakdown is on the question's own page. See See what people answered.
• A question on the booking form, answered once for the whole booking. Read it on the order's own page, or in the Export from Orders.
• A question on a portal, answered by the person running it. The question's own page counts those answers in portals.

Ask the same question of a ticket type as well and it comes back to the list.

A question you've switched off, or deleted from your account's fields, stays in the list while your attendees have answers on file. It's marked switched off or archived, and grouping by it counts the answers you already collected. Filter offers it the same way.

On a Pick any question each choice gets its own row, and somebody who ticked two boxes adds one to each. The rows therefore add up to more than the total.

Invitations

Pick Invitations and each row gives its total, then the four outcomes: Yes, No, Awaiting reply and Canceled. The four add up to the total. Group by offers Reply, List, Day, Week and Month.

Who hasn’t replied is the chase list: everyone still to answer, grouped by the list they're on. Select a row for their names and email addresses.

Measured against sets which day an invitation counts on: The day they were invited, which is the default, or The day they replied. An invitation nobody has answered has no reply day, so it drops out of that view. The chase list dates by the day you invited them.

Filter narrows to one Reply or one List, so the chase list can cover one list on its own.

Check-ins

Pick Check-ins for the arrival curve. Group by offers Hour, Day and Door. Each row gives its count and its Share. Select a row for who came in, with the door and the exact time.

Filter narrows to one Door.

Only the first scan at each door counts. Scan the same ticket twice at one door and you get one row, stamped when they first came through. Taking a check-in back removes it completely, so a correction doesn't show here.

Save a report

Save a report you want to keep. Select Save report at the foot of the page and give it a name. It joins Your reports on the index, showing its question and its headline figure.

Change anything on a saved report and you're offered Save changes or Discard. Save changes keeps the new question under the same name.

Renaming, duplicating and deleting are in the ⋮ menu beside Download.

• Duplicate copies a report to start another one from.
• Delete report asks first. Deleting a report keeps the orders it counted.

Built-in reports have no ⋮ menu. Open one, adjust it, and select Save report to keep that copy.

Saved reports belong to the event, and everyone working on it sees them. Saving, renaming and deleting need the same permission as changing the event itself.

Sales

The Sales report breaks tickets and revenue down By ticket type, By what was issued, and By source. A source is the main event page, one audience, or a combined row for portals, invitations, quotes, orders created in admin and door sales. Paid orders count as sold. Pending orders hold their places until they pay or expire. Select Download for the same breakdown as a file.

Collected above the tables is the money the event actually took: what buyers were charged, less anything you've handed back. It's the figure Income and deductions leads with, and the same figure on your event overview and your dashboard. The rows underneath are counted before whole-order discounts, and an order you've refunded isn't in them at all, so they can differ from it either way.

A ticket with price tiers or volume prices splits into its own rungs underneath it: a row for each tier, or a row for each band, with the tickets and the money that rung took. Those rows add up to the ticket's row above them. A tier or a band you've removed keeps its row, marked as removed, because the money it took is still in the total. In the download each rung has its own Section, so adding up the ticket-type rows doesn't count a split ticket twice.

By what was issued separates ticket money from the rest of what you sell, in a Tickets row, an Items row and a Donations row. The section appears on events that have items or donations.

Times

The Options report lists every bookable option in order with how full it is, counted in people. Rows link into that option's own management page. The report has its own CSV download.

Portals

The Portals report compares every portal's allocation side by side: how much is issued, reserved and still remaining. Rows link into the portal's own page for the detail. The report has its own CSV download.

Coupon usage

The Coupon usage report lists every promotion code with its rule and how much it's been redeemed for, including retired codes that still have history. The redeemed total counts pending orders alongside paid ones, so it can still move. The order figure counts each order once, so an order that used two codes adds one to it.

A code whose coupon you deleted keeps its row, its history and its money, marked Retired. Its row doesn't open.

Select Download to export the same table.

Notes

• Sales over time counts whole orders, so its gross is what the order charged, including products, donations and order-wide discounts. Read the Sales report for a per-ticket-type split, or one that separates items and donations.
• Days, weeks, months and hours are counted in the event's own timezone, which the report names under its table. The timezone of whoever is reading it makes no difference.
• Every CSV export uses English column headers and status values whatever the account's language, so the files open cleanly in a spreadsheet or feed another system.