Skip to main content

Voyado Engage

Product data

It’s essential to understand a customer’s purchases, in order to segment and analyze their behavior. This is where Product metadata comes in. The more data you have on a product, the more you know about your customer.

There are two different ways to use product data in Voyado:

  • Article data for purchases, i.e. be able to segment and analyze consumer behavior in regards to the products they have purchased.

  • Product data for email content population, i.e. adding product information by simply entering the article number. For more information, click here.

This section will focus on article data for purchases.

Meaning of “Articles”

Every article in Voyado holds its own data. Some standard fields, and some extra fields configured for every Client installation. These are called “spare fields”, and could be:

  • 10 extra string fields (spare1-10)

The line-item row in Voyado is always referring to the most detailed version of a specific article. Often identified via the SKU (in Voyado mapped with “ArticleNr”).

Article data for segmentation

Voyado stores an internal article directory. There are two different ways of adding product data to it:

  • Import the data via a XML file

  • Import the data via an external product feed url

Article import (via custom XML file)

The XML Article importer makes it possible to import an article directory, to minimize the size of the transaction import and its metadata.

Expected format:

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 more international standard

spare 1-10

string

255

Ten fields (named spare1 - spare10) for additional data

Article import via product feed

Another possibility of importing into the article directory is by fetching a product feed (preferably in a Google format) found at an open HTTP endpoint. Note that this feed needs to contain all the products that can be purchased at all locations (country e-commerce web sites or local shops) in ONE master language. It might be wise to let the PIM 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 (eCom does not need “old” data to be sent out to e.g. Google Shopping) Therefore, you might end up missing historical data. In some cases, a separate migration is recommended. Talk to your Voyado team about the best approach.