Any column the plugin writes to the attempts records, plus joined fields from the quiz custom post and the result rows. Common picks are quiz_id (rendered as the quiz title), result_id (rendered as the result label), started_at, finished_at and any utm fields. The agent UI lists what the installation actually has.

No. SleekView reads attempts QuizCat has already stored. Result routing and quiz logic stay with the plugin. The table only exposes the rows it already has, which is the honest behaviour rather than a synthesised summary.

Yes. Select rows, pick a new value (such as deleted = true for test attempts), and SleekView routes the change through CRUD so listening hooks still fire. Direct table edits are available for back-fills where downstream effects are not wanted.

Yes. QuizCat writes the same attempt and result records regardless of tier, and SleekView only needs those plus the quiz custom posts.

Yes. Add the utm source field as a column and filter by source value. A newsletter-driven cohort or a paid-ad cohort surfaces in one view across every quiz.

Yes. Each saved view captures column set, filters and sort order. Gate by WordPress capability so editors see content review, marketing leads see source-driven slices and clients see a read-only summary.

Yes. Any filtered attempt set exports as CSV with the same columns the view shows. Useful for a follow-up sequence on a high-intent result or for archiving a snapshot before a campaign clean-up.

No, it is an additional admin surface. QuizCat's own screens stay where they are. SleekView gives marketing, agencies and lead-gen operators the cross-campaign workbench they actually need without disturbing the plugin's per-quiz workflow.