Skip to main content
Strategies define how products are selected for a block. Each anchor type supports different strategies.

Interaction strategies

Use behavioral data to find products that customers frequently interact with together. Interaction data is computed periodically based on historical events.
Products that are frequently purchased together in the same order.Supported anchors: Product, CartUse cases:
  • Product page: “Customers who bought this also bought…”
  • Cart: “Complete your purchase with these items”
Products that are frequently viewed together in the same browsing session.Supported anchors: ProductUse cases:
  • Product page: “Customers also viewed these products”
  • Browse abandonment recovery
Products that are frequently added to cart together in the same session.Supported anchors: ProductUse cases:
  • Product page: “Often added together”
  • Cart optimization
Products that customers purchased after viewing a specific product in the same session. This strategy connects browsing behavior with purchase intent, surfacing products that shoppers who viewed the anchor product ultimately decided to buy.Supported anchors: ProductUse cases:
  • Product page: “Customers who viewed this ultimately bought…”
  • Conversion-focused recommendations
  • Identifying high-intent product pairings
Products that customers viewed shortly after viewing the anchor product in the same session. Unlike “Customers Also Viewed” (which considers any two views in the same session), this strategy is directional and only counts products viewed within the next few events after the anchor. Recommendations reflect what shoppers naturally clicked into next.Supported anchors: ProductUse cases:
  • Product page: “Shoppers viewed next”
  • Guiding shoppers through a browse path
  • Surfacing tightly related follow-on views
Products that customers who bought a specific product also purchased across any of their orders. Unlike “Frequently Bought Together” (which looks at products in the same order), this strategy looks at a customer’s entire purchase history to find broader buying patterns.Supported anchors: Product, CartUse cases:
  • Product page: “Customers who bought this also bought…”
  • Long-term cross-sell recommendations
  • Discovering complementary products across separate orders
Interaction strategies require sufficient historical data to generate meaningful recommendations. While strategy data is being computed, blocks using interaction strategies automatically return empty results and defer to their fallback chain. The API response includes a _training flag during this period.

Collection interaction strategies

Use behavioral data to find products related to a collection based on how shoppers who browse that collection interact with products. Unlike product interaction strategies (which find product-to-product relationships), collection interaction strategies compute collection-to-product relationships.
Products frequently purchased by shoppers who browsed the collection.Supported anchors: CollectionUse cases:
  • Collection page: “Popular purchases from this collection”
  • Cross-sell products based on collection browsing behavior
Products frequently viewed by shoppers who browsed the collection.Supported anchors: CollectionUse cases:
  • Collection page: “Shoppers also viewed these products”
  • Discover products related to a collection through browsing patterns
Collection interaction strategies require sufficient historical browsing and interaction data. Data is computed periodically based on configured time windows (7d, 30d, 90d).

Similar products strategies

Use vector similarity to find products that are visually and semantically similar to a seed product. The base Similar Products strategy seeds from the anchor product on the page; the behavior-seeded variants seed from products in the shopper’s own session — recent views, cart, or orders — so recommendations follow real intent instead of the current page alone.

Similar Products

Supported anchors: Product, Collection How it works: The system generates embeddings for each product based on product images, titles, descriptions, and attributes. It then runs the full ranking pipeline — combining vector similarity with behavioral signals — and stores the top results for each product in a precomputed cache. When a customer views a product, the block serves results directly from this cache for fast response times. If no precomputed data exists yet (for example, for a newly added product), the system falls back to real-time vector search automatically. For collection anchors, the system automatically selects a representative product from the collection to use as the similarity source. Precomputed results and freshness:
  • Results are recomputed daily when the existing data is more than three days old or new products have been added since the last run
  • When a product’s embeddings are updated (for example, after editing its title, description, or images), that product’s similar products are recomputed incrementally
  • All filters, facets, pagination, and sort orders continue to work as expected on precomputed results
  • No configuration is required — precomputed caching is enabled automatically for stores with active similar products blocks
Use cases:
  • “Similar Products” on product pages
  • “You May Also Like” recommendations
  • Visual discovery and exploration
  • Collection-based similarity recommendations

Behavior-seeded similarity

Behavior-seeded strategies blend the embeddings of products the shopper has already interacted with into a single seed vector, then run similarity search against your catalog. Products the shopper has already seen, added to cart, or purchased are automatically excluded from the results so they always see something new.
Recommend products that look like items the shopper has viewed recently in the current session, excluding products they’ve already seen.Supported anchors: any surface where session context is available (typically Home, Cart, Not Found, Landing, Other)Use cases:
  • “Because you were browsing…” hero on the home page
  • Recovery rail on cart or 404 pages
Recommend products that look like items currently in the shopper’s cart.Supported anchors: CartUse cases:
  • “You might also like” rail on the cart page
  • Style-matched cross-sell before checkout
Recommend products that look like items the shopper has purchased in past orders.Supported anchors: any surface where session context is availableUse cases:
  • Returning-customer home page rail
  • Style-continuation recommendations after a repeat visit
Recommend products that look like items the shopper just purchased in the current browsing session.Supported anchors: any surface where session context is available (typically post-purchase pages)Use cases:
  • Post-purchase “You may also like” rail
  • Thank-you page cross-sell
Behavior-seeded similarity strategies require the shopper to have relevant session activity (views, cart items, or orders). When the seed is empty or embeddings for the seed products aren’t ready yet, the block defers to its fallback chain.

Manual strategy

Curate products using a collection or hand-picked product IDs, with optional custom sorting. This strategy gives you complete control over which products appear in the block. Supported anchors: Product, Collection, Cart, None The example below shows selecting the manual strategy when you want to hand-pick which products appear in a block. Animated example of selecting the manual strategy for hand-picked block products Configuration:
  • Hand-picked products: Select specific products by ID in the dashboard. The display order matches the order you define. When hand-picked product IDs are configured, they take priority over collection-based selection.
  • Per-anchor product picks: For product-anchored blocks, you can hand-pick different recommendations for specific anchor products. When a customer views a product that has anchor-specific picks configured, those picks are returned instead of the default list. If no anchor-specific picks exist for the current product, the block falls back to the default hand-picked products.
  • Collection anchor blocks: The collection is determined dynamically from the API request’s anchor_id parameter (no collection selection needed in dashboard)
  • None anchor blocks: Select a collection to pull products from in the dashboard
  • Optionally apply a sort order for custom sorting
  • Apply merchandising rules: For collection-sourced blocks, toggle on to inherit the collection’s merchandising rule pins and banners. Off by default.

Apply merchandising rules

By default, manual blocks that pull products from a collection skip the collection’s merchandising rules — you get the raw collection contents in the configured sort order, without the pins, banners, or other rule effects that would normally apply on the collection page. Enable Apply merchandising rules when you want a collection-sourced block to behave like the collection itself:
  • Pinned products surface at the top of the block, matching their pinned positions on the collection page.
  • Banners configured on the collection’s merchandising rule are returned alongside the products.
  • Other rule effects (for example, sell-out deletion) apply to the block’s results.
Leave it off when the block should show the collection’s products in a fixed order — for example, a “New Arrivals” rail that always sorts by date regardless of what’s pinned on the collection page.
This toggle applies only to manual blocks whose products come from a collection. Hand-picked product IDs are unaffected — merchandising rules are never applied to explicitly picked products.

Per-anchor product picks

Per-anchor product picks let you tailor manual block recommendations based on which product a customer is viewing. Instead of showing the same hand-picked products for every anchor, you can define unique product lists for specific anchors. How it works:
  1. You configure a default set of hand-picked products for the block
  2. Optionally, you add per-anchor overrides for specific products
  3. When the block is requested with an anchor_id:
    • If the anchor has specific picks configured, those products are returned
    • Otherwise, the default hand-picked products are returned
This is useful when certain products have natural pairings that differ from your general recommendations. For example, a “Complete the Look” block might show different accessories depending on which clothing item a customer is viewing. Use cases:
  • “Best Sellers” block (collection of top products, sorted by sales)
  • “New Arrivals” block (collection of recent products, sorted by date)
  • “Editor’s Picks” (curated collection with custom order)
  • “Staff Picks” (hand-picked products in a specific order)
  • Seasonal promotions (collection of seasonal products)
  • “Complete the Look” with product-specific accessory pairings
  • Targeted cross-sells that vary by anchor product

Personalized strategies

Personalized strategies resolve per request against the current shopper’s session and identity. They don’t precompute a product-to-product matrix — instead they pull products directly from the shopper’s own browsing, cart, order history, or replenishment cadence. If the shopper has no relevant session activity yet, the block defers to its fallback chain.
Products the shopper has viewed recently in the current session, prioritizing items they revisited more than once.Supported anchors: any surface where session context is availableUse cases:
  • “Pick up where you left off” rail on the home page
  • Return-visit reminder on account or cart pages
Previously purchased products that are due to be repurchased based on typical replenishment cadence.Supported anchors: any surface where session context is availableUse cases:
  • “Time to reorder” rail for consumables and refills
  • Account page nudge for known repeat-purchase items
A blended feed that combines Recently Viewed, Browsing History Related, and Order Related into a single rail, tuned by the shopper’s affinity signals. Use this when you want one general-purpose personalized surface instead of stacking multiple blocks.Supported anchors: any surface where session context is availableUse cases:
  • “For you” home page hero for returning shoppers
  • Single personalized rail on account or landing pages
Personalized strategies require shopper session context. For brand-new visitors with no session activity, the block returns empty and the fallback chain takes over — typically a trending strategy.
Show what’s popular across the store without needing a shopper or anchor product. Trending strategies are ideal for top-of-funnel surfaces like the home page or 404 pages where you have no other context to work with.
Trending and popular products based on overall store activity, sales, and shopper interest.Supported anchors: Product, Collection, Cart, Home, Search, Not Found, Landing, OtherTime windows: 7d, 30dUse cases:
  • “Best sellers” hero on the home page
  • Default rail on search pages with no results
  • Fallback content for 404 pages
Real-time updates on what’s happening in the store — newest products, trending items, and active promotions.Supported anchors: Product, Collection, Cart, Home, Search, Not Found, Landing, OtherTime windows: 1h, 24hUse cases:
  • “Just dropped” or “What’s hot right now” on the home page
  • Live activity rail on landing pages during a launch or sale

Contextual strategies

Use signals from the page itself — the search query, the traffic source, or the cart total — to select products. Contextual strategies are aware of what brought the shopper to the page rather than who the shopper is.
Help shoppers discover relevant products based on what others viewed after searching with the same query.Supported anchors: SearchUse cases:
  • “Shoppers also viewed” rail on search results
  • Recovery rail on zero-result search pages
Recommend products based on what shoppers bought after searching with the same query.Supported anchors: SearchUse cases:
  • “Top picks for this search” rail
  • Conversion-focused recommendations alongside search results
Recommend products tailored to the traffic source, reflecting browsing, carting, and buying patterns from similar channels.Supported anchors: LandingUse cases:
  • Channel-aware hero rail on UTM-tagged landing pages
  • Campaign destinations that adapt to paid vs. organic traffic
Surface products that nudge the cart toward the free-shipping threshold, related to current cart contents and within the remaining spend window.Supported anchors: CartUse cases:
  • “Add to qualify for free shipping” cart rail
  • Threshold-aware upsell when the cart is close to a free-shipping break
Contextual strategies require the relevant page signal — a search query for searched_then_viewed and searched_then_purchased, a landing source for landing_page_picks, or cart contents for free_shipping_picks. When the signal isn’t available on the request, the block defers to its fallback chain.

Strategy availability by anchor type

Not all strategies are available for all anchor types. Use this matrix to plan which strategy to pick for the surface you’re building.