No. SleekView Feedback reads directly from the synced Eventbrite post type and meta that the plugin already maintains. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders on the next page load. Nothing is duplicated and the sync keeps running untouched.

Yes. SleekView ships with anonymous voting backed by cookies so any visitor can vote on synced Eventbrite events without an account. You can also require WordPress login if you want the board restricted to past ticket holders or members, and the same view handles both modes through a single setting.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by WordPress user ID. The plugin exposes a per IP rate limit so a single household cannot spam the board, which keeps the score honest without forcing a signup wall in front of every attendee.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can filter by start date, organiser, venue, or any synced meta key. A second board on a different page can show past events as a public archive while the homepage only lists upcoming dates and tiers.

Bug and Idea are just category values on the row. They appear in the WordPress admin alongside the synced Eventbrite event, so the same person handling refunds can see and resolve them without bouncing between Eventbrite, WordPress, and a separate ticketing tool.

They write back to the synced row in WordPress, which is the source of truth your scheduling and reporting already use. Your own queries and the Eventbrite Tickets blocks can sort upcoming events by score, which means the board drives what you plan next instead of being a vanity metric on a page.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any event archive, single, or landing page without touching the page editor.

The view paginates server side and only loads the rows needed to render the current page. Indexed meta keys stay fast even on long tables. For busy organisers, scoping the board by venue, organiser ID, or upcoming dates keeps both the query and the audience focused, so the page feels snappy even at scale.