the rec profiles you are requesting information from, along with profile specific parameters. This is required for POST requests

🔴 Required for Personalization when present IDs or SKUs of the products being viewed. This parameter is required only for recommendations profiles that use cross-sell or similar recommendations types, and is recommended for all requests made on Product Detail Pages. This parameter will often just be a single value on a PDP but could be multiple on something like a view wishlist page or a page for a bundle of products.

IDs or SKUs you wish to block from being returned by the API in this call. This is useful if you have other products that are being displayed on the page that you don't want returned by the recs API, potentially if you have curated products on the page.

🔴 Required for Personalization when present IDs or SKUs that are in the current shopper's cart. This is required to curate recommended products as the shopper navigates the site. Required for cart cross-sell.

🔴 Required for Personalization when present IDs or SKUs that the shopper has recently viewed, with the most recently viewed product SKU listed first in the comma-seperated list. This parameter is required to curate recommended products as the shopper navigates the site.

Filters all the recommendations (does not apply to last viewed profiles or static custom profiles). If there are any profile-specific filters, these filters will be added to them, not overwritten. A field must have the Recs Filter column selected in the Field Settings page in the AMC in order to be used. Because the data science only creates so many recommendations for each product, there is a high chance of filtering out all of the recommendations; as such, this is best used when showing nothing is better than showing the wrong product.