No. SleekView Feedback reads directly from whatever table or option key the Autopilot integration is using. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL job, no sync, no duplicated data on the site at all.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote feedback items 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 in settings.

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 a public Autopilot feedback queue honest without forcing a signup wall in front of regular site readers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one journey, one list, one segment, or any combination of fields Autopilot already stores. Different boards on different pages can use different filters at the same time for clean splits.

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

They write back to the source column in WordPress, which means your local journeys and reports can sort future actions by that score. Several teams use the score to gate which journeys get repeated, which makes the board operational and not just a vanity dashboard for the marketing lead.

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 at all.

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 really busy senders, scoping the board by journey or recent date range keeps both the query and the audience focused, so the page feels snappy.