Data source: Product feed

You can target ads to people who are already familiar with your business, such as those who have watched, purchased your items, or put them in a shopping cart but never bought them.

To set up ads for these users, create and upload your product feed, and then set up an audience segment based on it.
Step 1. Creating a product feed
A product feed is a file with information about your products or services: product name, price, image links, etc. Product feeds — source data for the automatic generation of dynamic remarketing banners.

Most CMS have built-in function of creating and updating XML-export of the product base, which allows you to automatically generate an XML-file of the product feed. You can check with the provider of the CMS you are using for details.

You only need to create a feed file once and update it as needed. The myTarget robot will download new versions of the feed file with the frequency that you specify in the feed download form in the myTarget interface.

General requirements for the feed file

There must be at least 20 items in a product feed.
When placing a product feed file, you should follow the rules:

  • The file should be placed on the advertiser's side and be accessible via a direct link, without using redirects;

  • The file can be placed in an archive of one of the following types: ZIP (extension *.zip); GNU ZIP (extension *.gz); Bzip2 (extension *.bz2);

  • The file must be saved in UTF-8 or Windows-1251 encoding;

  • All text contained in the fields of the feed file should not contain markup elements (for example, HTML tags);

  • If you need to use in the text field the angle bracket characters, ampersand, apostrophe or double quotes should be replaced with relevant HTML codes to properly display the ad:
<&lt;
>&gt;
&&amp;
'&apos;
"&quot;
Product feed containing import errors will be automatically deactivated 3 days after the last successful import.
Yandex product feeds

Yandex feed XML files. Example of filling

The product feed file must contain the fields that will be used to fill in the ad templates. There are mandatory and optional elements that you can add to your feed and use as macros to form individual text for each product in your ads.
Example of filling the XML-file
<?xml version="1.0" encoding="windows-1251"?>
<torg_price date="2018-01-01 00:01">
<shop>
    <name>Online store</name>
    <company>STORE</company>
    <url>https://www.example.com</url>
    <currencies>
        <currency id="RUR"/>
    </currencies>
    <categories>
        <category id="1" parentId="0">Conditioners</category>
        <category id="2" parentId="1">Wall mounted air conditioners</category>
    </categories>
    <offers>
        <offer id="1" available="true">
            <url>https://www.example.com/cond/model-ls-h0561al</url>
            <price>10596</price>
            <currencyId>RUR</currencyId>
            <categoryId>2</categoryId>
            <picture>https://www.example.com/pictures/model-ls-h0561al-1.jpeg</picture>
            <typePrefix>Conditioner</typePrefix>
            <vendor>LG</vendor>
            <model>LS-H0561AL</model>
        </offer>
        <offer id="2" available="true">
            <url>https://www.example.com/cond/model-ls-h0893</url>
            <price>30203</price>
            <currencyId>RUR</currencyId>
            <categoryId>2</categoryId>
            <picture>https://www.example.com/pictures/model-model-ls-h0893.jpeg</picture>
            <typePrefix>Conditioner</typePrefix>
            <vendor>LG</vendor>
            <model>LS-H0893</model>
        </offer>
    </offers>
</shop>
</torg_price>
Xml-file template
<?xml version="1.0" encoding="windows-1251"?>
<torg_price date="{yyyy-mm-dd hh:mm}">
<shop>
    <name>{Store name}</name>
    <company>{Company name}</company>
    <url>{Store Url}</url>
    <currencies>
        <currency id="{currency}"/>
    </currencies>
    <categories>
        <category id="{ID category}" parentId="{ID parent category}">{Сategory name}</category>
    </categories>
    <offers>
        <offer id="{ID product}" available="{Product availability}">
            <url>{Link to product page}</url>
            <price>{Current price}</price>
            <oldprice>{Old price}</oldprice>
            <currencyId>{ID currency}</currencyId>
            <categoryId>{ID category}</categoryId>
            <picture>{Link to product image}</picture>
            <typePrefix>{Product type}</typePrefix>
            <vendor>{The name of the manufacturer}</vendor>
            <model>{Product model}</model>
            <description>{Description of the product, its properties or features of the offer}</description>
        </offer>
    </offers>
</shop>
</torg_price>

Required elements of the XML file

Element
Description
Code
Announcement of the beginning of the XML file (header)
This is the standard XML document header, which contains information about the version of the XML markup language used and the encoding in which the file was generated.
<?xml version="1.0" encoding="windows-1251"?>
torg_price
The root element of the document, it must contain the date and time of generating the XML file.
<torg_price date="2018-01-01 00:01">
shop
The element should contain information about the advertiser (store), the structure of the used catalog of product categories, and the products themselves.
<shop>

<name>On-line store</name>

<company>"SHOP"</company>

<url>https://www.shop.ru/</url>

<currencies> ... </currencies>

<categories> ... </categories>

<offers> ... </offers>

</shop>
currencies
(nested in "shop")
Used to describe the currencies used to indicate the value of products in the feed. Pricing is possible in rubles (the value of "RUR" or "RUB"), hryvnia (the value of "UAH"), and tenge (the value of "KZT").
<currencies>

<currency id="RUR"/>

<currency id="RUB"/>

<currency id="UAH"/>

<currency id="KZT"/>

</currencies>

categories
(nested in "shop")
Serves to describe the structure of the advertiser's product catalog. Each category must have a unique identifier (ID parameter) and name. The category hierarchy is defined by specifying the parent category id in the parentId field. Category parentId or parentId="0" as root. The directory does not allow a circular hierarchy and the presence of the same categories with the same parent Id.

When building a catalog structure, it is recommended that each leaf category contain products that are identical in type and purpose. It is undesirable to link products to one category based on one manufacturer (for example, if refrigerators and washing machines are tied to the Bosch category at the same time).
<categories>

<category id="1" parentId="0">Conditioners</category>

<category id="2" parentId="1">Wall mounted air conditioners</category>

</categories>
offers
(nested in "shop")
Used to describe products, such as store product offers. Each product offer is described in a separate offer element.
<offers>

<offer> ... </offer>

<offer> ... </offer>

...

</offers>
offer
(nested in "offer")
Describes a specific product.

Must have properties:
  • id - unique identifier of the product (usually a numeric one);
  • available - logical element describing the availability of a product. It must contain the value "true" if the product is available (for example, the product is available), and "false" in case of temporary unavailability. In the absence of this element by default, the system considers that the product is in stock;
<offer id="1" available="true">

<url> ... </url>

<price> ... </price>

<currencyId> ... </currencyId>

<categoryId> ... </categoryId>

<picture> ... </picture>

<typePrefix> ... </typePrefix>

<vendor> ... </vendor>

<model> ... </model>

...

</offer>
url
(nested in "offer")
It is used to specify a link to the advertiser's site where the user will be redirected when clicking on a product displayed in an advertisement. For example, it may contain a link to a store site where you can buy a product or place an order for it.
<url>https://www.magazin.ru/offers/?offer=1</url>
price and currencyId
(nested in "offer")
The price at which the product is offered must be indicated in the price element. The currencyId element specifies the currency identifier (see the description of the currencies element), which represents the price for this product.
<price>10000</price>

<currencyId>RUR</currencyId>
categoryId
(nested in "offer")
Specifies which category the product belongs to. The value must contain the category identifier assigned to it in the description of the category tree in the service element

The value of the categoryId field can be a string of any Unicode characters no longer than 256 characters
<categoryId>1</categoryId>
picture
(nested in "offer")
It is used to specify a link to the product offer image. The link must be direct and must not contain redirects.

Note! When updating the image, be sure to change the link to it, otherwise the changes will not be recognized.

Image requirements:

  • valid image file formats are JPEG, PNG, GIF;
  • the picture should show only the product itself without additional inscriptions, watermarks and logos;
  • the image should be square, i.e. have aspect ratios of 1: 1 (one to one) - use of other aspect ratios is allowed, but the automatic adjustment of the image size to the formats of advertisements may not be performed correctly;
  • the image should have a size of not less than 450 pixels on the larger side (we recommend using images of 600x600 in size - this size corresponds to most ad formats and is suitable for automatic fitting);
  • the background of the image should be plain, we recommend using white color for the background.
<picture>https://www.magazin.ru/pictures/model1.jpeg</picture>
typePrefix

(nested in "offer")
Specifies the type of product. It is recommended to specify the type of product without additional detail. For example, "Fridge", "Dress", "Skates".
<typePrefix>Laptop</typePrefix>
vendor
(nested in "offer")
Specifies the manufacturer of the product. Under the manufacturer refers to the company (brand, trademark) that produces this product.
<vendor>HP</vendor>
model
(nested in "offer")
Specifies the product model.
<model>Pavilion 15-n064sr</model>

Optional XML-file elements

Element
Description
Code
name (nested in "offer")
Used to specify the product name in one line – for example, it can contain the type, the name of the manufacturer and the product model.

Use the name element only if you cannot use the typePrefix, vendor, and model elements. By default, the product name is formed based on the values of the elements typePrefix, vendor and model.

You should avoid specifying the name element and the typeprefix, vendor, and model elements in the product description at the same time.
<name>Laptop HP Pavilion 15-n064sr</name>
oldprice (nested in "offer")
If the current price of the product is lower than the previous one, i.e. the price has been reduced and the discount is valid, the previous price can be specified in the oldprice element.

Based on the difference between the values of the price and oldprice elements, the discount is automatically calculated (rounded to an integer according to the General mathematical rules), information about it is displayed in advertisements (in part of the available formats). The discount is displayed if its size is not less than 5% and not more than 95%.

Also, if the oldprice element contains the same value as the price element, the "New" icon (in the part of available formats) will be automatically displayed on the banner.

Important: the oldprice element does not replace the price element, so you cannot specify oldprice without specifying price– such a product will not be allowed to be displayed.
<oldprice>15000</oldprice>
description (nested in "offer")
It is used to specify an arbitrary description of the product, its properties or features of the proposal.
<description>Super offer!</description>

Google feeds

MyTarget supports Google feeds in the following formats:
  • XML — this format must conform to the basic principles of the XML structure. Products are represented by a set of XML nodes..
  • TSV — the format is based on tab-separated values.
  • CSV — the format is based on comma-separated values.
Example of a Google feed XML file
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:g="http://base.google.com/ns/1.0">
	<channel>
		<title>TSUM</title>
		<link>https://www.tsum.ru/</link>
		<description>TSUM - online store of clothing, shoes and accessories of the world's leading brands.</description>
		<item>
			<g:id>7281042</g:id>
			<link>https://www.tsum.ru/product/4181947-kozhanyi-zazhim-dlya-deneg-dolce-gabbana-bordovyi/</link>
			<g:item_group_id>1314700</g:item_group_id>
			<g:gtin>5100000807830</g:gtin>
			<g:price>17650 RUB</g:price>
			<title>Leather money clipDolce &amp; Gabbana</title>
			<g:description>The maroon money clip doesn't have to be changed from season to season. Made of durable Dauphine embossed leather, this accessory will last for many years. The model with eight credit card slots is decorated with a miniature plate engraved with the brand's logo.</g:description>			<g:image_link>https://st.tsum.com/btrx/i/19/00/50/0//01_808.jpg</g:image_link>			<g:additional_image_link>https://st.tsum.com/btrx/i/19/00/50/0//02_808.jpg</g:additional_image_link>	<mobile_ios_app_link>tsumapp://www.tsum.ru/product/4181947-kozhanyi-zazhim-dlya-deneg-dolce-gabbana-bordovyi/</mobile_ios_app_link>
			<mobile_ios_app_store_id>1089560311</mobile_ios_app_store_id>
			<g:condition>new</g:condition>
			<g:availability>in stock</g:availability>
			<g:brand>Dolce &amp; Gabbana</g:brand>
			<g:google_product_category/>
			<g:gender>male</g:gender>
			<g:age_group>adult</g:age_group>
			<g:material>Genuine leather: 100%; </g:material>
			<g:color>Red</g:color>
			<g:product_type>Male &gt; Accessories &gt; Leather accessories &gt; Money clips</g:product_type>
			<g:mnp>0115/BP1920/A1001</g:mnp>
			<g:size>NS</g:size>
		</item>

Required elements of the Google feed XML file

Element
Description
<title>
The name of the advertiser
<link>
Link to the advertiser's website
<description>
General description of the advertiser's online store/app
<item>
Parent element for a specific product in the feed
<g:id>
Unique product ID
<g:title>
Product name
<g:description>
Product description
<g:link>
It is used to specify a link to the advertiser's site, where the user will be redirected when clicking on the product displayed in the ad.
<g:image_link>
It is used as a link to the product image. The link must be direct and must not contain redirects.

Note! When updating the image, be sure to change the link to it, otherwise the changes will not be recognized.

<g:price>
Used to specify the product price

The price currency is passed in the <g:price> field after the price. Separator: space. Example:

<g:price>8867 RUB</g:price>
<g:availability>
Determines whether the product is available for sale.
It can have one of 3 text values:

-in stock;
-out of stock;
-preorder.
<g:brand>
Specifies the manufacturer of the product. A manufacturer is a company (brand, trade mark) that makes this product.

Optional elements of the Google feed XML file

Element
Description
<g:product_type>
It is used to specify the product's own category of the product manufacturer
<g:google_product_category>
Specifies the product category according to the Google product classification
<g:mobile_android_app_link>
Specifies the deep link URL for Android devices
<g:android_app_link>
Specifies the app ID in Google Play
<g:mobile_ios_app_store_id>
Specifies the app ID in the Apple Store
<g:mobile_ios_app_link>
Specifies the deep link URL for iOS devices
TSV and CSV Google feeds
Requirements for a TSV feed:
  • The first line of the file is the header. It must contain the names of fields separated by tabs.
  • Each field on a separate line is tab-separated.
  • There should be no trailing tabs at the end of each line in the file.
  • There should be no tabs or end-of-line characters in the feed fields.
  • If the feed field contains multiple values, these values should be separated by commas.

Requirements for a CSV feed:
  • The first line of the file is the header, and must contain field names separated by commas.
  • Each field on a separate line is separated by commas.
  • There should be no trailing commas at the end of each line in the file.
  • There should be no commas or end-of-line characters in the feed fields.
  • If the feed field contains multiple values, these values should be separated by commas.

Required TSV/CSV elements in the Google feed

Element
Description
Id
Unique product ID
title
Product name
description
Product description
link
It is used to specify a link to the advertiser's site, where the user will be redirected when clicking on the product displayed in the ad.
image_link
It is used to indicate a link to the product image. The link must be direct and must not contain redirects.

Note! When updating the image, be sure to change the link to it, otherwise the changes will not be recognized.
price
Used to specify the product price

The price currency is passed in the <g:price> field after the price. Separator: space. Example:

price 8867 RUB
availability
Determines whether the product is available for sale.
It can have one of 3 text values:

-in stock;
-out of stock;
-preorder.
brand
Indicates the manufacturer of the product. A manufacturer is a company (brand, trade mark) that produces this product.

Optional TSV/CSV elements in the Google feed

Element
Description
product_type
It is used to specify the product's own category of the product manufacturer
google_product_category
Specifies the product category according to the Google product classification
mobile_android_app_link
Specifies the deep link URL for Android devices
android_app_link
Specifies the app ID in Google Play
mobile_ios_app_store_id
Specifies the app ID in the Apple Store
mobile_ios_app_link
Specifies the deep link URL for iOS devices

Facebook feeds

MyTarget supports Facebook feeds in the following formats:
  • XML — this format must conform to the basic principles of the XML structure. Products are represented by a set of XML nodes.
  • TSV — the format is based on tab-separated values.
  • CSV — the format is based on comma-separated values.
Example of a Facebook feed XML file
<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:g="http://base.google.com/ns/1.0" version="2.0">
    <channel>
        <title>My Deal Shop Products</title>
        <description>Product Feed for Facebook</description>
        <link>https://www.mydealsshop.foo</link>
        <atom:link href="https://www.mydealsshop.foo/pages/test-feed" rel="self"
            type="application/rss+xml" />
        <item>
            <g:item_group_id>SKU-123123</g:item_group_id>
            <g:gtin>12345678912345</g:gtin>
            <g:google_product_category>Toys &amp; Games &gt; Toys &gt; Executive Toys &gt; Magnet
                Toys
            </g:google_product_category>
            <g:id>SKU-123123-RED</g:id>
            <g:title>WidgetThing</g:title>
            <g:description>This product is the product you need to do the thing</g:description>
            <g:link>https://www.mydealsshop.foo/products/widgetthing</g:link>
            <g:image_link>https://cdn.mycdn.foo/files/123123123.jpg</g:image_link>
            <color>Red</color>
            <g:brand>AcmeCo</g:brand>
            <g:condition>New</g:condition>
            <g:availability>in stock</g:availability>
            <g:price>19.99 USD</g:price>
            <g:sale_price>9.99 USD</g:sale_price>
        </item>
    </channel>
</rss>

Required elements of the Facebook XML-file

Element
Description
<title>
Advertiser name
<link>
Link to the advertiser's website
<description>
General description of the advertiser's app/site
<item>
The parent element for a specific product
<g:id>
Unique product identifier
<g:title>
Название продукта
<g:description>
Описание продукта
<g:link>
Serves to provide a link to the advertiser's website, where the user will be redirected when they click on the product displayed in the advertisement.
<g:image_link>
Serves to indicate a link to the product image. The link must be direct and must not contain redirects.

Note! When updating the image, be sure to change the link to it, otherwise the changes will not be recognized.

<g:price>
Serves to indicate the price of goods
The price currency is passed in the <g:price> field after the price. Separator: space. Example: <g:price>8867 RUB</g:price>
<g:availability>
Determines the availability of a product for sale. Can be one of the following text values:
-in stock;
-out of stock;
-available for order;
- discontinued.
<g:brand>
Serves to indicate the manufacturer of the product. A manufacturer is a company (brand, trade mark) that produces this product.

Optional elements of the Facebook feed XML file

Element
Description
<g:product_type>
Serves to indicate the manufacturer's own product category
<g:google_product_category>
Used to indicate the product category according to the Google product classification
<g:custom_label_0> … <g:custom_label_4>
Additional product information that you want to include.
<applink property=ios_url" content="myapp://product/01.00.01.1-1.0.8-8.25.3"/>
Serves for specifying the deep link URL for iOS devices
<applink property="ios_app_store_id" content="111222333"/>
Used to specify the app ID in the App Store
<applink property="ios_app_name" content="myappname"/>
App name
<applink property="android_url" content="myapp://product/01.00.01.1-1.0.8-8.25.3"/>
Serves for specifying the deep link URL for Android devices
<applink property="android_package" content="myapp_package"/>
Used to specify the app ID on Google Play
<applink property="android_app_name" content="myappname"/>
App name
TSV/CSV-feeds Facebook
TSV feed requirements:
  1. The first line of the file is a header, should contain the names of the fields, separated by tabs.
  2. Each field on a separate line is separated by tabs.
  3. There should be no trailing tabs at the end of each line in the file.
  4. There should be no tabs or line breaks in feed fields.
  5. If the feed field contains multiple values, these values should be separated by commas.
CSV feed requirements:
  1. The first line of the file is a header, which must contain the names of the fields, separated by commas.
  2. Each field on a separate line is separated by commas.
  3. There should be no trailing commas at the end of each line in the file.
  4. There must be no commas or line breaks in feed fields.
  5. If the feed field contains multiple values, these values should be separated by commas.

Required TSV/CSV elements in the Facebook feed

Element
Description
Id
Unique product ID
title
Product name
description
Product description
link
It is used to specify a link to the advertiser's site, where the user will be redirected when clicking on the product displayed in the ad.
image_link
It is used to indicate a link to the product image. The link must be direct and must not contain redirects.

Note! When updating the image, be sure to change the link to it, otherwise the changes will not be recognized.
price
Used to specify the product price

The price currency is passed in the <g:price> field after the price. Separator: space. Example:

price 8867 RUB
availability
Determines whether the product is available for sale.
It can have one of 3 text values:

-in stock;
-out of stock;
-preorder.
brand
Indicates the manufacturer of the product. A manufacturer is a company (brand, trade mark) that produces this product.

Optional TSV/CSV elements in the Facebook feed

Element
Description
product_type
It is used to specify the product's own category of the product manufacturer
google_product_category
Specifies the product category according to the Google product classification
custom_label_0 … custom_label_4
Additional product information you want to include
ios_url
Serves for specifying the deep link URL for iOS devices
ios_app_store_id
Used to specify the app ID in the App Store
ios_app_name
App name
android_url
Serves for specifying the deep link URL for Android devices
android_package
Used to specify the app ID on Google Play
android_app_name
App name
Step 2. Download your product feed
To download feed myTarget you should have a counter Top@Mail.Ru. To download feed to myTarget go to "Audience – Product feeds" and fill out the form "Upload product feed":

  • specify a name for the feed (for example, "Women's clothing-Moscow");

  • specify a link where myTarget can download the feed (for example, https://www.example.com/feeds/trg.xml). If the feed file is protected by HTTP-authorization, then specify the login and password in the link (for example, http://username:password@example.com/feeds/trg.xml);

  • choose a counter Top@Mail.Ru will be assigned to the feed;

  • set the feed ID is an arbitrary numeric identifier (which is required for further identification products feed in a special code for dynamic remarketing);

  • specify whether to clear links from the feed from UTM tags;

  • set the feed update period (in hours) – mytarget will download the updated feed file using the link above with the specified frequency.

After filling in all the fields, click the "Add" button-the feed will be loaded and processed.
Product Feed Download
When you upload a feed, an audience segment is automatically created. You can use this segment for your dynamic remarketing campaign in its original form, or you can customize it as you like.

Information about the added feed will be displayed on the page:
Uploaded Product Feed
Dynamic remarketing event statistics
The "Event Stat" link allows you to get statistics on dynamic remarketing events within a specific product feed in an Excel file. Statistics are formed for the previous 91 days starting from the current day.

To get a file with statistics, in the "Status" column click "Events stat":
Button for receiving a file with statistics
The statistics file may look like this:
Statistics file
shop_id - counter identifier TopMail.ru
feed_id - product feed identifier
page_type - type of dynamic remarketing event
  • product - viewing the product in the application or on the advertiser's website
  • cart - add an item to the cart or view the contents of the cart
  • purchase - purchase of goods
count - the number of received events of a certain type
unmatched_count - the number of unmatched dynamic remarketing events, that is, events with products whose id myTarget could not find in the product feed
source_type - kind of source of dynamic remarketing event
  • inapp - the event was received from the mobile application
  • top - the event was received from the site
Manual restore feed
If a product feed has not been used in advertising campaigns for more than 30 days, the system sends it to the archive. You can manually restore the feed file and start using it again. To do this, in the "Status" column click "Restore feed":
Restore feed
After that, the feed will receive the "Active" status.
Was this article helpful?
Yes
No