No. SleekView Feedback reads directly from whatever post type or log table Pro writes to. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL, no sync, no duplicated data.

Yes. SleekView ships with anonymous voting backed by cookies, so public subscribers can upvote journey steps without an account. You can also require login if you want the board restricted to editors or paying members, and the same view handles both modes with a single toggle.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep public boards honest without forcing a signup wall in front of subscribers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to a particular journey, segment, or campaign type Pro already tracks. Different boards on different pages can use different filters.

Deliverability is just a category value on the row. You can write it into a meta key Pro already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original journey step, so the email ops lead can see the flag without leaving WordPress.

They write back to the source column, which means Pro and any of your own queries can sort future journeys and steps by that score. Several teams use the score to gate which branches get more traffic and which ones get retired, making the board operational and not a vanity dashboard.

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. For deep journeys, scoping the board by program or year keeps both the query and the audience focused, so the page feels snappy even at scale.