How each Ticket Tailor record is turned into ThirdSectorBee records. To set the integration up, see Connect Ticket Tailor.
Data mapping
| Ticket Tailor record | ThirdSectorBee result |
|---|---|
| Event mapped to an existing activity | The fundraising activity you chose; every payment and touchpoint from the event is linked to it |
| Event mapped to a new activity | A fundraising activity with the name you gave, and the activity type Event. It’s created once; later records reuse it |
| Issued ticket | The ticket holder as a contact, resolved by email address, and a [Ticket Tailor] Ticket issued touchpoint (inbound), timestamped when the ticket was issued. First and last name are filled in only when Ticket Tailor has them, so a blank name never overwrites a name you already hold |
| Completed order | The buyer as a contact (resolved by email), and a payment: amount and currency from the order, status Paid, direction inbound, date paid from when the order was placed, payment method Ticket Tailor |
| Check-in | The ticket holder’s contact and a [Ticket Tailor] Checked in touchpoint (inbound), timestamped when they checked in |
The buyer and the ticket holder can be different people, so an order and a check-in for the same ticket can land on different contacts. No consent is recorded, and nothing is written back to Ticket Tailor.
The two touchpoint types and the Ticket Tailor payment method are added to your beehive when Ticket Tailor is enabled for it. If your beehive already had a payment method called “Ticket Tailor”, yours is kept as it is, and imported payments aren’t linked to it.
What brings records in
| Route | What it covers | When |
|---|---|---|
| Hourly check | Every mapped event that hasn’t ended more than 30 days ago: tickets, orders and check-ins | Every hour |
| Webhook | The single order or ticket Ticket Tailor tells us about (ORDER.CREATED, ORDER.UPDATED, ISSUED_TICKET.CREATED, ISSUED_TICKET.UPDATED) |
Within moments, once you’ve added the webhook in Ticket Tailor and saved its signing secret here |
| Sync now | Every mapped event, or one, including events that ended long ago | When someone with tickettailor:sync:initiate starts it |
Ticket Tailor doesn’t send a webhook for check-ins, so check-ins always arrive through the hourly check or a manual sync.
A webhook delivery is accepted only when it carries a valid Tickettailor-Webhook-Signature made with the signing secret you saved, and was sent within the last five minutes. A delivery that fails this check is refused, and Ticket Tailor shows it as failed in its own webhook log. When the signature is present but doesn’t match, or is too old, the Settings tab also shows the most recent refusal and why.
Duplicates and repeats
- Each ticket, order and check-in is imported once. A later sync or webhook for the same record changes nothing unless the record changed in Ticket Tailor, in which case the new details are sent (for example, a corrected name on a ticket).
- A payment or touchpoint is never created twice for the same Ticket Tailor record, even if a webhook and the hourly check both pick it up.
Skips and limits
- Events without a mapping are not imported.
- Only completed orders become payments. Pending orders (awaiting payment) are imported once they complete; refunded and cancelled orders are never imported. A free order brings its buyer in as a contact but records no payment.
- A ticket holder without a name, at the same email address as the buyer, is treated as the buyer, so the two don’t become separate contacts. Such tickets arrive with the hourly check rather than the webhook, because only the check sees the order alongside the ticket.
- If you switch off one of the Ticket Tailor touchpoint types in your touchpoint settings, those touchpoints stop being recorded; the contacts still come in.
- Void tickets, and check-ins on them, are not imported.
- A refund, cancellation or void after a record was imported doesn’t change what was recorded. Update the payment in ThirdSectorBee.
- A ticket or order Ticket Tailor returns without an email address can’t be matched to a contact and is skipped.
- The History tab keeps 90 days of webhook deliveries, manual syncs, and hourly checks that imported something.