Blocksify Pro visibility conditions are reusable rule sets that decide whether a Blocksify block appears on a rendered page.
What is a visibility condition?
A saved condition is a named set of rules kept in Blocksify → Dashboard → Conditions. You can select the same condition on each Blocksify block that provides the Visibility panel.
The list shows each friendly condition name and its Active status. The Applies to column can use compact wording such as user is_logged_in, cookie is_set, and archive is.
For example, Northstar Studio can keep one Members Only condition and apply it to calls to action across Properties, Agents, and the WooCommerce shop. Editing that saved condition changes what all attached blocks test the next time their pages are rendered.
How do visibility conditions work?
Each condition contains rules and optional groups. Choose ALL when every item must pass, or ANY when one passing item is enough; each added group has its own ALL or ANY choice.
Blocksify Pro checks the selected condition when WordPress renders the front end. If it passes, the block is included; if it fails, the block is not rendered at all. The editor does not show a live visitor-specific result, so test the published page in the relevant states.
- Go to Blocksify → Dashboard → Conditions.
- Click Add New.
- Enter a Name and add one or more rules.
- Click Save changes.
- Edit a page, select a block, and choose the saved item under Visibility → Condition.
If a selected condition is later deleted, moved to Trash, or cannot be read, Blocksify Pro leaves the block visible. This prevents a broken reference from silently removing important content.
Warning: Full-page or CDN caching can serve one rendered result to many visitors. Exclude pages with User, Cookie, or Device rules from shared caching, or configure the cache to vary safely for those differences.
Why use saved conditions?
Reuse one audience rule
Apply Members Only to several blocks instead of rebuilding login checks page by page. A single edit keeps those placements aligned.
Target pages and visitors together
Combine page context with visitor context. Northstar Studio could show a call to action on Villa listings only when the visitor is logged in, or show a newsletter banner only when its cookie is not set.
Keep content out of the page output
A failed condition removes the block while WordPress builds the page. This is different from the device visibility toggles described in the Section block guide, which are intended for responsive presentation.
Continue with Create and apply a condition, then use the Condition types reference to choose exact rules. For a map of every Pro control area, see Where Blocksify Pro appears in WordPress.