Block priority and ordering
Each storefront request asks for one specific block by its ID, so Layers always serves the block you request. Priority doesn’t pick between blocks. Rules only adjust the requested block, and a Hide Block rule hands the request to that block’s fallback chain.Priority system
Each block has a priority number:- Lower numbers come first
- The Recommendation Blocks list sorts by priority by default, so you can keep related blocks grouped in a predictable order
- Priority doesn’t change which block a request serves or the order Layers tries fallbacks in
Target different audiences
To show different recommendations to different shoppers on the same surface, configure one block and let its context decide:- Rules adjust the block for matching shoppers. For example, an Override Safeguards rule can show 16 products to desktop shoppers and 8 to mobile shoppers, or a Change Strategy rule can switch VIP customers to a personalized strategy. See Rules & Safeguards.
- Fallback branches send different shoppers to different fallback blocks. For example, US shoppers can fall back to a US best sellers block while EU shoppers fall back to an EU block. See Fallback trees.
Block status
Blocks have two statuses that control whether they are live:- Published: Block is live and the API returns it
- Draft: Block is not live and the API does not return it
Publishing and unpublishing
You can control a block’s status directly from the block editor using the Publish and Unpublish buttons in the page header:- When creating a new block, click Publish to save and immediately make it live, or click Save Changes to save it as a draft.
- When editing a published block, click Unpublish to revert it to draft status without deleting it.
- When editing a draft block, click Publish to make it live.
- Testing new block configurations before going live
- Temporarily disabling blocks without deleting them
- Preparing seasonal blocks in advance
Filtering by status
On the blocks list page, you can filter blocks by their publication status using the Published column filter. Select Published or Draft to narrow the list. The Published column shows a single badge that combines publication status and strategy readiness. A published block whose strategy data is still computing shows Publishing with a spinner. A block whose data computation failed shows Failed, and a block whose data is live shows Published. See Data-is-computing state for details.See also
- Blocks Overview - Overview of blocks and anchor types
- Strategies - Strategy types and availability
- Rules & Safeguards - Conditional rules and safeguard configuration
- Blocks API Reference - API documentation for retrieving block products