From the WordPress posts and meta that the Crowdsignal plugin syncs from crowdsignal.com. Vote totals, last response timestamps, close dates, and type all sync into postmeta on the synced items. SleekView reads that data and renders aggregates from it.

Yes. SleekView Charts is read-only and never blocks or interferes with the Crowdsignal plugin's sync layer. Sync between WordPress and crowdsignal.com continues on its normal schedule; the plugin's webhook handlers and cron events all run as configured.

Yes, using the last-response timestamp as a date dimension. The granularity depends on the plugin's sync frequency, so trends reflect synced state rather than the per-second activity on crowdsignal.com itself. For most editorial use that resolution is plenty.

Drill from a chart to the Table tab to view individual response rows for surveys you have permission to see. The Crowdsignal plugin syncs response-level data for those surveys; SleekView surfaces it as a table linked from the dashboard.

Each card exports aggregated rows as CSV. Export an editorial recap of last quarter's poll leaders, hand a completion-rate summary to a research team, or archive engagement state at the end of a campaign.

The Table tab can compute a list of posts where a Crowdsignal embed appears, based on a search across post content. The chart dashboard focuses on engagement aggregates; embed-location detail lives one tab over.

Yes. Save dashboards per role: editors see top voted and closing soon, community research sees per-type response trends, engagement managers see a cross-type overview. Each saved view persists per user with role-scoped defaults.

Items synced before the totals fields were populated may have null counts. SleekView treats them as zero in numeric aggregates and excludes them from rankings until totals sync. Re-running the plugin's manual sync usually fills them in.