Blocksify Pro provides seven condition types for controlling when a Blocksify block appears.
Where to find it
- Go to Blocksify → Dashboard → Conditions.
- Click Add New or open an existing condition.
- Under Rules, click Add rule, then open the Condition choice. The seven types appear.
Entire Site
Entire Site always passes. Use it as a broad group item or temporary always-visible rule.
| Option | What it matches |
| Entire Site | Every front-end request. Its comparison is automatic, so no Comparator or Value appears. |
Singular
Singular matches an individual entry of any public content type. Choose is or is not.
| Option | What it matches |
| All singular | Any individual public entry. |
| Post type | Entries of one available type, such as Post, Page, Product, Property, or Agent. |
| Post | After choosing a post type, optionally narrows it to named entries such as Elmsworth Villa and Rosemount Villa. After you close the picker, it summarizes these choices as 2 selected; an empty picker matches the whole type. |
| is / is not | The chosen entries, or any request outside that choice. |
Archive
Archive matches listing and special pages. Available post-type and taxonomy archives follow the site.
| Option | What it matches |
| All archives | Every archive plus the front page, posts page, 404 page, and search results. |
| Front page | The site’s front page. |
| Posts page (Blog index) | The blog posts page. |
| 404 page | A request WordPress cannot find. |
| Search results | The search results page. |
| Author archive / Date archive | Any author or date archive. |
| Post type archive | An available content-type archive, such as Properties. |
| Taxonomy archive | An available taxonomy archive, such as Property Type archive or City. |
| Term | Optionally narrows a taxonomy archive to named terms. The selected example appears as Villa (32), where 32 is its WordPress term ID; an empty picker matches every term archive. |
| is / is not | The selected archive, or any request outside it. |
User
User matches login state, role, or account. The picker includes roles added by other plugins.
| Option | What it matches |
| is logged in | Any signed-in visitor. |
| is not logged in | Any signed-out visitor. |
| has role | A visitor with at least one selected role, such as Customer or Subscriber. After you close the picker, two chosen roles appear as 2 selected. |
| doesn’t have role | A visitor with none of those roles. |
| is | One selected user. |
| is not | Anyone except that user. |
Cookie
Cookie checks an exact cookie name and optionally its value. Use is not set for a pre-signup newsletter banner.
| Option | What it matches |
| Cookie | The exact cookie name, such as northstar_newsletter. |
| is set / is not set | Whether the named cookie exists. |
| is | A value exactly equal to Expected value. |
| contains / doesn’t contain | A value that includes or excludes the expected text. |
| starts with / ends with | A value with matching beginning or ending text. |
| Expected value | Text shown only for comparisons that need it. |
URL
URL compares the case-sensitive request path without its query string.
| Option | What it matches |
| URL | The request path, such as /properties/. |
| is / is not | A path equal to or different from the pattern. |
| contains / doesn’t contain | A path that includes or excludes the pattern. |
| starts with / ends with | A path with matching beginning or ending text. |
| matches regex | A path accepted by the pattern body, entered without delimiters. |
For example, /properties/ with starts with covers Northstar Studio property paths. A query such as ?city=miami is ignored.
Device
Device uses the visitor’s browser identification, not viewport width.
| Option | What it matches |
| Desktop | A non-tablet, non-phone browser; unknown identification also falls here. |
| Tablet | Common tablet browsers. |
| Mobile | Common phone browsers. |
| is / is not | The selected class or the other classes. |
For responsive hiding, use the block’s Visibility controls described in the Section block guide.
Combining rules
At the top, ALL means AND and ANY means OR. Each group has its own ALL or ANY choice.
- Use root ANY and group ALL for OR between groups and AND within them.
- Use root ALL when every root item must pass.
- Use group ANY when one rule inside may pass.
See Create and apply a condition for a complete ANY example. Saved block visibility conditions differ from template display conditions, which choose where an entire Dynamic Template replaces a theme layout.
Note: Full-page or CDN caching can prevent User, Cookie, and Device conditions from being checked separately for each visitor. Exclude affected pages from shared caching or vary the cache safely.