Data Feeds

This post is also available in:

In order to run properly, Samba requires integration with the following data feeds:

If you created your e-shop via one of the supported e-commerce platforms, you don’t have to bother with data integration. Just follow the step-by-step guide here. If you use a different, unsupported platform, do not despair, we’re working on the integration of other popular platforms. Until then, please, follow the step-by-step guide, which you can find below.

Links (publicly accessible, or containing access data in the format https: // username: password@youreshop.com/feedname.xml) to these feeds can be provided in the section Settings – Integrations – Data integration – Connection settings in Samba.

Basic auth security with HTTPS

Access credentials filled in using basic authentication (i.e. in the format https://username:password@youreshop.com/feed.xml) are fully secured during transmission thanks to the HTTPS protocol, so there is no need to worry about interception by a third party. The HTTP request is sent to the IP address corresponding to the domain and contains only the part after the first slash after the domain, so the processed URL in the request does not contain basic auth data. This is because the basic auth data is transmitted at the request header level. However, without HTTPS certificate, the entire request including the headers travels unencrypted, so it is strongly recommended to have the domain secured with this protocol.

To save the changes, press Save configuration.

Once you have filled in all the data, press Refresh. Samba will download the feeds immediately according to your settings. You’ll usually see the output from our validation in minutes, so you can fix the errors.

Regular updates:

Data feeds are updated once a day by default.
Data feeds are always updated as a whole. Therefore, if the update fails for any reason, even partially processed data from one feed is not processed.
Samba automatically attempts to update the data again at progressively longer intervals until the time of the next scheduled update.
If you don’t want to use one of the feeds and need to update your data, use the so-called Empty Feeds.

Properties of the data feeds

XML format
UTF-8LE coding
do NOT use unicode control characters (except the CR and LF characters)

Special characters

Special characters &, >, <, \, ", ' must be escaped according to the official XML format specification or the so-called CDATA section must be used. I.e. for example instead of

<VALUE>A&B <> C&D</Value>

use escaping

<VALUE>A&B <> C&D</Value>

or use CDATA section as follows

<VALUE><![CDATA[A&B <> C&D]]></Value>

It is important to maintain referential integrity between feeds, i.e. ID consistency across feeds. Make sure the product ID is the same in the product and order feed. The same goes for the customer ID in the orders and customers feed.

The most common mistakes

Take a look at the most common problems that you can encounter while integration your shop and Samba. The link to the article is here.

Products feed

This feed contains the database of all your products, that you offer on your e-shop. For the best results, we recommend including as many optional parameters as possible. Thanks to this data feed, Samba is able to recognize the parameters of the products (type, brand, category, price category, colour, size,….) and then offer this product to the right customer. Samba works with the stock information and special offers as well, so it doesn’t offer a product, that you don’t have in stock and on the other hand, offers a product, that is on sale, and more.

Supported parameters

Name	Type	Required	Description
PRODUCT_ID	String	yes	product ID
TITLE	String	yes	product name
PRICE	Float, >=0	yes	selling price (tax included, without shipping and handling)
URL	String	yes	product URL
IMAGE	String	no	product picture URL (approx 300x300 px)
DESCRIPTION	String	no	detail description of the product (without HTML tags)
BRAND	String	no	product brand
STOCK	Integer, >=0, default:1	no	number of pieces in stock
PRICE_BEFORE_DISCOUNT	Float, >0, PRICE_BEFORE_DISCOUNT > PRICE	no	price before discount (tax included)
PRICE_BUY	Float, >0	no	cost price of the product (for calculating profit margin)
PRICES	[NAME, VALUE]	no	special prices for different customer groups, see PRICE_CATEGORY in the customer feed
CATEGORYTEXT	String	no	categories that include the product, seperated by "\|"
PRODUCT_LINE	String	no	product line
VARIANT	Products list	no	see product variants below
SHOW	Boolean, default: TRUE	no	can we show this product?
PARAMETER	[NAME, VALUE]	no	Other parameters (NAME does not have to be unique, please see example below)

In case of multiple occurrences of a parameter with the same NAME, all relevant VALUEs are processed. As part of the filtering, it is possible to search among all values.

SHOW a STOCK parameter

Samba offers only the products, that you have in stock, with PRICE>0 and existing URL and IMAGE. If you want to prohibit some products from the offering, set the SHOW parameter to FALSE.

Product variants

Each product can have an unlimited number of different variants, i.e. the same products with some different parameters, e.g. colour or size. These variants are grouped into one parent product, the so-called master product. This designation ensures that different variants of the same product,, are not recommended to the customer in the same advertising message.

A product listed as a master is typically one of the variants, or it can be a directory of variants (depending on the implementation of your e-shop)
Selection criterion
- Master product must meet:
  - PRICE > 0
  - STOCK > 0
  - there is an IMAGE
  - there is a URL
- A product with a PRODUCT_ID that is not nested in the VARIANT tag is automatically processed as a master product.
  - However, if such a product does not meet the above criteria, the first variant that meets the criteria is automatically selected as the master product.
  - If no variant meets the criteria, the originally specified product, i.e. the product not embedded in the VARIANT tag, is selected as the master product.
If an attribute is missing from a variant, the one specified in the master product is automatically used. This also applies to the PRICES attribute, see below.

Rounding of prices

The newsletter is filled with the prices listed in the product feed. However, if you have some prices set to values like 419,72 USD, you can tell Samba to round such price to the number of decimal places you want.

This setting can be found in Settings – Integration – Data Integration – Connection Settings, where you can choose if and to how many decimal places you want to round prices

For example, using “Number of decimal places: 0” would round prices to whole numbers. The price of 419,72 USD would therefore be rounded to 420 USD.

Customer groups with different prices

Using the PRICES attribute, you can define different selling prices and original prices before discount for different customers. This can be useful, for example, if you use different discount programs or work with “VIP” and “guest” customers, etc.

Working principle:

PRICE_CATEGORY only applies to personalized products in the emailing. Currently, it does not apply to personalization in web recommendations – only the default price (the same for all clients) is returned here.
For groups you can redefine:
- PRICE – selling price
- PRICE_BEFORE_DISCOUNT – price before discount
For every customer for whom a match is found between PRICE_CATEGORY in the customer feed and PRICES>CATEGORY>NAME in the product feed, this special group price is automatically displayed in the product recommendation.
If no PRICE_CATEGORY is listed for a customer, or one that is not listed for the currently recommended product, the default default price for that product is used for that customer.
A maximum of 1000 groups with different prices across the entire feed are allowed.
- Products exceeding this limit will not be processed.
- Customers exceeding this limit are processed, but special group prices will not be applied.

Example of the products feed

<?xml version="1.0" encoding="utf-8"?>
<PRODUCTS>
     <PRODUCT>
          <PRODUCT_ID>D45S8741545SD</PRODUCT_ID>
          <BRAND>Product Brand</BRAND>
          <TITLE>Product name</TITLE>
          <DESCRIPTION>Detailed description of this product</DESCRIPTION>
          <PRICE>40.1</PRICE>
          <PRICE_BEFORE_DISCOUNT>42.1</PRICE_BEFORE_DISCOUNT>
          <STOCK>60</STOCK>
          <URL>http://www.myeshop.com/path/to/the/product</URL>
          <IMAGE>http://www.myeshop.com/path/to/the/image.jpg</IMAGE>
          <CATEGORYTEXT>Clothes | Men | Trousers</CATEGORYTEXT>
          <PRICES>
               <CATEGORY>
                    <NAME>guest</NAME>
                    <PRICE>41</PRICE>
                    <PRICE_BEFORE_DISCOUNT>42.1</PRICE_BEFORE_DISCOUNT>
               </CATEGORY>
               <CATEGORY>
                    <NAME>vip</NAME>
                    <PRICE>40</PRICE>
                    <PRICE_BEFORE_DISCOUNT>45.1</PRICE_BEFORE_DISCOUNT>
               </CATEGORY>
          </PRICES>
          <PARAMETERS>
               <PARAMETER>
                    <NAME>Color</NAME>
                    <VALUE>White</VALUE>
               </PARAMETER>
          </PARAMETERS>
          <VARIANT>
               <PRODUCT_ID>D45S8741545SD-XXL</PRODUCT_ID>
               <TITLE>Product name XXL</TITLE>
               <DESCRIPTION>Detailed description of this product XXL</DESCRIPTION>
               <PARAMETERS>
                    <PARAMETER>
                         <NAME>Size</NAME>
                         <VALUE>XXL</VALUE>
                    </PARAMETER>
                    <PARAMETER>
                         <NAME>EAN</NAME>
                         <VALUE>467891186861118</VALUE>
                    </PARAMETER>
               </PARAMETERS>
               <PRICE>40.1</PRICE>
               <PRICES>
                    <CATEGORY>
                         <NAME>guest</NAME>
                         <PRICE>41</PRICE>
                         <PRICE_BEFORE_DISCOUNT>42.1</PRICE_BEFORE_DISCOUNT>
                    </CATEGORY>
                    <CATEGORY>
                         <NAME>vip</NAME>
                         <PRICE>40</PRICE>
                         <PRICE_BEFORE_DISCOUNT>45.1</PRICE_BEFORE_DISCOUNT>
                    </CATEGORY>
               </PRICES>
               <STOCK>10</STOCK>
               <IMAGE>http://www.myeshop.com/path/to/the/imageXXL.jpg</IMAGE>
               <URL>http://www.myeshop.com/path/to/the/product?variant=xxl</URL>
          </VARIANT>
          <VARIANT>
               <PRODUCT_ID>D45S8741545SD-L</PRODUCT_ID>
               <TITLE>Product name L</TITLE>
               <DESCRIPTION>Detailed description of this product L</DESCRIPTION>
               <PARAMETERS>
                    <PARAMETER>
                         <NAME>Size</NAME>
                         <VALUE>L</VALUE>
                    </PARAMETER>
                    <PARAMETER>
                         <NAME>EAN</NAME>
                         <VALUE>467891186861118</VALUE>
                    </PARAMETER>
               </PARAMETERS>
               <PRICE>40.1</PRICE>
               <PRICES>
                    <CATEGORY>
                         <NAME>guest</NAME>
                         <PRICE>41</PRICE>
                         <PRICE_BEFORE_DISCOUNT>42.1</PRICE_BEFORE_DISCOUNT>
                    </CATEGORY>
                    <CATEGORY>
                         <NAME>vip</NAME>
                         <PRICE>40</PRICE>
                         <PRICE_BEFORE_DISCOUNT>45.1</PRICE_BEFORE_DISCOUNT>
                    </CATEGORY>
               </PRICES>
               <STOCK>10</STOCK>
               <IMAGE>http://www.myeshop.com/path/to/the/imageL.jpg</IMAGE>
               <URL>http://www.myeshop.com/path/to/the/product?variant=l</URL>
          </VARIANT>
     </PRODUCT>
</PRODUCTS>

Customers feed

Customers feed should contain the whole database of your customers. Samba can adjust its personalization based on other metaparameters, such as gender or the date of registration.

Samba is able to distinguish 3 levels of newsletter subscription.

every day
special occasions
never

Samba targets only those customers who really want to receive newsletters.

For information on how the number of customers affects your payment plan, see this article.

Supported parameters

Name	Type	Required	Description
CUSTOMER_ID	String	yes	Customer ID
NEWSLETTER_FREQUENCY	Enum: every day \| special occasions \| never	yes	Subscription frequency (never = unsubscribed)
NLF_TIME	Datetime (as string)	no	Datetime in the YYYY-MM-DDThh:mm:ss.sTZD format (more info) Time of the customer's subscription change
EMAIL	String	no	A valid email address
REGISTRATION	Date & time (as a String)	no	Date and time of registration in the following format: YYYY-MM-DDThh:mm:ss.sTZD (more info), default: "1970-01-01"
FIRST_NAME	String	no	First name
LAST_NAME	String	no	Last name
ZIP_CODE	String	no	ZIP code
PHONE	String	no	Phone number with the Incl. plus sign and country code (e.g. "+420xxxxxxxxx" for Czech Republic, or +11234567890 for USA)
SMS_FREQUENCY	Enum: every day \| special occasions \| never	no	SMS subscription frequency (never = unsubscribed), default: "never"
DATA_PERMISSION	Enum: full \| do_not_personalize \| anonymized_only	no	default: "full"
PRICE_CATEGORY	String	no	customer group for determining special product prices - see PRICES in products feed
PARAMETERS	[NAME, VALUE]	no	Other parameters (NAME does not have to be unique, please see example below)

In case of multiple occurrence of a parameter with the same NAME, all relevant VALUEs are processed. As part of the filtering, it is possible to search among all values. When used in a template by inserting a dynamic variable, one of the values is used randomly.

<NLF_TIME> attribute

This attribute gives Samba the information about the exact time, when customer changed their subscription status. If the unsubscribed customer resubscribes, Samba will know, which action should be prioritized. If the attribute is not present, information from Samba is prioritized – unsubscribing via the footer link, and/or through the Database Administration.

<DATA_PERMISSION> attribute

Customers provided with the value DATA_PERMISSION = anonymized_only will not be targeted by any channel. The system only uses their anonymized data (behavior patterns) in order to train our algorithms. You can find more information here.

Example of customers feed

<?xml version="1.0" encoding="utf-8"?>
<CUSTOMERS>
     <CUSTOMER>
          <CUSTOMER_ID>D45S8741545SD</CUSTOMER_ID>
          <EMAIL>jan.novak@email.cz</EMAIL>
          <REGISTRATION>2014-12-31T03:53:43.962Z</REGISTRATION>
          <FIRST_NAME>Jan</FIRST_NAME>
          <LAST_NAME>Novák</LAST_NAME>
          <NEWSLETTER_FREQUENCY>every day</NEWSLETTER_FREQUENCY>
          <NLF_TIME>2014-12-31T03:56:43.962Z</NLF_TIME>
          <ZIP_CODE>15000</ZIP_CODE>
          <PRICE_CATEGORY>vip</PRICE_CATEGORY>
          <PARAMETERS>
               <PARAMETER>
                    <NAME>Bonus points</NAME>
                    <VALUE>100</VALUE>
               </PARAMETER>
               <PARAMETER>
                    <NAME>Gender</NAME>
                    <VALUE>male</VALUE>
               </PARAMETER>
          </PARAMETERS>
     </CUSTOMER>
</CUSTOMERS>

Incremental customers feed

Samba supports the so-called incremental data feed, which means that this feed contains only those customers that have been created or changed recently. This reduces the load on the servers, where you only need to generate the complete database of customers for the initial update and a small increment every next day.

Procedure

Initial import of history
1. Set the customers feed to the Complete type.
2. Enter the URL of the complete feed.
3. Perform a data update in Samba.
Incremental processing
1. Set the customers feed to the Incremental type.
2. Insert the URL of the incremental feed.
3. Perform a data update in Samba.

The way the whole process works is that once you switch the type to Incremental, Samba automatically maintains the customers history collected so far and aggregates each new increment into this history using the upsert method on CUSTOMER_ID. This means that

a new CUSTOMER_ID appears in the increment – the record is processed and added to the accumulated database in Samba
a previously processed CUSTOMER_ID appears in the increment – the existing customer record is discarded and only the parameters (and items) specified in the increment are processed for the customer

Until you switch the setting back to the Complete type, Samba keeps this accumulated history in its database.

Incremental type

Samba distinguishes the following types of increments based on how the URL is dynamized:

Static URL
- Use when you always generate on one specific and unchanging URL all customers that have changed during a selected period (the length of the period is up to you, typically 7 days).
- E.g. https://samba.ai/export/customers/customers_increment.xml
Specific date
- Use when you periodically generate a new file for a specific time period – for example, you generate a new daily increment every day.
- E.g. https://samba.ai/export/customers/customers_increment_{date}.xml
Date From – To
- Use when you have a service on your side ready to return order exports by from/to attributes.
- Samba automatically selects from as the date of the last successful run, to is selected as “today”. This ensures the next run to reload boundary data that may have been incomplete at the time of processing.
- E.g. https://samba.ai/export/customers/customers_increment_{from}_{to}.xml

Using the “Latest increment available X days ago” option, you can set Samba to e.g. download an increment with a 1-day delay (e.g. on March 17th Samba will download at most an increment with a date of March 16th and not a newer one). This can prevent the entire data update from failing due to data unavailability on your side.

Logic of increment

It is recommended to set the logic so that all customers that have undergone a change during the period appear in the increment. If you set the logic only on e.g. the date of customer’s registration, which is static, the updated customer data will be missing in Samba.

Orders feed

Orders feed should ideally contain history of your orders, that happened on your eshop (we recommend the history to be at least 2 years old, but whole history is preferred or you can also use increments, as explained below). Samba uses this feed to analyse purchase patterns of your customers, which is then being used to personalise. All products in this data feed must be present in the product feed, or they will be marked as “Invalid orders” and ignored by the system.

If you don’t fill in the price of the product in the order, the price of the product (from the product feed) is used instead.

Samba currently supports 3 order states:

finished – finished order, customer has paid or received the goods. This is the only state Samba is actually working with.
created – order has been created and is waiting for finishing (payment, delivery, etc.).
canceled – cancelled or deleted order (by the customer or the eshop).

If you do not fill the order state, Samba will see the order as finished. If the order is in finished state and the attribute FINISHED_ON is not present, the date value in CREATED_ON element is assumed as the date/time of finishing the order.

If you allow customers to create orders without registration, use the EMAIL element instead of CUSTOMER_ID and, if you can, PHONE and ZIP_CODE as well. Samba will create virtual customers, which you can then use for targeting purposes during campaign creation.

In detail: If an unknown CUSTOMER_ID is specified (or is not specified at all) in the specific order and there is a customer (in customer feed) with the same EMAIL as used in this order, the order is then automatically assigned to the customer based on the EMAIL element. However, if there is no such EMAIL in the customer feed, then the value in EMAIL will be temporarily used as a new CUSTOMER_ID so that the order can be processed. Orders without valid EMAIL and CUSTOMER_ID will not be processed at all.

Based on your customer terms and conditions you can select the following option in the Connection settings for these customers:

Do I have the rights to subscribe unregistered customers who made an order?

GDPR states that you do have rights to do this, but you will have to make sure that you are eligible to do so (this is called “Legitimate Interest“). Also, be sure to have properly working “Unsubscribe” link in the footer of your newsletter.

Supported parameters

Name	Type	Required	Description
ORDER_ID	String	yes	Order ID
CUSTOMER_ID	String	no	Customer ID
CREATED_ON	Date & time (as a String)	yes	Date and time in the following format: YYYY-MM-DDThh:mm:ss.sTZD (more info).
ITEMS		yes	Products included in this order
FINISHED_ON	Date &n time (as a String)	no	Date and time in the following format: YYYY-MM-DDThh:mm:ss.sTZD (more info). Please don't use this parameter or leave it blank if the order wasn't finished.
STATUS	String	no	State of the order: "created", "finished", or "canceled".
EMAIL	String	no	A valid email address
PHONE	String	no	Incl. plus sign and country code (e.g. "+420xxxxxxxxx" for Czech Republic)
ZIP_CODE	String	no	Delivery ZIP code
COUNTRY_CODE	String	no	International identification code of the country (e.g. "CZ" or "US")

ITEMS

Each order must include all products from that order. The product price here determines the selling price paid by the customer (excluding shipping and handling, including VAT).

Name	Type	Required	Description
PRODUCT_ID	String	yes	ID of the product or its variant
AMOUNT	Number (integer, >0)	no	Quantity of the product (default: 1)
PRICE	Number (>=0)	no	Subtotal of all of the pieces of the product, tax included, without shipping and handling.

PRICE processing policy

If an ITEM in the order

does not include PRICE, or
has included PRICE with an error (e.g., it is empty, it is not a number, its a negative number),

then Samba will try to find its current price based on the PRODUCT_ID in the product feed. If the product does not exist in the product feed, the order item will not be processed.

If an item has a PRICE defined more than once in the order, the item will not be processed at all.

An order without valid items will not be processed.

In Samba analytical methods, only completed orders and items with positive prices are taken into consideration.

Example of orders feed

<?xml version="1.0" encoding="utf-8"?>
<ORDERS>
       <ORDER>
             <ORDER_ID>5ds465d</ORDER_ID>
             <CUSTOMER_ID>d4s5a6sd6as</CUSTOMER_ID>
             <CREATED_ON>2014-12-31T03:53:43.962Z</CREATED_ON>
             <FINISHED_ON>2015-01-05T03:53:43.962Z</FINISHED_ON>
             <STATUS>finished</STATUS>
             <ZIP_CODE>15500</ZIP_CODE>
             <COUNTRY_CODE>CZ</COUNTRY_CODE>
             <ITEMS>
                    <ITEM>
                          <PRODUCT_ID>DAS656</PRODUCT_ID>
                          <AMOUNT>6</AMOUNT>
                          <PRICE>36</PRICE>
                    </ITEM>
              </ITEMS>
        </ORDER>
        <ORDER>
             <ORDER_ID>35DS45</ORDER_ID>
             <EMAIL>jan.novak@email.cz</EMAIL>
             <CREATED_ON>2014-12-31T03:53:43.962Z</CREATED_ON>
             <FINISHED_ON>2015-01-05T03:53:43.962Z</FINISHED_ON>
             <STATUS>finished</STATUS>
             <ZIP_CODE>15500</ZIP_CODE>
             <COUNTRY_CODE>CZ</COUNTRY_CODE>
             <ITEMS>
                    <ITEM>
                          <PRODUCT_ID>DAS656</PRODUCT_ID>
                          <AMOUNT>6</AMOUNT>
                          <PRICE>36</PRICE>
                    </ITEM>
              </ITEMS>
         </ORDER>

 </ORDERS>

Incremental orders feed

Samba supports the so-called incremental data feed, which means that this feed contains only those orders that have been created or changed recently. This reduces the load on the servers, where you only need to generate the complete history for the initial update and a small increment every next day.

Procedure

Initial import of history
1. Set the order feed to the Complete type.
2. Enter the URL of the complete feed.
3. Perform a data update in Samba.
Incremental processing
1. Set the order feed to the Incremental type.
2. Insert the URL of the incremental feed.
3. Perform a data update in Samba.

The way the whole process works is that once you switch the type to Incremental, Samba automatically maintains the order history collected so far and aggregates each new increment into this history using the upsert method on ORDER_ID. This means that

a new ORDER_ID appears in the increment – the record is processed and added to the accumulated database in Samba
a previously processed ORDER_ID appears in the increment – the existing order record is discarded and only the parameters (and items) specified in the increment are processed for the order

Until you switch the setting back to the Complete type, Samba keeps this accumulated history in its database.

Incremental type

Samba distinguishes the following types of increments based on how the URL is dynamized:

Static URL
- Use when you always generate on one specific and unchanging URL all orders that have changed during a selected period (the length of the period is up to you, typically 7 days).
- E.g. https://samba.ai/export/orders/orders_increment.xml
Specific date
- Use when you periodically generate a new file for a specific time period – for example, you generate a new daily increment every day.
- E.g. https://samba.ai/export/orders/orders_increment_{date}.xml
Date From – To
- Use when you have a service on your side ready to return order exports by from/to attributes.
- Samba automatically selects from as the date of the last successful run, to is selected as “today”. This ensures the next run to reload boundary data that may have been incomplete at the time of processing.
- E.g. https://samba.ai/export/orders/orders_increment_{from}_{to}.xml

Logic of increment

It is recommended to set the logic so that all orders that have undergone a change during the period appear in the increment. If you set the logic only on e.g. the date of order creation, you may miss information about cancelled orders and returns in Samba.

Processed data

Only those orders from the increment that are valid at the moment are processed and accumulated into the history – it means that all mandatory attributes have to be correct. Samba then processes only those orders for a given data update that are fully determined in terms of the existence of the customer in the customer feed and the existence of the product in the product feed.

Customer in order

If an unknown CUSTOMER_ID is specified (or is not specified at all) in the specific order and there is a customer (in customer feed) with the same EMAIL as used in this order, the order is then automatically assigned to the customer based on the EMAIL element.

However, if there is no such EMAIL in the customer feed, then the value in EMAIL will be temporarily used for generating a new virtual customer with ID equal to EMAIL and this particular order is merged into the accumulated history. However, this order is processed only as long as the order is part of the increment. At any time later, the customer is no longer generated and therefore the order is not processed, until a customer with a CUSTOMER_ID equal to EMAIL appears in the customer feed again.

Incremental Customers Feed

However, if you also use an incremental type of customer feed, then even these virtual customers are never lost and are constantly generated so that their orders can be processed.

If at some point in time the customer CUSTOMER_ID listed for an order that has undergone incremental processing and has been stored in the accumulated database disappears, it will not be processed and read in Samba until the CUSTOMER_ID appears again in the customer feed.

Orders without valid EMAIL and CUSTOMER_ID will not be processed at all.

Product in order

When using increments, it can generally be said that (analogous to the above for a customer in an order) only those product items that contain the products listed in the product data feed are processed. In the case of an incremental data feed, let’s demonstrate how it works with the following example:

Suppose there has been a one-time retrieval of complete data within a data feed and now overnight increments are being used within the same account.
In the example, we have order “Ord1” in the increment (from January 1st), which contains product called “Prod1”:

On the January 1st, an increment of the order feed will be downloaded, which contains order “Ord1” and in the same time there is a “Prod1” in the product data feed. The order will be processed in this case.
A day later (January 2nd) the order “Ord1” is no longer in the increment and the product “Prod1” is no longer in the product data feed. The order will not be processed in this case.
The following day (January 3rd) the order “Ord1” is still not in the increment, but the product “Prod1” is again shown in the product data feed. The order will be processed again in this case.

As we can see, the determining moment for Samba is, whether the product is contained in the product data feed within the time of the last process of the increment – only in this case the data history is correctly saved into the accumulated history of orders. In the following days, the order will be processed again only in case the product is currently residing in the product data feed.

Category feed

The category feed should include the tree of categories used in products feed. TITLE in this feed must correspond to CATEGORYTEXT in product feed.

Supported parameters

Tag name	Type	Required	Description
TITLE	String	yes	Category name
URL	String	yes	Category URL
PARAMETER	[par1,par2]	no	Other category parameters

Example of category feed

<?xml version="1.0" encoding="utf-8"?>
<CATEGORY>
     <ITEM>
          <TITLE>Category</Title>
          <URL>http://www.myeshop.cz/way/to/category</URL>
          <ITEM>
               <TITLE>Subcategory</Title>
               <URL>http://www.myeshop.cz/way/to/Subcategory</URL>
          </ITEM>
     </ITEM>
     <ITEM>
          <TITLE>Category A</Title>
          <URL>http://www.myeshop.cz/way/to/categorya</URL>
          <ITEM>
               <TITLE>Subcategory A</Title>
               <URL>http://www.myeshop.cz/way/to/Subcategorya</URL>
               <ITEM>
                    <TITLE>Subcategory B</Title>
                    <URL>http://www.myeshop.cz/way/to/Subcategoryb</URL>
               </ITEM>
          </ITEM>
     </ITEM>
</CATEGORY>

Using empty feeds

If you don’t use some of the feeds and you need to update the data in Samba, you can simply use the following links to the so-called empty feeds. This can be especially useful if you only want to integrate the customer database in Samba and need to synchronize unsubscribed customers and recalculate customer filters.

Feed type	URL
Products	`https://samba-feed-examples.s3.eu-west-1.amazonaws.com/empty/products_empty.xml`
Orders	`https://samba-feed-examples.s3.eu-west-1.amazonaws.com/empty/orders_empty.xml`
Customers	`https://samba-feed-examples.s3.eu-west-1.amazonaws.com/empty/customers_empty.xml`

This post is also available in:

Updated on August 8, 2022

Was this article helpful?

Yes No

Properties of the data feeds

Products feed

Supported parameters

Product variants

Rounding of prices

Customer groups with different prices

Example of the products feed

Customers feed

Supported parameters

Example of customers feed

Incremental customers feed

Incremental type

Orders feed

Supported parameters

ITEMS

Example of orders feed

Incremental orders feed

Incremental type

Processed data

Customer in order

Product in order

Category feed

Supported parameters

Example of category feed

Using empty feeds

Was this article helpful?

Related Articles