Skip to main content

Voyado Engage

Product data

An article is an individual line-item purchase on a receipt.

Example: A certain hat.

A product is an article plus the other information relevant for this retail context.

Example: That certain hat, in the color red, available at a specific store.

Product metadata is all the other pieces of information connected to a product.

Example: The hat's availability, review score, how many sellers there are, how many variations exist...

By linking the line-items on a contact's receipt with the product data for those articles, you gain the ability to more precisely segment and analyze a contact's shopping behavior. The more data you have about a product, the more you know about the person who bought it.

Enrichment of articles

Articles on receipts don't have any of the useful product data or metadata. This is to save space in the transmission and importing of transactions, but also to allow flexibility in adding product data, a process known as "enrichment". Enrichment is simply linking the articles on a receipt with their product data.

The SKU code is the key to enrichment. Since an SKU exists both for the article on the receipt and in the article register, this allows them to be connected. The SKU is mapped to "ArticleNr" in Engage. Note that a line-item row in Engage always refers to the most detailed version of a specific article.

You can read more about this in the introduction to receipts.

Data fields for articles

An article in Engage includes standard fields and some flexible extra fields configured per client installation. These “spare fields” are of two types:

  • 10 extra string fields (spare1, spare2 ... spare10)

  • 5 extra date/time fields (datespare1, datespare2 ... datespare5)

These fields are used to save product data.

Using product data

There are two ways to leverage product data in Engage:

  • Using already purchased articles to segment and analyze a contact's buying behavior

  • Inserting product information when populating emails (read more about this here).

This section will focus on the first option: using article data for segmentation.

Article data for segmentation

Engage maintains an internal article directory. There are two ways of adding product data to (enriching) these articles --through an XML file import or an external product feed URL.

1) XML file import of articles

The Article XML importer allows you to import an article directory.

For example files and the XSD schema for file import, go to the example files page.

The following fields are available in the <article> node. The * indicates a mandatory field.

Field

Format

Max. characters

Description

*sku

string

255

Article SKU, the most detailed designator for an article. Must be unique. Transactions will be matched on this key.

*number

string

255

Article number / group number, can be shared by color variants of the same product over multiple SKUs

*name

string

255

Article name in human readable form

*itemnumber

string

255

Item number, can be shared by color and size variants of the same product over multiple SKUs

*MainCategory

string

255

 

group

string

255

Main article category name

awardsbonus

boolean

1 or 0

Sets the article qualified for bonus if set to true.

Brand

string

255

 

Color

string

255

 

Size

string

100

 

ProductCategory

string

255

 

SubCategory

string

255

 

AgeGroup

string

255

 

Gender

string

6

Description

string

255

 

Season

string

255

EAN

string

20

GTIN

string

20

Same as EAN, but a more international standard

spare 1-10

string

255

Ten fields (named spare1 - spare10) for additional data

2) Product feed import of articles

Another way to import into the article directory is by fetching a product feed (preferably in a Google format) from an open HTTP endpoint. Note that this feed needs to contain all the products that can be purchased at all locations (e-commerce web sites or local shops) and in a single master language.

It might be wise to let the PIM (Product Information Management) system generate this file rather than the web shop.

Note

When migrating historical transactions, the product feed won’t be able to add metadata, since the feed normally contains current data (e-com does not need “old” data to be sent out to, for example, Google Shopping). Therefore, you might end up missing historical data. In some cases, a separate migration is recommended. Talk to your Engage team about the best approach.