No. SleekView Feedback reads directly from the cp_module post type and any meta or stats tables Convert Plus already maintains. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. Nothing is duplicated, nothing has to sync.

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

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

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can filter by module_status, type, or any meta key Convert Plus writes. A second board on another page can show retired modules as a public archive while the homepage board only lists live optins.

Bug, Idea, and Request are just category values on the row. They show up in WordPress alongside the source module, so the same person editing optins can see and resolve them without leaving Convert Plus. You can also export them as a CSV for a separate support workflow if needed.

They write back to the source column, so your own queries, dashboards, and any custom reports can sort future modules by score. Several publishers use the score to gate which optins keep impressions and which lose them, which makes the board operational instead of just a widget.

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 page 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.