Understanding Block and Condition Availability by Page
What you will achieve in this guide
Follow the feature-specific setup and testing instructions below. Check the supported pages and plan requirements before activating the feature.
The available condition inputs depend on the page. A condition that works in checkout may be unavailable or ignored on an account surface; choose the page and data together.
Key distinctions
| Page | Condition availability |
|---|---|
| Checkout | Eligible supported checkout/cart/customer/shipping inputs; checkout UI placement requires Plus. |
| Thank you / Order status | Available order/customer inputs; selected shipping method is unavailable on Order status; Days since order is supported only on these post-checkout surfaces. |
| Profile | Only Customer, Language, Market, and Time on page conditions are evaluated; cart/order conditions are ignored. |
How this feature works
Conditions control when an already-placed block is visible. Use all/AND when every condition must match and any/OR when one matching condition is sufficient, where the form exposes those controls. The target page must supply the input: cart, shipping, order, and customer data are not interchangeable.
Before you begin
Checkout-step visual blocks require Shopify Plus. Supported Thank you and Order status blocks are available on Basic and higher. Check the page labels on the block’s Rivio card; a card does not necessarily support every page.
Worked example: Use conditions that the chosen page can evaluate
Example setup: A Profile block and a separate checkout or post-checkout block.
Step-by-step instructions
Open the block card and confirm the intended page is supported.
For a checkout block, choose a supported input available during checkout, such as cart contents or shipping country.
For Thank you/Order status, use the available order/customer context; do not use selected shipping method on Order status.
For Profile, limit conditions to Customer, Language, Market, and Time on page. Cart/order conditions are ignored there.
Save the active configuration and exact editor placement.
Test the relevant signed-in customer, completed order, or checkout session; compare a non-matching case.
Verify the result
| Test case | Expected result or verification |
|---|---|
| Profile with cart/order condition | Do not expect that condition to restrict visibility. |
| Order status selected-shipping-method condition | That input is unavailable. |
| Supported Customer condition on Profile | Test a matching and non-matching signed-in customer. |
If the result is different
| Check | What it means / what to do |
|---|---|
| Unexpected buyer sees content | Review all/AND versus any/OR and the selected condition values. |
| Customer tag does not match | Test with the intended logged-in customer; anonymous checkout may lack tag context. |
| Condition works on another page only | Check the page’s supported inputs; Profile ignores cart/order conditions and Order status lacks selected shipping method. |
Check page-specific data
Customer-tag conditions require logged-in customer context. Selected shipping method is unavailable on Order status. Days since order is available only on Thank you/Order status. On Profile, only Customer, Language, Market, and Time on page conditions are evaluated; cart/order conditions are ignored.
Related guides
- How to Conditionally Show Shopify Checkout Blocks
- How to Show Shopify Checkout Blocks Based on Customer Tags
- How to Show Checkout Blocks Based on Shopify Markets
Need help?
Email support@rivioapps.com with your store domain, feature name, target page, the relevant settings, and a screenshot of the actual result. Include the test cart, customer, or order details needed to reproduce the issue.
Screenshot reference
Screenshot to add: The saved settings described in this guide, with its selected conditions or scope visible.
Screenshot to add: The worked example’s actual customer result or saved Shopify record, including the relevant test inputs.
Was this article helpful?
Your feedback helps us continuously improve our setup guides and documentation.
Thank you for your feedback! Our documentation team reviews all suggestions.