No. SleekView reads the existing post meta and response cache that the Pirsch WordPress plugin writes during its sync. The only write is the upvote increment, which lands on a meta key you choose so it sits next to the rest of the post data without touching the Pirsch account, dashboard, or API settings at all.

Yes. The Upvote button supports guest votes with a per-session lock to keep counts honest, which fits the cookieless Pirsch posture. If you would rather restrict votes to logged-in users or to specific roles like Editor or Contributor, you can flip that in the view settings.

You map a review_status meta key when you build the view. SleekView shows a colored pill for each value, and any URL without a status simply renders without a pill rather than blocking the card from showing. Editors can update the status by editing the post or via a custom admin column.

Yes. You can pick a cached Pirsch custom event count instead of visitors as the vote weight when you build the view. That ranks the board by conversions, which is the right metric for landing pages and signup funnels rather than top-of-funnel content.

Yes. Every saved view has its own role and capability scope, so you can publish a public Top Pages wall on the homepage and a separate Editorial Triage queue that only Editors and Authors can see. Both views share the same Pirsch cache underneath the surface.

When the underlying post is deleted, SleekView removes the card on the next refresh. If the post is trashed rather than fully deleted, the card disappears from the public view but the upvote meta is preserved on the trashed post in case you restore it from the trash later.

Yes. Every SleekView is available as a shortcode and a Gutenberg block, so you can drop a Top this week view onto the homepage, embed a Needs update view on an internal Wiki page, or stitch several views into a single editorial dashboard with separate columns side by side.

SleekView paginates and sorts at the database level rather than loading every meta row into memory, so a site with thousands of posts and a deep Pirsch cache still renders the top of the feedback board in well under a second on a normal shared host. Aggregation queries hit indexed columns by default.