Eventbrite Integration pulls the Eventbrite Attendees API into local WordPress storage on a schedule. Each attendee lands in a cache table with the Eventbrite attendee ID, the order ID, the ticket class name, and a status field like attending, checked_in, refunded, or not_attending, plus the gross amount and currency from the order. The plugin Attendees screen shows those rows as a list per event, with status as a column label and very few filters.

SleekView Kanban reads the same local cache table and groups attendees by status into columns. The board shows Attending, Checked in, Not attending, and Refunded with a count at the top of each column and a card per attendee. Each card carries attendee name and email, event title, ticket class, and gross amount, so the front of the card holds what an organiser needs to act on the row without opening the Eventbrite dashboard in another tab.

Dragging the card updates the local cache row to reflect a local annotation: a marked-attended override, a flagged-for-followup note, or a tagged-as-vip label that the team adds beyond what the Eventbrite API stores. The sync still pulls the authoritative state from Eventbrite on the next run, so the board surfaces both the synced state and the local annotations side by side. Refunds and check-ins issued through Eventbrite continue to flow into the board through the standard sync.

Eventbrite Integration is designed as a frontend layer: the plugin pulls events and attendees from the API so the website displays accurate information without the team logging into Eventbrite. The Attendees screen is a per-event list that mirrors the Eventbrite Attendees report, which is fine for a quick check but unwieldy when an organisation runs ten or twenty events at the same time and wants to handle VIP coordination, sponsor outreach, and followup as a single team workflow. SleekView Kanban reads the same local cache the plugin populates and lays it out as a working board with Attending, Checked in, Not attending, and Refunded columns.

Eventbrite stays the source of truth for synced status, and SleekView adds the local working layer the plugin does not: VIP tags, followup notes, sponsor flags, and an audit log of who acted on which attendee. Refunds and check-ins issued on Eventbrite continue to flow in on the next sync, so the board never drifts from the canonical state held by the API. The team gets a single board to coordinate around, and the website still reads the same accurate event data the plugin was built to deliver.