It actually renders and hides. SleekView writes the campaign_status back to the Bloom campaign row and the Bloom frontend module reads that status on the next page load to decide whether to inject the optin. The card state and the live optin render state stay in sync because the same drag drives both writes through the Bloom campaigns table.

Use campaign_status for the primary lanes since it covers the exact states Bloom tracks. If you want a board that splits by display type, compose the group-by from campaign_status plus display_type so the same kanban can show popups, fly-ins, inline forms, below-post optins, widgets, and locked content either combined into status lanes or split into type-specific columns.

Yes. Add a filter on the Bloom targeting rules so the board only shows optins targeting a specific category or page. Save the filtered URL for each scope and the team responsible for that category gets a focused board on their own optins. The same Bloom plugin drives multiple boards without any duplication of the underlying campaign rows.

Yes. SleekView only changes the campaign_status field, which is the same field the Bloom editor toggles when you publish or unpublish an optin. All of Bloom's display rules, frequency caps, cookie-based suppression, and exit-intent triggers continue to run exactly as before. The kanban is the activation surface, not a replacement for Bloom's display logic.

Nothing harmful. SleekView reads native WordPress capabilities and you set which roles can drop into the Live lane. For designers and writers the Live lane becomes a non-drop target and the card snaps back to its previous lane. You can add a typed confirmation modal for the Live lane to add an extra guardrail when production traffic is at stake.

No. The kanban writes only the campaign_status field that Bloom already updates when you publish or unpublish from its own editor. Impression tracking, conversion measurement, and the Bloom statistics tab all continue to run exactly as before, and the rates displayed on live cards read from the same conversion_rate field Bloom uses on its statistics screen.

Each lane paginates independently. The Live and Scheduled lanes carry only the small number of currently active optins so they always render instantly. The Paused lane lazy-loads on scroll, so a year or two of archived optins sit comfortably in the column without slowing rotation work in the active lanes used for daily campaign management.

Yes. SleekView reads any SQL view, so you can join the Bloom campaigns table to a custom approvals table or a postmeta key that stores the assigned designer or copywriter. The joined columns become available as card fields without modifying the Bloom plugin, and writes can be selectively enabled on a field-by-field basis from the view config.