Yes. Moving a card calls wp_update_post and the Thrive Leads test helpers, the same functions the admin uses, so impression counts, conversion stats, and any custom code listening to Thrive form events continue to fire through the normal pipeline without any extra plugin glue or workarounds.

SleekView reads the Thrive Leads form post types directly and joins the lead group taxonomy and impression meta in the same query. You pick the form post types as the source, choose the state field to group by, and SleekView renders one card per form with the fields you select for the card front.

Yes. SleekView ships with role-based permissions, so marketers can have a single page that holds the forms board and nothing else. Only chosen roles can drag cards, and destination columns can be limited per role so contributors cannot promote tests into Live without a manager's approval move.

Custom form types and test states appear automatically because SleekView reads distinct values from the chosen field. You can rename column headers, pick colors, and decide whether marketers can drag cards between any two columns or only along an approved campaign launch path.

Yes. Each board has one source so the rules stay clear, and the lead group taxonomy can act as a card filter so the same board surface covers every group. Many teams add a second board scoped to a single campaign lead group for focused weekly reviews.

Dragging never deletes data. It changes the state field SleekView is grouping by, which matches what the admin screens do. Archived forms keep their conversion history and can be reactivated from the same board, and only an explicit move into Trash removes the underlying form post.

Yes. Each card can show the time since the test started or last reached a milestone, so a test that has been running for weeks looks visibly different from a fresh one. Sort options can also place the oldest cards at the top of every column so stale tests never silently drift out of view.

No. SleekView pages the board, only loads cards for visible columns, and uses indexed queries on the form post types and Thrive meta. Sites with thousands of forms across many campaigns stay responsive because heavy meta is only fetched for cards currently on screen during a review session.