No. SleekView Feedback reads directly from whatever table, post type, or meta key Turnstile and your form plugin are 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 any of your sites.

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 the block settings panel.

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 Turnstile 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 login form events, contact form events, checkout events, or any combination of fields your Turnstile integration already stores. Different boards on different pages can use different filters at once.

False rejection is just a category value on the row. You can write it into a meta key your form plugin already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original event, so the admin tuning the widget can see the flag without leaving WordPress.

Turnstile itself does not change, but the upvote writes back to your local data. Your own queries, dashboards, and form tuning can sort by that score, which means decisions about which forms to keep covered and which widgets to retire become data driven instead of guesswork from a busy admin.

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 or training the editors.

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 sites, scoping the board by form ID or recent date range keeps both the query and the audience focused, so the page feels snappy at scale.