No. SleekView Feedback reads directly from whatever subscription CPT, commission table, or webhook log the bridge uses. 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. Anything the bridge writes appears on next load.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote billing issues without a login. You can also require login if you want the board restricted to verified subscribers only, and the same view handles both modes with a single toggle in the block settings.

Each visitor gets a cookie scoped vote token per item. Logged in subscribers 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 billing boards honest without forcing a separate signup wall in front of unhappy customers.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to one product, one campaign, or any combination of dimensions the bridge already tracks. Different boards on different pages can use different filters per product or affiliate segment.

Affiliate Tracking is just a category value on the row. You can write it into a meta key the bridge webhook log already understands or a dedicated column on a commission table. Either way it shows up in the WordPress admin alongside the original event, so the manager can act without leaving WordPress.

They write back to the source column on the WordPress side, which means your queries and the synced subscription CPT can sort by that score. Several SaaS teams use the score to escalate billing bugs and prioritise affiliate tracking fixes, which makes the board operational and not just 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 customer portal, affiliate dashboard, or roadmap template without touching the editor.

The view paginates server side and only loads the rows it needs to render the current page. Indexed columns on the webhook log stay fast even at high volume. For really busy accounts, scoping the board by product or webhook event type keeps both the query and the audience focused at peak.