skip to Main Content

Introduction

One of the basic data tables, Persoo needs to know to be able to provide product related features, are products. Regular product imports provide Persoo system with data like product names, prices, image links etc. These data are used by recommendation algorithms, decisions, for user segmentation and also in the Offers to display recommended products on the web site.

Generally, you can import any data table you need – products, categories, brands, articles, stores, pages,…

Here we look at the concept, which is the same for all data tables. But always, you can imagine data table items as products. See

Important note: if you changed the product import, that would require the new/updated product data, make sure to publish the product import first and run it. Otherwise you might publish some algorithm and offer changes that will not have available new/updated product data.

Data import

Source file url

Provide URL with imput data … typically URL of your Google/Facebook/Heureka product feed. See examples of product feeds.

More over you can use Google Spreadsheet tables, which can be downloaded in CSV format. See how to use Google Spread Sheet as data import source.

File formats

Supported file formats are XML, CSV, JSON in encoding UTF-8.
For some formats, you must specify also item entity name, i.e. <item> for XML or delimeter for CSV.

Data table language

Each data table may contain text data. To provide a fulltext search engine, which can also use language tools, you need to specify the language of the table.

Product fields

There are

  • Standartized product fields for tables products, categories, queries … where some fields ahs special meaning and functionality (but not all of them are required).
  • Custom fields related to your product features or your internal tags (to be used in filters or internal to influence recommendation algorithms,…

All tables requires ID. Also there are standardized fields to be able to provide nice “titles”, links, images in targeting and in catalogue in Persoo administration.

  • id (with the exception of table products, where we have itemID and itemGroupID instead)
  • title
  • description
  • link
  • imageLink

Imported fields

From all fields cotained in the source, select those, you need to import and use. For each such a field, you must specify its data type, i.e. number, string, … See field data types.

Other import related notes

Recommendation: export all product fields you have in your product database. It’s easier to export all columns you have in your product DB at once, than to ask your developer to add fields one by one and wait for it.

You can even use your orignal field/column names. Persoo has rich options, how to rename, modify product fields,…(javascript preprocessing function). So you cannot make mistake if you export all raw product data with original field names.

Passing on multiple values of the same field.

In the JSON format, pass an array of items (e.g. colors: [‘white’,’red’]). In an XML format, pass the same field multiple times. For example <colors><color>white</color><color>red</color></colors>.
In CSV import, use comma, and then process it into an array in Import processing.

Important notes

Pay attention to the specifications of the feed fields, as any deviation will complicate the setup.
Make sure, that the values are identical to the values given by the site’s data layer, so they can be easily paired in our system.

We recommend consulting feed’s fields also with your personalization consultant and marketing representative, as these data directly impact what scenarios can be implemented.

Back To Top
×Close search
Search