# How do you build custom reports on ticket sales and buyer behaviour? | Ticket Fairy -oppaat

1. [Ticket Fairy](https://www.ticketfairy.com/)
2. [Oppaat](https://www.ticketfairy.com/fi/guides)
3. How do you build custom reports on ticket sales and buyer behaviour?

Järjestäjien kysymyksiä

# How do you build custom reports on ticket sales and buyer behaviour?

The reports that answer the usual questions, the orders table for the ones they do not, and the export that gets your event's numbers into anything else.

Kenelle:  Anyone facing a question the standard reports do not answer

Kestää:  6 minuuttia

Many "custom report" questions already have a screen. Your event's statistics cover what sold and when, where the buyers came from, who they are, which fans sold to their friends, and who has arrived. Start there, and build something by hand for what they do not cover.

For the questions that are genuinely yours, work from the orders table: filter it to the slice you mean and export that slice to CSV, or export every ticket rather than every order when the question is about attendees. That file is what goes into a spreadsheet, a BI tool or a finance system.

And you can ask in words. Fai in the dashboard, your own assistant over MCP and the command line all read the same numbers the screens draw, so "which age band bought the most, and how does that compare with last time" is a question rather than a spreadsheet.

## Näin Ticket Fairy hoitaa sen

- ### [The statistics your event already has](https://www.ticketfairy.com/fi/guides/read-your-audience-demographics)

  You get Performance, Orders, Traffic, Demographics, Psychographics, Geographics, Influencers, Check-In and Devices. Each answers one question about your event, and you build none of them.
- ### The orders table, filtered

  Filter it to a ticket type, a date, a status or an add-on, and you are looking at the answer. Export what you filtered to and the file holds the same rows.
- ### Export to CSV, orders or tickets

  **Export to CSV** takes the rows as you have filtered them. **Export all Tickets** and **Export Filtered Tickets** give you one row per ticket instead, which is the shape most questions about attendees need.
- ### [The same numbers, asked in words](https://www.ticketfairy.com/fi/guides/see-where-buyers-came-from)

  Fai reads these screens inside the dashboard, your own AI assistant reads them over our MCP server, and the command line prints them as JSON for a script that runs every morning.

## Näin otat sen käyttöön

- [Check whether a screen already answers it](#step-1)
- [Filter the orders table to the slice you mean](#step-2)
- [Export the slice, not the database](#step-3)
- [Put the recurring ones on a schedule](#step-4)

## Mitä tarvitset ennen aloitusta

- You're an owner or an admin on the event. A **Stats** login opens the report screens but not the orders table, and you need the orders table to export.
- Your event has sold something. Every report below reads your real orders.

1. ## Check whether a screen already answers it

   Open **Statistics** on your event and start with **Analytics**, which is what sold and when. Traffic sources, ages and locations, referrals and check-ins each have a screen of their own beside it.
         ![The event Analytics overview, with tickets sold, revenue and the sales curve across the run](https://www.ticketfairy.com/embeds/posters/marketing-analytics--analytics-overview.png)    Statistics, Analytics.
2. ## Filter the orders table to the slice you mean

   Open **Orders** and narrow it to one ticket type, one add-on, one order status, one discount code, or a search. The rows left on screen are the orders your question is about, one row per order rather than one per person.

   There is no date filter on this table. Where the question is about a window of time, sort by order date and take the rows you need, or read the sales-over-time screen, which does exactly that.
3. ## Export the slice, not the database

   Use **Export to CSV** for the orders as filtered, or **Export Filtered Tickets** where the question is about attendees rather than transactions.

   One order can hold several tickets, so an orders export and a tickets export answer different questions. Pick the one whose rows are the thing you are counting.
4. ## Put the recurring ones on a schedule

   Where the same question comes back every week, ask it from the command line with JSON output and let a script run it. You get the numbers the screens show, so you never have to reconcile two answers.

## Tai anna sen hoitua puolestasi

Fai and your own AI assistant over our MCP server both read the statistics screens. The command line reads them too, and writes the orders export straight to a file a script can pick up.

### Hallintapaneelissasi, Fain kanssa

Compare this event with the last one I ran: what sold, where the buyers came from, and which age band bought the most.

### Omasta avustajastasi, MCP:n kautta

Yhdistä avustajasi [MCP-palvelimeemme](https://www.ticketfairy.com/mcp-server) ja pyydä sitä:

Sivun vain luku -asetus riittää tähän. Täällä ei muuteta mitään, joten jätä `--read-only` paikallaan.

Find my event by name. Pull its sales summary, its traffic and its age demographics, then tell me which referrers sent the most visitors and how sales moved over the same days.

## Päätteeltä

Asenna CLI osoitteesta [CLI-sivultamme](https://www.ticketfairy.com/cli), kirjaudu komennolla `ticketfairy auth login` ja valitse brändi, jonka parissa työskentelet, komennolla `ticketfairy brand use <BRAND_ID>`. `ticketfairy brand list` ja `ticketfairy event list` tulostavat tunnisteet, joita alla olevat komennot tarvitsevat.

Sign in with the same login you use for the screens. To export the orders you need an owner or admin login, the same as in the dashboard.

### What has sold, as the summary at the top of the screen

ticketfairy event stats \<EVENT\_ID\> --metric sales

### The same numbers per ticket type

ticketfairy event stats \<EVENT\_ID\> --metric performance --output json

### Every order for the event, written to a file for a spreadsheet

ticketfairy order export \<EVENT\_ID\> --output csv --file orders.csv

## Kysymyksiä joita sinulla voi olla

Is there a report builder?:  Not a drag-and-drop one. The report screens cover the questions that come up most. Past those, filter the orders table and export it, or ask Fai, your own assistant over MCP, or the command line, which all read the same numbers.

What is the difference between an orders export and a tickets export?:  One row per transaction against one row per ticket. A single order can carry four tickets in three names, so counting attendees from an orders export undercounts them.

Can I get ticket sales into our BI tool?:  Yes. Export the slice as CSV for a one-off, and for something that runs on a schedule use the command line with JSON output, which returns the same figures the screens draw.

Who can see these reports?:  You can open the report screens on an owner, admin, **Stats** or **Limited Stats** login, so you can let somebody read the numbers without letting them change the event. You need an owner or admin login to open the orders table, so that is what the filtered export asks of you.

Do the reports include refunded orders?:  You choose. Filter the orders table to include or exclude refunded and cancelled orders, and decide which of the two your question means before you export.

## Mihin seuraavaksi

- [Mitä muuta voit tehdä Ticket Fairyllä](https://www.ticketfairy.com/fi/event-ticketing/features)
- [See who buys your tickets in your event demographics](https://www.ticketfairy.com/fi/guides/read-your-audience-demographics)
- [See where your event page visitors came from](https://www.ticketfairy.com/fi/guides/see-where-buyers-came-from)
- [See which buyers come back to your events](https://www.ticketfairy.com/fi/guides/browse-your-customer-list)
- [How do you stop a high-demand on-sale from falling over?](https://www.ticketfairy.com/fi/guides/hold-up-a-high-demand-on-sale)
- [How do you manage many events on one ticketing platform?](https://www.ticketfairy.com/fi/guides/run-many-events-on-one-platform)
- [How do you compare ticketing platforms on fees, payouts and customer data?](https://www.ticketfairy.com/fi/guides/compare-ticketing-platforms-fees-payouts-and-data)
- [What marketing tools should a ticketing platform give you?](https://www.ticketfairy.com/fi/guides/marketing-tools-a-ticketing-platform-should-have)
- [How do you manage backstage access passes for an event?](https://www.ticketfairy.com/fi/guides/manage-backstage-access-passes)
- [How does event accreditation fit with your ticketing and CRM?](https://www.ticketfairy.com/fi/guides/accreditation-with-ticketing-and-crm)
- [How do you manage tickets for a multi-day event?](https://www.ticketfairy.com/fi/guides/manage-tickets-for-a-multi-day-event)
- [How do you let buyers pay for tickets in instalments?](https://www.ticketfairy.com/fi/guides/let-buyers-pay-for-tickets-in-instalments)
- [What makes an embedded ticket checkout worth having?](https://www.ticketfairy.com/fi/guides/embed-ticket-checkout-on-your-own-site)
- [How do you connect ticketing to your email marketing?](https://www.ticketfairy.com/fi/guides/connect-ticketing-to-email-marketing)
- [How do you give fan clubs presale access to your tickets?](https://www.ticketfairy.com/fi/guides/give-your-fans-presale-access)
- [Kaikki Ticket Fairy -oppaat](https://www.ticketfairy.com/fi/guides)

## Tee tämä omassa tapahtumassasi

Luo tili, rakenna tapahtumasi ja seuraa näitä vaiheita omassa hallintapaneelissasi. Ilman myyntipuhelua.

  [Luo ilmainen tili](https://manage.ticketfairy.com/welcome) [Varaa esittely](https://www.ticketfairy.com/fi/event-ticketing/book-a-demo)