theMarketer's integration relies heavily on receiving data regarding the interaction of customers with your products. In order for product-related events to be captured properly, you are required to send a detailed product feed.
The product feed needs to be accessible on your website (eg. https://www.yourwebsite.com/product_feed.xml)
Sample feed file:
<?xml version="1.0" encoding="UTF-8"?>
<products>
<product>
<id>123</id>
<sku>ABC123</sku>
<name><![CDATA[Sample product name]]></name>
<description><![CDATA[Sample product description]]></description>
<url>https://www.yourwebsite.com/sample-product-url</url>
<main_image>https://www.yourwebsite.com/main_image.jpg</main_image>
<category><![CDATA[Men|Clothes|Shirts]]></category> <!-- full category tree, categories separated by | -->
<brand><![CDATA[Brand name]]></brand>
<acquisition_price>20</acquisition_price>
<price>85</price>
<sale_price>39</sale_price>
<sale_price_start_date>2022-05-02 09:00</sale_price_start_date> <!-- promo price availability start date -->
<sale_price_end_date>2022-05-10 09:00</sale_price_end_date> <!-- promo price availability end date -->
<availability>1</availability> <!-- 0 - out of stock, 1 - in stock, 2 - in supplier stock -->
<stock>200</stock> <!-- Total stock in pieces. If stock is 0, then availability can be 0 or 2. If stock > 0, then availability must be 1 -->
<media_gallery>
<image>https://www.yourwebsite.com/image1.jpg</image>
<image>https://www.yourwebsite.com/image2.jpg</image>
<image>https://www.yourwebsite.com/image3.jpg</image>
</media_gallery>
<variations>
<variation>
<id>123</id>
<sku>ABC123-S</sku>
<acquisition_price>20</acquisition_price>
<price>85</price>
<sale_price>39</sale_price>
<size><![CDATA[S]]></size> <!-- filled in if variation is on size, else do not send the size parameter -->
<color><![CDATA[Red]]></color> <!-- filled in if variation is on color, else do not send the color parameter -->
<availability>1</availability> <!-- 0 - out of stock, 1 - in stock, 2 - in supplier stock -->
<stock>20</stock> <!-- Total stock in pieces. If stock is 0, then availability can be 0 or 2. If stock > 0, then availability must be 1 -->
</variation>
<variation>
<id>123</id>
<sku>ABC123-M</sku>
<acquisition_price>20</acquisition_price>
<price>85</price>
<sale_price>39</sale_price>
<size><![CDATA[M]]></size> <!-- filled in if variation is on size, else do not send the size parameter -->
<color><![CDATA[Red]]></color> <!-- filled in if variation is on color, else do not send the color parameter -->
<availability>1</availability> <!-- 0 - out of stock, 1 - in stock, 2 - in supplier stock -->
<stock>20</stock> <!-- Total stock in pieces. If stock is 0, then availability can be 0 or 2. If stock > 0, then availability must be 1 -->
</variation>
</variations>
<created_at>2021-04-18 08:15</created_at> <!-- when product was added to the store -->
<recurrence>2</recurrence><!-- product recurrence in days -->
<extra_attributes> <!-- extra product attributes available in the platform, empty if there are no attributes -->
<attribute_name_from_your_platform><![CDATA[Attribute value]]></attribute_name_from_your_platform>
</extra_attributes>
</product>
</products>
In this table you can find the specific requirements for each product attribute:
Attribute | Required | Observations |
---|---|---|
id | Yes | |
sku | Yes | |
name | Yes | |
description | Yes | |
url | Yes | |
main_image | Yes | |
category | Yes | |
brand | Yes | |
acquisition_price | Yes | |
price | Yes | |
sale_price | Yes | |
sale_price_start_date | Optional | |
sale_price_end_date | Optional* | *Required if sale_price_start_date is defined |
availability | Yes | |
stock | Yes | |
media_gallery | Yes* | *If multiple images are not available, please set the main image |
variations | Optional | |
created_at | Yes | |
recurrence | Optional | |
extra_attributes | Optional |