Integration

Zembula + Eventbrite

Eventbrite flags whether each attendee checked in, cancelled or was refunded, and Zembula can show that in an email. Zembula can read an attendee by attendee id or event id.

It's our business to grow yours

Book a demo

What Zembula can read from Eventbrite

Eventbrite is a ticketing and registration platform with a public REST API. Zembula can read four kinds of data from it. An attendee is one registered person on an order, with the ticket class and the flags for check-in, cancellation and refund. The attendee profile adds the name, the email address, the phone number, the company and the job title.

An order records one purchase with its status, its costs and the event it belongs to. An event holds the name, the summary, the start and end times, the page URL, the status and the currency. Zembula can read an attendee by attendee id or event id, an order by order id and an event by event id. Eventbrite sends webhooks when an order is placed, updated or refunded, when an attendee is updated or checks in, and when an event is created, published or updated.

Klaviyo uses them to sync a Bought Ticket event for each attendee with a valid email address. By default, Eventbrite allows 2,000 calls an hour for each token. A private token from the API keys page of your account covers the connection.

DataDetailLooked up by
AttendeeOne registered person on an order, with ticket class and profile.attendee id or event id
Attendee statusWhether the attendee checked in, cancelled or was refunded.attendee id or event id
OrderOne purchase, with its status, costs and event.order id
EventAn event page with name, dates, URL, status and currency.event id

How the data arrives

  • API: Zembula can read attendees by event, orders by order id and events by event id.
  • Webhook: Eventbrite sends events such as order placed, attendee checked in and event published.
  • ESP merge tags: Klaviyo syncs a Bought Ticket event for each attendee with a valid email address.

What you need

  • An API key or a data export from Eventbrite. Zembula sets up the connection for you.
  • A private token from the API keys page of your Eventbrite account.
  • The attendee id, order id or event id in your email service provider, sent as a merge tag.

Limits to plan for

LimitWhat it means
2,000 calls per hour by default for each token.Opens above this hourly rate fail to read.

Ideas for email

  • Remind an attendee of the event with its start date and page URL.
  • Send a post-event email only to attendees who checked in.
  • Recover an abandoned order with the event and the order status shown.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.