In order for your Listrak solutions to function, you need to provide a basic set of data points, however, you may find that additional data points can enhance your solutions. In addition, these added data points can help achieve your strategic goals.
Outlined below are the required and recommended data points for your product data. In addition, you'll learn some use cases for the product data and how it can be used to support functionality at Listrak.
Required Data Fields
The table below displays the data points that are required to provide an accurate, clean, and concise product catalog. The fields are used in a variety of ways throughout Listrak, including in Product Browse Abandonment Triggered Campaigns and in email filtering.
💡 The value of brand may be left blank if you only sell your house products, or you can fill in your brand for all products. This should be determined in consultation with your Implementation Team.
⚠️ These data points will be used to power many different triggered campaigns as well as segmentation and additional features at Listrak. If this data is not provided some features of Listrak may not function as intended.
Header | Data Type* * see below | Description | Length |
SKU | Alphanumeric | The unique identifier of a product. | 100 |
Title | Alphanumeric | The name of the product. | 500 |
Image URL | Alphanumeric | The location of the product's image. | 500 |
Link URL | Alphanumeric | The link to the product webpage. | 500 |
Description | Alphanumeric | A concise explanation of the product. |
|
Price | Decimal | How much the product costs.
*Use the data transform tool in the Data File Setup to remove additional formatting, such as dollar signs |
|
Brand | Alphanumeric | The brand of the product. | 50 |
Category | Alphanumeric | The top-level grouping of the product, such as department. | 50 |
Subcategory | Alphanumeric | The second-level grouping of a product. | 50 |
On Sale | Boolean | A value that specifies explicitly if a product is on sale. |
|
QOH | Integer | The number of products available for purchase. |
|
In Stock | Boolean | In value that explicitly notes if a product currently is in stock. |
|
Master SKU | Alphanumeric | A unique identifier for group of products. SKU further breaks down this grouping by values such as size, color, or gender. |
|
Discontinued | Boolean | An explicit indicator that a product is no longer available for purchase. |
|
Data Types Accepted in Listrak
Alphanumeric: consists of both letters and numbers
Decimal: consists of numbers with a fractional part separated from the integer with a decimal separator (e.g. 11.25)
Boolean: consists of 0, False, N, No, or 1, True, Y, Yes
Integer: consists of whole numbers (no fractions or decimals)
Recommended Data Fields for Optimal Performance
The table below outlines the additional data available to import about your products. This additional data improves the functionality of your Listrak campaigns. It is strongly recommended to provide as much of these recommended data fields as possible to provide flexibility when updating your Listrak functionality.
Header | Data Type | Description | Length |
Sale Start Date | Date | The date and time a product goes on sale. |
|
Sale End Date | Date | The date and time a product is no longer on sale. |
|
Is Clearance | Boolean | An indicator that a product is being discontinued. |
|
Is Outlet | Boolean | Ain indicator that the product is in a specific section of your site. |
|
Review Product ID | Alphanumeric | A value that matches the product to the ID of a review if you have a product review in place. | 100 |
Review URL | Alphanumeric | The unique URL that directs to a product's review page. | 500 |
Is Purchasable | Boolean | An indicator that the item is currently available on the site. |
|
Size | Alphanumeric | The size of the specific product. E.g. Lg or 7.5 | 100 |
Color | Alphanumeric | The color, print, or pattern of the specific product. E.g. Green, Striped | 100 |
Style | Alphanumeric | The style, cut, or other detail about the specific product. E.g. Skinny, Formal | 100 |
Gender | Alphanumeric | The value that represents the gender of the specific product. E.g. W, Unisex, Toddler | 100 |
MSRP | Decimal | Manufactures Suggested Retail Price is the price the manufacture recommends for the product. |
|
Meta (1-5) | Alphanumeric | Five different customizable fields that can store additional details about your products to support your goals. E.g. Tertiary Category, Make, Fabric Care | 500 |
Sale Price | Decimal | The reduced price charged when an item is on sale. |
|
Unit Cost | Decimal | The price of producing a single product. |
|
Is Viewable | Boolean | An indicator that can be used to identify products that should be used in Listrak solutions. |
|
Related Products | Alphanumeric | A list of products that complement the specific product, such as additional accessories or complete an outfit. |
|
How can the Data be Used?
Product data is used in many different ways throughout the Listrak Platform. Three of the most common ways your product data will impact your strategies are:
Triggered Campaigns
Broadcast Message Creation and Filtering
Product Recommendations
Triggered Campaigns and Product Data
Triggered Campaigns built in both Conductor and Journey Hub can use the data about products to determine which contacts should or should not receive messages and personalize the email content.
💡 A consistent naming and categorization of your products is critical to be able to filter out products you do not want to appear in your triggered campaigns.
Some common uses cases for these filters include:
Send messages with different creative aspects based on the gender of products purchased.
Send messages with different promotional offers based on whether coupons are accepted for a category or subcategory.
Stop contacts from receive a message is a product is not in stock.
Broadcast Message Filtering
Broadcast messages is provide the broadest opportunity to utilize product data because every email features different content that can be tailored to groups of contacts.
💡 Broadcast message filtering will identify a contact who has (or has not) purchased a product with specific characteristics. When considering update to your data think about how you group products to feature in emails to help target contacts who purchased them.
Send a message about uncommon sizes based in items contacts have previously purchased.
Create product blocks in Composer emails to easily pull in the details of your products.
Product Recommendations
Product Recommendations allows you to add dynamic products to emails based on a contact's activity on your site. The information gathered about the products a contact is browsing, abandoning, or purchasing can influence the strategy for the products that are show or enhance the product's appearance.
💡 Product data can filter the products that appear in the email, e.g. showing products in a specific color or category.
💡 The data can also be used to select what elements are displayed in an email, as seen below.
Display a product's sale price when an item is on sale
Display additional data from recommended fields (e.g. Color, Style) to provide additional details to help contacts make a decision.
Add a product's rating if integrated with one of Listrak's review providers