Criteo feed for Shopify

Criteo offers three ways to connect a catalog: an e-commerce-platform integration (Shopify among 35+), a Product Feed URL it polls, and Criteo's own FTP. The feed URL is the one that gives you control of the file. The feed must be CSV or XML in the Google Feed format, and ZIP or GZ compression is supported across all connection types.

Criteo imports the catalog every day, you can schedule up to four imports a day (UTC), and a manual import can be launched at any time. Two safety rails sit on the merchant's side: if your server filters by IP, Criteo's ranges 178.250.0.0/21 and 2a02:2638::/32 need allow-listing, and the Feed Stability threshold blocks an import in which too many products would become non-displayable at once, until you review it. Feedflock hosts the file on a stable URL and regenerates it every hour, so every import picks up current prices and stock.

Criteo's setup guide says it three times: a feed for the URL connection must be CSV or XML in the Google Feed format, a Google or Facebook feed can be reused with no extra formatting, and the guide's own XML sample is a Google RSS 2.0 document. There is no Criteo XML dialect of its own.

When a Google-structured feed arrives, Test Setup builds a ready-to-use configuration with 3 mappings and 9 predefined rules, locked because they align Google's structure with Criteo's specification. The mappings cover the three names where Criteo's vocabulary differs: title becomes name, link becomes producturl, image_link becomes bigimage. Every other field name is the Google name, which is exactly the spelling Feedflock emits.

The pairing that matters on Criteo is to the pixel: the feed's id must exactly match the ID your website pixel reports for the same product, and Criteo warns that any change to product IDs disrupts display and reporting. The template defaults id to the SKU, falling back to the Shopify variant ID. Each variant of a product needs its own distinct id, grouped under a shared item_group_id, and the two ranges must never meet, because an id equal to an item_group_id is undefined behavior and updates may be ignored.

Criteo labels gtin and mpn Required, with a condition attached: the MPN is required for products without a GTIN, and products with neither may not be eligible for all features (they are still displayable). The template therefore treats them as a conditional pair rather than hard requirements: gtin comes from the Shopify barcode (8, 12, 13 or 14 digits) and mpn stays empty unless you map a real manufacturer number.

Prices are written with a period decimal separator and no thousands separator, with the ISO currency code in the value, as in Criteo's own samples: 59.00 USD. Criteo's naming is the reverse of Google's: its price is the final price after a discount and retailprice the standard price before one. In a Google-format feed that pair is exactly g:sale_price and g:price, which Criteo's XML sample carries, so the template keeps Google's meanings (g:price holds the regular price, g:sale_price the amount actually charged) and Criteo's locked rules do the swap.

Availability is one of three values spelled with spaces: in stock, out of stock, preorder. A sold-out variant stays in the feed marked out of stock, and Criteo excludes it from the banners itself. It counts as Not Displayable, alongside anything missing its ID, name, URL or image. Criteo publishes no file-size or item cap; the only limit is 256 KB of data per product.