Data mapping
| Ticket Tailor | ThirdSectorBee |
|---|---|
| Event | Fundraising activity |
| Attendee | Contact |
| Order | Payment |
Each Ticket Tailor event must be mapped to a fundraising activity before its orders will sync. Events without a mapping are skipped.
Sync triggers
| Trigger | When it runs |
|---|---|
| Webhook | Automatically, when a new order is placed in Ticket Tailor (requires webhook setup) |
| Sync this event | Manually, for a single event from the Mappings tab |
| Full sync now | Manually, pulls all events and orders from Ticket Tailor |
What happens during a sync
For each order on a mapped event:
- ThirdSectorBee looks up the attendee by email address.
- If a matching contact exists, it is updated with any new details.
- If no match is found, a new contact is created.
- A payment record is created for the order amount and linked to the contact and the fundraising activity.
- If the order has already been synced previously, it is skipped to avoid duplicates.
Skipped records
An order is skipped (not synced) if:
- Its event has no mapping in the Mappings tab.
- It has already been successfully synced in a previous run.
Sync history
The History tab shows a log of incoming webhook notifications. Each entry shows when the notification arrived, what type of event it was, and whether it was processed without error.
A Failed status means the webhook was received but processing encountered a problem. Check that your event mappings are configured correctly and that the related fundraising activity still exists.