No. SleekView Feedback reads directly from the synced ConvertBox Pro post type and any meta or option rows the integration writes. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. Nothing has to sync.

Yes. SleekView ships with anonymous voting backed by cookies so any visitor can upvote a flow without an account. You can also require login if you want the board restricted to staff, paying members, or a beta cohort, and the same view handles both modes with a setting.

Each visitor gets a cookie scoped vote token per item, and logged in users are tracked by user ID. The plugin exposes a rate limit per IP so a single browser cannot spam the board, which keeps the score honest without forcing every subscriber to create an account first.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can filter by the live flag, the audience field, or any meta key the ConvertBox Pro sync writes. A second board on a separate page can show retired flows as an archive while the homepage lists live.

Bug, Idea, and Request are just category values on the row. They show up in WordPress alongside the synced ConvertBox Pro post, so the same person editing flows can see and resolve them without leaving the dashboard. You can also export them as a CSV for support.

They write back to the synced column inside WordPress. Your own queries, dashboards, and reports can sort future multi step flows by score. Several publishers use the score to gate which conditional branches get more impressions, which makes the board operational.

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 template without touching the editor.

The view paginates server side and only loads the rows it needs to render the current page. Indexed columns stay fast even on long tables. Scoping the board by active campaign or recent date keeps both the query and the audience focused, so the page feels snappy at scale.