On Eventbrite's servers. Eventbrite is the system of record for events, attendees, ticket sales, and check-ins. WordPress integrations are read-mostly clients — they either embed Eventbrite's widgets at runtime or sync events into a local cache (custom post type, transient, or option) that becomes stale until the next sync.

Whatever your Eventbrite integration plugin caches locally. That might be a custom post type with synced events, a transient with the latest API response, or a JSON blob in wp_options. The agent UI walks each common storage location and helps you confirm which one applies to your plugin so the table can read it directly.

Generally no. Most Eventbrite WordPress integrations are one-way (Eventbrite to WP). SleekView's edits stay in your local cache by default and get overwritten on the next sync. If your plugin exposes a write-back API, you can wire that into SleekView's update flow, but the safe assumption is read-only with edits informational rather than canonical.

No — that plugin was closed in 2020 and is not available on WordPress.org anymore. Most teams today rely on third-party integrations or embed Eventbrite's own widgets directly. SleekView works with whichever you use, as long as the integration caches data locally in some form. Pure-embed setups have no local data to read.

If your integration caches the sold count, yes. If it only embeds Eventbrite's widget without caching, the count isn't in your database — you'd need a sync-enabled plugin or a small custom sync via Eventbrite's API to populate the local cache. The agent UI is upfront when the relevant column doesn't exist locally.

If you want events to live in WordPress (and own the data), yes — and SleekView has a dedicated view for that. Eventbrite makes sense when you specifically want Eventbrite's ticketing, attendee management, and discovery network. Many teams run both and pair the two SleekView views to cover the full event portfolio in one admin.

That depends on your integration's sync schedule. Most plugins sync on a cron (hourly or daily) and on manual trigger. SleekView shows the last-synced timestamp as a column when the integration writes one, so the team sees how stale the snapshot is before making decisions. For real-time check-ins, fall back to Eventbrite's dashboard or app.

The cached data layout will change because each plugin stores it differently. SleekView's agent UI re-discovers the new schema, so you rebuild the saved views once after the migration. The Eventbrite event IDs themselves stay stable across integrations because they come from Eventbrite, which makes mapping old views to new fields straightforward.