Bricks Builder Integration

What it does

The Bricks Builder integration extends Bricks’ built-in Conditions panel with two new condition types: User Tag (does the visitor have, or not have, a given Keap tag?) and User Conditional (does the visitor satisfy a saved iMEMBER360 Conditional?). You attach these conditions to any element directly on the Bricks canvas — no shortcodes wrapped around content, no separate “members-only” page versions, no custom code.

Because Bricks evaluates conditions server-side before rendering, protected content never reaches an unauthorised visitor’s browser. Your pages stay fast, your cache stays valid, and your member experience stays in lockstep with your Keap CRM.

Key features

• User Tag condition — show or hide elements based on one or many Keap tags
• User Conditional condition — drive visibility from any saved iMEMBER360 Conditional (login state, role, contact field, date logic, etc.)
• Works on any Bricks element: sections, containers, blocks, widgets, popups, and template parts
• Combine with Bricks’ native conditions (logic operators, page context, browser data) for compound rules
• Conditions evaluate server-side — protected content never leaks to the browser, cache-friendly
• Re-use the same Keap tag or Conditional across as many Bricks elements as you like

Works well with

Pair the Bricks integration with these iMEMBER360 features for the full member experience:

• Conditionals — build the saved Conditionals Bricks reads from
• Content Protection — site-wide page and post protection
• Tag Automation — apply tags from WordPress events Bricks can react to
• Shortcodes — embed personalised Keap data inside Bricks Text elements

Other builders we integrate with: Elementor, Oxygen, Beaver Builder, WordPress Block Editor.