Inputs

The Inputs section changes dynamically based on the recipe you selected. Different recipes use different input layouts. The sections below describe the most common patterns you may see.

Event-based inputs

In recipes driven by user activity (such as views, purchases, or add-to-cart events), the Inputs section displays an event timeline with the following fields.

Field Description
Event Name The event to use as input. For example, purchase, add_to_cart, or view.
From Past / To Past Defines the time window for the event. For example, From Past: 7 and To Past: 0 with Time Unit: Days looks at events from the last 7 days. The system displays a computed date range (for example, From 02/03/26 3:32 AM To 02/10/26 3:32 AM) so you can verify the window is correct.
Time Unit The unit for the time window: Minutes, Hours, Days, Weeks, or Months. Use Minutes or Hours for real-time or near real-time recommendation scenarios.
Item The item reference from the event. Select Item in Event to use the actual item, or Parent Item to use the parent product. To consider both, add a separate event row for each. For more on parent items, see Recommendations based on parent product.
Order By

Controls how items from the event timeline are ordered:

  • Most recent (default) β€” Items from the most recent events appear first.
  • Most frequent β€” Items that appear most frequently across events are prioritized. Use this when you want to surface items a user has interacted with repeatedly rather than most recently.

Click + Event to add additional event rows. To remove an event row, click the trash icon (πŸ—‘) next to it.

Some event-based recipes also include a Form input text field (at the top of the section) and a Form checkbox (at the bottom). The Form input defines the variable name for form data passed into the block. When the Form checkbox is checked, the block accepts input values from that form data. These are relevant when recommendations are triggered by form submissions or API requests.

Sample-Event-Block.png

Attribute-based inputs

In recipes that match items to a specific user or catalog attribute, the Inputs section displays an attribute selector. The field name varies by recipe. Some recipes also include a ranking selector to control how matched items are sorted.

Attribute-based inputs showing a single attribute selector.

Item list inputs

In recipes for manually curated recommendations, the Inputs section displays a List of Items separated by a delimiter text field where you enter item identifiers, and a Delimiter String field to define the separator (for example, a comma).

Item list inputs showing list of items and delimiter fields.

Β  Recipe-specific fields

Some recipes may include additional fields not described above. Configure the inputs in your block using the same principles; the field labels and inline descriptions in the UI indicate what each control does.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.