Product Feed Custom Columns
In addition to the mandatory and recommended columns, you can add more columns that describe your product. These can later be used for targeting (for example, add "color", and target users who purchased blue items), affinity scores (for example, include color affinity in the affinity recommendation algorithm), or to define merchandising rules in your recommendation widgets (for example, never recommend products of a specific brand).
Supported formats:
Format | Description | Column Name | Example |
---|---|---|---|
Float (up to 1000 characters) | Any custom product attribute with numeric values. For example, "special_price" or "margin". | type:number:<"column_name"> | "type:number:margin":0.15 |
Date (yyyy-mm-ddThh:mm:ss) | Any custom product attribute with date values. For example, "date_added" or "sale_end_date". | type:date:<"column_name"> | "type:date:date_added":"2023-01-12T10:08:11" |
String (up to 1000 characters) | Any custom product attribute with string values. For example, "brand" or "badge title". | <"column_name"> | "brand":"My Cool Brand" |
Guidelines:
- Characters:
- Custom string columns support up to 1,000 characters, with no special characters.
- The character
:
is not allowed, except for typed columns. Using it blocks the feed sync.- Allowed use example:
type:number:custom_price
- Disallowed use example:
my:number
- Allowed use example:
- The character
.
is not allowed, as it can break the RCOM Elasticsearch indexer (learn more).
- Column names:
- Max length is 255 characters.
- Must not be prefaced with
id
.
- Custom number and date columns can't be translated (= used in lng columns).
- Custom number and date columns can't be empty (empty values are assigned the value '0' or the current date, respectively).
- After you add a column, you can't remove it. You can stop using it or return empty values, but the column must be included in any future sync.
- You can create up to 300 columns (including mandatory, custom, and translated columns).
Updated 4 months ago