Skip to main content
Each row on the Recommendation Blocks list shows a 7-day inline performance summary. To see a deeper breakdown, including longer timeframes, position-by-position results, and the products driving conversion, open the Performance sheet.

​
Prerequisites

  • Your storefront must forward click, add-to-cart, and purchase events to the Beacon API with the block’s attributionToken from the Blocks API. Without these events, the performance sheet shows empty results.

​
Steps

  1. Go to Recommendation Blocks.
  2. Find the block you want to inspect.
  3. Click the inline performance summary on that row (the chart icon and metrics block) to open the Performance sheet.
  4. Use the date range and compare-to pickers at the top of the sheet to change the timeframe and the comparison period. Use the Revenue picker to switch between Blended and Full credit revenue. See Performance panel.

​
What you can see

The Performance sheet is organized into these sections:
  • KPI cards — Impressions, CTR, add-to-cart rate, purchase rate, revenue, and revenue per impression (RPI). Each card shows the absolute value and the percent change versus the prior period of the same length.
  • Trend — A combined line and bar chart showing impressions, clicks, add-to-carts, and purchases across the selected timeframe.
  • Position — Per-slot performance, so you can tell whether the first products in the carousel are doing the work or whether engagement spreads evenly across positions.
  • Top products — The products with the most impressions, clicks, and revenue while the block was active. Each row shows the product title alongside its individual performance metrics.

​
How clicks, add-to-carts, and purchases are counted

The KPI cards report blended counts: a sum of events tied directly to the block’s attributionToken plus modeled events from the same browsing session. A modeled event counts only when the shopper clicked the same product from this block earlier in the session. Modeled events get less credit the longer after the block was shown they happen, and none after 72 hours. Each modeled event is credited to a single search, collection, or block, so it isn’t counted twice across surfaces. Blended counting keeps your block’s totals accurate even when the attributionToken doesn’t survive the full path to checkout, such as when a shopper opens a product on a page that doesn’t forward the token. See Metrics: Blended attribution for a full breakdown of the attribution categories. The KPI cards in the Performance sheet also surface a deterministic-versus-modeled breakdown so you can see how much of each total is signed by the token directly.

​
Troubleshooting

​
Next steps