Connect Eventbrite so that the events you sell tickets for appear in Events, and the people who buy tickets and attend them appear on their contact records. Once it’s running, an event’s Related tab shows its ticket income and attendance, and a supporter’s timeline shows every Eventbrite event they registered for, checked in to or cancelled.
Before you start
- Eventbrite must be switched to Enabled on the Integrations overview. See enable a service first.
- Connecting, pausing and disconnecting need
eventbrite:settings:change. Sync now needseventbrite:sync:initiate. - Have your Eventbrite private token ready. In Eventbrite, open Account settings → Developer links → API keys and copy the private token. It must belong to a user of the Eventbrite organisation whose events you want.
Connect your account
- Open Integrations → Eventbrite.
- Paste the private token into Private token and choose Connect.
- If your Eventbrite user belongs to more than one organisation, choose the one whose events belong to this beehive under Organisation, then choose Connect again.
ThirdSectorBee checks the token with Eventbrite before saving it, and the token is never shown again. Connecting starts bringing in your Eventbrite history straight away; a large account can take a few minutes.
What comes in
| In Eventbrite | In ThirdSectorBee |
|---|---|
| An event | An event in Events, with its name, summary, dates, venue, capacity and status. A live event is Published, an ended one Completed, a cancelled one Cancelled. |
| A paid order | A Paid payment from the buyer for the order’s total, linked to the event. Free orders create no payment. |
| A ticket (attendee) | A [Eventbrite] Registered touchpoint on the ticket holder’s timeline, linked to the event. |
| A check-in | A [Eventbrite] Checked in touchpoint. |
| A cancelled or refunded ticket | A [Eventbrite] Registration cancelled touchpoint. |
Buyers and ticket holders are matched to contacts by email address; a new email address creates a new contact. A ticket holder with no email address (Eventbrite only asks for one per ticket if you choose to) is not brought in.
Each Eventbrite event becomes its own event in ThirdSectorBee. If you change the event in Eventbrite, the change comes through; anything you add in ThirdSectorBee that Eventbrite doesn’t hold, such as an event manager or a programme or fundraising link, is kept.
How often it updates
When connecting succeeds, ThirdSectorBee asks Eventbrite to tell it about changes, so new orders, tickets and check-ins usually arrive within a minute or two. The page says so under the connection details. As a safety net, ThirdSectorBee also checks Eventbrite every six hours. If the page says changes arrive at the next six-hourly sync, Eventbrite could not be set up to notify us, and everything still comes in, just later.
Sync now reads every event, order and ticket again. Nothing is duplicated, so it’s safe to run whenever you think something is missing.
Pause or disconnect
- Turn off Bring in data from Eventbrite to pause without disconnecting. Turn it back on to resume.
- Disconnect Eventbrite removes the stored token and stops updates. Events, contacts, payments and timeline entries already brought in are kept.
Known limits
- A refund in Eventbrite doesn’t change the payment already recorded. The ticket shows as cancelled on the timeline; record the refund yourself.
- Ticket types are not copied onto the event, and Eventbrite’s fees are not recorded: the payment is what the buyer paid.
- An Eventbrite event can’t yet be linked to an event you already created in ThirdSectorBee; it is brought in as a separate event.