Conditions

Conditions help personalize account content. Use conditions when content should only appear for certain customers or situations. Examples:

• Show VIP content to customers with a VIP tag.
• Show a first-order offer to customers whose verified order count is zero.
• Show support information based on customer or order context.

​

Add and test a condition

1. Choose the page, section, or block whose visibility you want to change.
2. Open its Visibility controls and attach a saved condition or add a rule.
3. Choose the field, operator, and expected value.
4. Select All rules or Any rule deliberately.
5. Save, then test customers who should match and customers who should not.

For a VIP message, use a customer-tag condition for the exact VIP tag your store uses. For an order-specific rule, use a location with verified order context. A general account page cannot supply every order field. All rules means every rule must match. Any rule means at least one can match. A child block remains hidden if its parent page or section is hidden. Conditions are display controls, not a way to grant access to another customer’s orders or private information. Do not use missing data as evidence that a customer belongs to an audience.

​

Reusable condition library

Account Canvas includes a reusable condition library. Merchants can create a condition once, then reuse it across blocks, sections, and pages. Each condition supports:

• All rules logic, where every rule must match.
• Any rule logic, where at least one rule must match.
• Reuse by condition ID or condition name inside other display rules.

​

Supported condition families

Account Canvas currently supports condition fields across:

• Customer identity, tags, created date, order count, amount spent, marketing state, store credit, default address, and B2B state.
• Order identity, lifecycle status, financial status, fulfillment status, return status, processed date, and order value.
• Line item quantity, product title, variant title, price, and discount state.
• Product ID, tags, vendor, type, and availability.
• Market language.
• Shop name, domain, and currency.
• Current date, day, month, and year.
• Customer, order, product, and shop metafield values when configured.

Some Shopify-backed context depends on the customer account surface and the permissions available to the app.

​

Supported operators

Available operators depend on the field type:

• Text: exists, missing, equals, does not equal, contains, does not contain, is in list, and is not in list.
• Numbers: exists, missing, equals, does not equal, greater than, less than, greater than or equal, less than or equal, between, and not between.
• Lists: exists, missing, contains any, contains all, contains none, count equals, count greater than, and count less than.
• Dates: exists, missing, on, on or before, on or after, between, in the last N days, and more than N days ago.
• Booleans: is true and is false.

​

Where conditions are used

Conditions can be assigned to:

• Saved blocks
• Saved sections
• Individual blocks inside a page
• Page-level visibility rules

If a condition does not match, Account Canvas hides that content before it is shown in the customer account experience. Order, line-item, and product rule families require Pro or Advanced; B2B and metafield rule families require Advanced. Store capabilities and permissions still apply. See plans and limits and troubleshooting.