WP Event Aggregator imports events from external sources and stores them as posts in WordPress with sync meta keys like _eventbrite_id and _meetup_event_id on the post. Comments on the imported event page hold post-event opinions, the rating add-on writes scores into the post's meta, and the team often gets topic requests in a separate form. Three readers, three screens, one audience.

SleekView Feedback collapses those into a single board. It reads wp_comments joined to the synced event post, the rating meta rows, and any topic request submissions from the confirmation page. Each row renders as a card with the title, running vote count read from comment or rating meta, the author, a category pill for the topic, and a status pill bound to the organiser response field. The card front carries the sync source label so an Eventbrite event reads differently from a Meetup event on the same board.

Upvote writes the increment back to meta on the row. Submit lands a new topic request as a comment on the closest upcoming event with the category preset. The board export writes the top cards to CSV with the sync source so the programme team can see which platforms drive which topics for the next planning round.

WP Event Aggregator solves the import problem and leaves the team with one calendar to manage. The reporting problem starts when the events finish, because the team now reads comments on Eventbrite-sourced posts, ratings on Meetup-sourced posts, and emails about Facebook-sourced posts, all in different screens. SleekView Feedback fixes that by reading every comment and every rating on every synced post on the same board, with the sync source visible as a pill on each card so the team can still tell where each opinion came from.

The Berlin Eventbrite event and the Vienna Meetup show up side by side, votes accumulate from real attendees, and the highest cards win the next planning round whether the original event ran on Eventbrite or as an ICS feed. The audience stops repeating the same request on three platforms, and the team stops merging three reports into a single planning sheet.