Yes. Moving a card calls the Convertful API helper that the plugin already uses, so impression counts, conversion stats, and any custom code listening to Convertful events continue to fire through the normal pipeline. The Convertful workspace side stays consistent with the kanban surface.

SleekView reads the synced Convertful widget table that the plugin maintains and joins the connected mail provider list meta in the same query. You pick the synced table as the source, choose the state field to group by, and SleekView renders one card per widget with the fields you select.

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

Custom widget types and any extra status values appear automatically because SleekView reads distinct values from the chosen column. 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 campaign tag on the cards lets the same board show every widget at once. Many teams add a second board scoped to a single campaign for focused weekly reviews during a launch or seasonal promo.

Dragging never deletes data. It changes the state field SleekView is grouping by, which matches what the workspace does. Archived widgets keep their test history and can be reactivated from the same board, and only an explicit move into Trash removes the local synced widget row from the table.

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 synced widget table for the status filter. Sites with hundreds of widgets and large submission logs stay responsive because heavy fields are only fetched for cards currently on screen.