Sending Generic XML products to Criteo
Here is how you send the products in your XML file to Criteo with HexFeed: you enter your XML address in Settings and create a profile that maps XML tags to product fields; HexFeed pulls products, prices and stock from your XML source regularly. Then, on the Feeds screen, you create a feed with the “Criteo” option in the platform list and use rules to decide which products go out. Finally, you add the protected XML address from the feed's Access tab on the Criteo side; Criteo reads the feed on its own schedule and keeps your products up to date.
What is Criteo for?
Criteo's product catalog; it feeds Criteo's product-focused retargeting and dynamic ads. HexFeed generates the Criteo feed in Google product data format.
Feed format: XML (in Google product data format)
The Generic XML side
HexFeed connects to your Generic XML store via XML mapping profiles. What you need: the XML address that holds your products and a mapping profile for this XML.
Details of the Generic XML integrationStep by step: Generic XML → Criteo feed
Set up in 10 steps; menu names on the Criteo side may differ slightly depending on your account.
- 1
Open your HexFeed account
Sign up at app.hexfeed.io and create your store.
- 2
Set up the Generic XML connection
In Settings > E-Commerce Platform, select Generic XML and create a profile with “Manage XML Mapping Profiles”: enter the XML address, the tag that represents a product and the field mappings. When the profile is saved, the XML URL is written to the connection automatically.
- 3
Check the first sync
Product data is pulled from your XML source: products in the XML, the price, stock, image and category fields you map, variants (if a variant mode is selected in the profile). The numbers of added, updated and failed records for each run appear on the Integration Logs screen.
- 4
Create the Criteo feed
On the Feeds screen, click “Create Feed”; choose the “Criteo” option from the platform list, then set the feed name and the variant preference. The feed is created protected with an access key.
- 5
Prepare the fields for Criteo
Map your categories to the Google product taxonomy; because the Criteo feed is in Google format, the google_product_category field is filled from this mapping.
- 6
Set up rules, discounts and images
On the Rules tab, filter the products that will go into the feed; if needed, add a feed-specific discount, a product limit and an image template. The Filtered Products screen shows which products will go into the feed.
- 7
Copy the feed address
Copy the address from the feed's Access tab. You give Criteo the “URL with key”, which carries the key in the query string.
- 8
Add the address on the Criteo side
Enter HexFeed's feed address with key in the product feed setting of your Criteo account, or pass it to your Criteo account team.
- 9
Verify the upload
After Criteo processes the catalog, check on the Criteo side that the products can be used in campaigns.
- 10
Monitor access
The feed's access logs show when the Criteo side fetched the feed; the quality score lists missing fields with sample products.
Which fields are written to the Criteo feed?
HexFeed generates the fields below from the product data that comes from your XML source. In a feed with variants, each size becomes a separate row and is linked to the parent product with item_group_id.
id, title, description, linkimage_link and up to 10 additional_image_linkprice, sale_price (if discounted), availability, conditionbrand, gtin, mpn, google_product_category, product_typeitem_group_id and size (in a feed with variants)gender, age_group, color
What does HexFeed add to your Criteo feed?
Instead of sending the data that comes from your XML source as it is, you set up a separate feed for Criteo:
Filtering products with rules
You decide which products go into the feed with rules such as price, stock, size availability, category, brand, color, size, discount rate, product name, tag and GA4 metrics (views, add-to-carts, purchases, conversion). A product must match all the rules you define.
Product limit
You sort the products that remain after the rules by a criterion you choose (e.g. Google purchases in the last 30 days) and take the top N products into the feed.
Feed-specific discount
You schedule percentage or amount discounts that apply only to this feed, with a date range; the price in your store does not change.
Google category mapping
You map your store categories to the Google product taxonomy once; the google_product_category field is filled from this mapping.
Image templates
You design a discount badge, price strip or brand frame once; each product gets an image rendered with its own price and discount, and this image is used as the main image in the feed.
Stock and price sync
HexFeed refreshes product, price and stock data from your store at the frequency set for your store (from hourly to once a day; every 3 hours by default); a product that runs out of stock is written to the feed as out of stock, or removed entirely with a stock rule.
Protected feed address
The feed address is protected with an access key; requests without the key are rejected. The access logs show when the feed was fetched.
Feed quality score
Feed products are analyzed; issues such as a missing GTIN or a short description are listed with sample products, and the change from the previous analysis is shown.
Frequently asked questions about Generic XML and Criteo
What do I need to set up a Criteo feed with Generic XML?
On the Generic XML side you need the XML address that holds your products and a mapping profile for this XML; on the Criteo side you need an account where you can add the feed address. HexFeed generates a feed in XML format for Criteo from the data that comes from your XML source.
When a price or stock changes in your XML source, when does Criteo see it?
HexFeed refreshes product, price and stock data from your XML source at the frequency set for your store (from hourly to once a day; every 3 hours by default). Each time Criteo reads the feed it gets this current data; the reading frequency is determined on the Criteo side.
How are the sizes and colors of my Generic XML products reflected in the Criteo feed?
Variants are read according to the variant mode you choose in the mapping profile. Records with an empty ID are skipped; with the skip condition you can leave unwanted records out from the start. In a feed with variants, each size becomes a separate row and is linked to the parent product with item_group_id.
In which format is the Criteo feed generated?
As XML in Google product data format (RSS 2.0, g: fields). Because Criteo can read this format, no separate conversion is needed.
Can I use the same feed for Google and Criteo?
You can, but a separate feed is recommended: by applying different rules, a product limit and an image template to the Criteo feed, you separately select the products you want to show in retargeting.
Can my Criteo feed address be downloaded by others?
The feed is created protected with an access key; requests without the key are rejected. You give Criteo the “URL with key”, which carries the key in the query string. You can change or remove the key from the feed's Access tab.
Other channels for Generic XML
Criteo from other platforms
Set up your Generic XML → Criteo feed
Set up your Generic XML connection and create your first Criteo feed. If you would like to do the setup together, contact us.
