Ticket Tailor is an online box office. If you sell tickets for a gala, a quiz night or a sponsored walk through it, the integration brings the people involved into ThirdSectorBee so their involvement sits alongside everything else you know about them. You don’t need to export lists from Ticket Tailor and import them by hand.
Events belong to fundraising activities
ThirdSectorBee doesn’t copy your Ticket Tailor events as events. Instead, you map each Ticket Tailor event to a fundraising activity, either one you already have or one the sync creates for you. That’s what lets ticket income count towards the activity’s totals, next to donations and other income for the same appeal or event.
An event you haven’t mapped is left out entirely, which is useful when Ticket Tailor also holds events you don’t want in your CRM.
What comes across
| Ticket Tailor | ThirdSectorBee |
|---|---|
| Event | The fundraising activity you mapped it to |
| Ticket holder | A contact, matched by email address, with a [Ticket Tailor] Ticket issued touchpoint |
| Completed order | The buyer as a contact, and a paid payment with the payment method Ticket Tailor, linked to the activity |
| Check-in | A [Ticket Tailor] Checked in touchpoint on the ticket holder’s timeline |
The person who bought the tickets and the people who hold them can be different contacts. Only completed orders become payments: pending, refunded and cancelled orders are left out, and so are void tickets.
Enabling Ticket Tailor adds the two touchpoint types and the Ticket Tailor payment method to your beehive, so you can filter timelines and payments by them.
Information only flows one way, from Ticket Tailor into ThirdSectorBee. Buying a ticket isn’t consent to marketing, so the integration doesn’t record any.
How data arrives
Every hour. ThirdSectorBee checks Ticket Tailor for new tickets, orders and check-ins on each mapped event, until 30 days after the event ends. This is the dependable route, and the only one for check-ins, because Ticket Tailor doesn’t announce them.
As it happens. Once you add a webhook in Ticket Tailor and paste its signing secret into ThirdSectorBee, new orders and tickets arrive within moments instead of waiting for the next hourly check.
On demand. A colleague with the right permission can start a sync for every mapped event, or for one, including events that ended long ago.
However a record arrives, it’s imported once: a repeat sync or a webhook for something already imported changes nothing unless the record changed in Ticket Tailor.