Yes. SleekView reads the synced comments and reactions from wp_comments and Disqus meta written by the Disqus plugin's Sync API. The Sync API is a checkbox in the Disqus plugin settings, and the board works as soon as the sync has caught up. Without sync, the board has no data because Disqus does not write to WordPress tables.

Yes. The board's Upvote button posts back through the Disqus Sync API, which forwards the action to the Disqus thread. The next time the embedded Disqus widget renders, the upvote count reflects the click made on the SleekView board, and Disqus reputation and notification rules apply exactly as if the click came from inside the widget itself.

The data source ties to a single Disqus shortname per WordPress site, which is how the Disqus plugin itself is configured. Within that shortname you can scope the board to specific WordPress post types, categories, or post IDs, so you can build a board scoped to a section of the site even when one shortname powers many sections.

Yes. Spam and trash actions from Disqus mirror into the synced WordPress comment status, which SleekView reads on every render. A comment marked spam in Disqus disappears from the board on the next page load, and a comment restored from the spam queue reappears with its current upvote count, all without manual cleanup steps.

No. The board reads from local WordPress storage that the Disqus Sync API populates in the background, so each visitor view of the board does not trigger a Disqus API call. Upvote clicks trigger one API call each through the Sync layer, which is identical to the cost of a regular upvote in the embedded Disqus widget.

Yes. SleekView supports multiple boards on the same page, so a single page can display a Disqus-driven feedback board and a WooCommerce reviews board side by side. Each board reads its own data source, sorts independently, and renders its own pills, which lets editorial pages combine both feedback channels in a single layout.

The Disqus plugin performs a full historical sync the first time the Sync API is enabled, which means every existing comment across every post mirrors into wp_comments with its current upvote count and reaction data. SleekView reads those rows the same way it reads new comments, so historical feedback appears on the board on the very next render.

Yes. Disqus reactions sync into custom comment meta keys, and SleekView reads those keys as additional numeric columns. You can use a specific reaction type as the sort source instead of generic upvotes, or stack multiple reactions into a weighted score that drives the board order with finer control over what counts as engagement.