This topic describes mandatory item elements in the RSS product feed, used for importing catalog content from Episerver Commerce to the Episerver personalization engine.
Item element tags
The <item> portions of an RSS feed contain a number of elements that provide descriptive information for each item/product. The following fields are mandatory for the Episerver feed. You may request additional information to fully optimize the product recommendations.
|<title>||The title of the item.
The values for <title> are used as the labels for the links in the recommendation widget. The <title> value should convey enough information for a user to understand what the link refers to. For example:
|<description>||A text description of the item.
The value for the <description> describes the item. It is typically a few sentences in length and ideally should be all text with no HTML. The descriptions should be able to stand-alone and provide enough information so users know what the item is. For example:
|<pubDate>||The publication date of the item.
If your data supports <pubDate> then it needs to be included in the feed as it is valuable information when calculating product recommendations. If your data does not support this, the field must be included but leave the content blank. For example:
|<guid>||A value or string that uniquely identifies the item within the site catalog.
The <guid> (Globally Unique ID of a product) serves as an important connector between your data and the Episerver product recommendations engine. The GUIDs provided in the feed must match those that are being used on the website. There is no established format for what a <guid> value should be, the only requirement being that no two <guid> values within a data set be the same. For example:
|<link>||The URL of the item. Typically the content/product detail page.
The value of the <link> provides the "landing spot" on your site for the links in the Episerver product recommendations. The <link> value should simply be the URL for the Product Detail Page in your website. Avoid adding parameters to the URL. The URL must match the website. For example:
|<p:imageLink>||The link to the image that is required.
The <p:imageLink> element associates the images that you want to display with each item. Avoid adding parameters to the URL. The URL must match the website. For example:
|<p:price>||The product’s price. (This must match the price listed on the site.)
This element describes the retail price or the sale/promotion price of the product.
|<category>||Classification of the item, which is used to group items together. This needs to match the category structure of the website (breadcrumb).
The <category> element defines the type of product and needs to match the category structure of the website. Use a greater-than symbol (>) to separate category levels. If a product belongs to multiple categories, then specify as shown.
|<p:stock>||The number of products available.
The <p:stock> element advises the number of products that are available for that item. If unable to advise, the quantity <p:inStock> can be used.
See optional elements detailed later in this document. For example:
Last updated: Nov 06, 2017