It actually renders and hides. SleekView writes the campaign_status meta back to the Icegram campaign post and the Icegram frontend module reads that meta on the next page load to decide whether to inject the message. The local card state and the actual message render state stay in sync because the same drag drives both writes through the Icegram post meta.

Use campaign_status for the primary lanes since it carries the exact states Icegram tracks. If you want a board that splits by message type, compose the group-by from campaign_status plus message_type so the same kanban can show lightboxes, action bars, toasts, and inline messages either combined into status lanes or split into type columns.

Yes. Add a site_id filter to the kanban view so the board only shows campaigns running on that site. Save the filtered URL for each brand and every site team gets a focused board of their own campaigns while the same Icegram install drives every kanban in the network without any data duplication or cross-site contamination.

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. You can add a typed confirmation modal for the Live lane for an extra guardrail when production traffic is at stake.

No. The kanban writes only the campaign_status meta and schedule meta that Icegram already updates from its own editor. Impression tracking, click attribution, and conversion measurement all continue to run inside Icegram exactly as before, and the rates displayed on live cards read from the same Icegram analytics meta keys the editor uses on its analytics screen.

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

Yes. SleekView reads any SQL view, so you can join the Icegram campaign post type 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 Icegram plugin, and writes can be selectively enabled on a field-by-field basis from the view config.

Yes. The kanban config stores column references against logical Icegram field names, not row IDs, so when Icegram refreshes its schema the same lanes still render against the new rows. Plugin updates that add new Icegram campaign states show up automatically as new lanes the first time a campaign in that new state lands in the post type.