Skip to main content
Pages are entities that determine what types of product listings should be included in the response for a given page ID, such as recommendations or facetable product grids. They also include rules that merchandisers can configure, such as pinned products, default sorting, and other merchandising controls. It is possible to work with pages in two ways:
  • You can import a collection of pages using the import API (see the guide on how to import and export pages) or set them up in the app.
  • Or you can supply a configuration in the POST body of each landing page query.
We recommend importing pages, as that gives you access to more customization tools and options, such as the Navigation editor, improved facet handling, and Boost by page.
The page identifier, page ID or page reference, is used to identify an existing page configuration. An existing page configuration created via the Admin API or Elevate Application takes precedence over configuration supplied in the POST request body.

Product rules

Product rules is a configuration that is equal to the visual way of defining a product selection in the Elevate app. The product rules are a form of logical expressions that are used to restrict the products in a response. Rules can go from easy, such as to only include a single product using its product key or products of a specific brand, to more complex with multiple attributes for the product selection.
Product filters and Product rules cannot be present in the same page configuration.

Expressions

An expression may consist of multiple rules where each rule must have at least one restriction. A restriction must include a condition, which in turn consists of an attribute that has a value that is either a list of strings, an interval, an interval with a unit, or a specified newness . The structure of an expression can be visualized as follows:

Rule

A rule must have at least one restriction. Rules are separated with a whitespace, that is, a space, a tab, or a newline. If more than one rule is used, the rules are to be considered as using the logical OR operator. When product keys are specified in a rule (equal to Handpicked in the apps), this rule must be the first rule and must contain a set of product keys (one or more) as its only condition. Example:
include products that are *striped* OR have the product key *1234*

Restriction

A restriction is either an include, incl, or an exclude, excl, followed by a condition. If more than one restriction is present in a rule, the restrictions can be considered as using the logical AND operator. Example:
include products that are both *striped* AND NOT *white*

Condition

A condition must consist of an attribute followed by a value that is either a list of strings, an interval, an interval with a unit, or a specified newness. If more than one value is present within a list of strings, consider the values to be using the logical OR operator. Example:
include products that are either *red* OR *green*

Attribute

Most built-in or custom attributes are allowed in conditions. Here is a list of common ones to use:

Type definitions

Products and variants

Criteria are evaluated at the product level. This means:
  • If a variant is included in the selection, the entire product it belongs to will be included.
  • If a product has multiple variants, and at least one variant matches the selection criteria, the product will be included.
To exclude a product, none of its variants can match the selection criteria. Even if one variant of a product is explicitly excluded, the product will still be included as long as at least one other variant is included. A product is excluded when all of its variants are excluded.

Examples

Handpick products p1234 and p5678.

Product filters

The Product filters configuration has been superseded by the Product rules configuration. It is recommended to use the Product rules configuration for new Voyado Elevate integrations.
Product filters can be applied to both primary listings and recommendation listings and are included in the request body for the target listing. Applying a filter will restrict the set of returned products to be included in the actual result set and can be either numeric or value filters.Listing multiple attributes to filter on will restrict the products to all conditions (logical AND). When listing values within one attribute, products with any of the listed properties apply (logical OR).
Product filters and Product rules cannot be present in the same page configuration.
The following illustrates an example of applying a filter for a Calvin Klein outlet of products from old seasons.
  • All products will be of the brand Calvin Klein.
  • All products will at least be 1 percent discounted.
  • All products belong to either the Winter or Spring season.

Numeric product filters

Numeric filters can be provided as a range, single values, or as lists of values. All ranges are inclusive and may be provided with a one-sided limitation, where min defaults to 0 and max defaults to the maximum eligible value.

Supported numeric filter attributes

Value product filters

Value filters can be provided as single values or as a list of values.

Supported value filter attributes

Primary list

Some page types include primary listings such as search and category pages. Primary lists can be configured with product rules.

Recommendation lists

Most page types support recommendation lists. To include recommendation lists in a page response, the request body must include the recommendation configuration.

Algorithms

All recommendation algorithms will utilize provided product rules, productRules, or product filters, productFilter (deprecated).
The recommendation algorithms ALTERNATIVES and UPSELL are primarily used on product pages. They are best utilized without product rules/filters. Too strict product rules/filters may prevent actual visitor behavior from being properly reflected and thus reduce sales.

Parameters

Content filters

Content filters can be applied to most content listings and are included in the request body for the target listing. Applying a filter will restrict the set of returned content and can only be string value filters, for example not numeric. Listing multiple attributes to filter on will restrict the content to all conditions (logical AND). When listing values within one attribute, content with any of the listed properties apply (logical OR). The following illustrates an example of applying a filter for content by the author Pelle containing both articles and size guides.
  • All content will be from the author Pelle.
  • All products will be of either the article or size-guide type.

Value content filters

Value filters can be provided as single values or as a list of values.

Supported value filter attributes

Content lists

Search page, autocomplete, and landing page support content lists. To include content lists in a page response, the request body must include a content list configuration.

Algorithms (Content)

Last modified on September 11, 2026