Data mapping
| Ticket Tailor record | ThirdSectorBee result |
|---|---|
| Mapped event | Existing fundraising activity, or an activity created during sync |
| Attendee | Contact resolved using email |
| Order | Buyer contact and inbound Paid payment linked to the activity |
| Check-in | Attendee contact and inbound Attendance touchpoint linked to the activity |
The buyer and attendee can be different people. Ticket Tailor mappings do not create Events-module records.
Triggers and processing
Use Sync this event for one mapped event or Full sync now for all mapped events. Correctly signed webhooks can dispatch order, attendee, and check-in updates as they arrive. Connection instructions explain the current webhook setup limitation.
Imports are processed asynchronously, so records may appear after the sync response. Already processed order and check-in IDs are skipped to avoid repeated payment and touchpoint creation. Attendee details can be refreshed by another sync.
Skips and limits
- Events without a saved mapping are skipped.
- Refunded and cancelled orders are not imported as Paid payments. A later refund or cancellation does not reverse an already imported payment through this integration.
- A check-in needs previously synced attendee details. A full sync processes attendees before check-ins.
- Webhook requests without a valid signature are discarded.
The History tab displays webhook notifications, including event type and status (OK or Error). It is not a full import audit. If data is absent, check mappings and signing, run a manual sync, and inspect the resulting records as well as the webhook history.