The Criteo feed

The Criteo feed channel type builds the product catalog Criteo's retargeting banners are made from. This article covers the OneTag the feed needs, Criteo's reversed price columns, and how signup differs outside the US and UK.

Updated November 6, 2026

Criteo runs retargeting ads across the open web: someone browses your store, and Criteo later shows them a banner of your products on other sites. Criteo builds that banner from your product data.

The Criteo feed channel type builds that catalog: a channel whose columns follow Criteo's own product-feed documentation.

Before you start#

Creating this channel prepares a feed. It doesn't open a Criteo account, and it doesn't start any ads.

  • Outside the US and UK, you need Criteo's team. Criteo GO, the self-serve signup, is available in the United States and the United Kingdom only, with other markets planned. Everywhere else, including Sweden, Denmark, Norway, Finland and the rest of Europe, Criteo's team sets up the account after a contract. For most European merchants, Criteo begins with a sales conversation, and a published feed URL is the useful half you can bring to it.
  • The catalog alone runs no ads: Criteo's OneTag has to be live on your store. OneTag is a small JavaScript snippet that tells Criteo what people viewed, added to a basket and bought. Criteo says that without it, it can't deliver personalised ads. You install it on your store, through a tag manager, or with Criteo's Shopify app. Renable delivers the catalog and never the tag, and it can't see whether the tag is there. If nothing runs, check this first.
  • The product IDs your OneTag sends must match the IDs in this feed. Criteo scores the two lists as a match rate: it asks for above 80%, and says that below 60% it affects how the campaign performs. The ads get progressively worse as the IDs drift. Check your match rate in Criteo early, because Renable can't see it.
  • On Shopify, Criteo's own app may already connect you. It syncs the product feed and deploys the tags. A Renable channel adds catalog quality (enriched titles and descriptions, barcode coverage, clean product images) and one place to manage every destination.
  • Criteo builds its own banners, so your Studio templates don't appear in them. The channel type binds image_link to Image link, your own photo as your product feed lists it. To send the image Renable processed (background removed, cropped), bind the column to Product image, with Image link as the fallback for products that have no processed image.

Criteo's price columns#

Criteo's price columns are the reverse of Google's. On Criteo, price is the price after any discount, which a shopper pays today, and retailprice is the regular price before it. On Google, price is the regular price and sale_price the discounted one. When a product isn't discounted, the two Criteo columns hold the same value.

The channel type sets this up for you: price uses Sale price, Renable's current selling price, and retailprice uses Price, the regular one. If you rebind price to the regular price, your products list above what you charge. There's no sale_price column and no sale-price rule.

Creating the channel#

On a project's Channels tab, create a channel and pick the Criteo feed type. It sets up:

  • Criteo's columns: id, title, description, link, image_link, price, retailprice, availability, gtin, mpn, item_group_id, brand, google_product_category and product_type, bound to your product data. Criteo also accepts name, producturl and bigimage for the title, link and image columns, so a channel using those names isn't reported as missing them.
  • One starter rule: availability drops to out of stock when a product's stock hits zero or its content is incomplete. Criteo leaves out-of-stock products out of its banners, so a low fill rate on description or image_link means that share of your catalog is held back.
  • No custom label or extra-image columns. You can add them on the Fields tab.

On the Settings tab, the Used for card shows the channel declared for Criteo with its always-on Dynamic retargeting use, which switches on the field checks. Criteo has no add-ons: its catalog has no video field, and every dynamic layout it publishes shows different products, never several images of one. You can still add the additional-image column by hand. A Criteo feed is always the Main feed.

The file format is preset to CSV because it's the simplest to set up in Criteo: you only declare the delimiter, while XML also needs the product node, ID node and encoding. Criteo reads XML, CSV, TSV and JSON, the widest set of any destination, and you can switch on the Settings tab with no warning.

Delivering the feed#

Criteo fetches your feed URL, and its guide describes adding the feed as something you do yourself in its Management Center. If Criteo's team set up your account under a contract, check with them whether you add it or they do.

  1. In Criteo, open your product catalog's Feeds page, under Assets → Product Catalog.
  2. Click Add Feed and choose Product Feed URL.
  3. Paste your channel's feed URL. Connecting a channel to Meta, Google, or TikTok shows where to find it.
  4. Click Test Setup, check how Criteo read your file on the Feed Preview tab, then click Import to Catalog.

Criteo's feed guide walks through the same steps.

  • Criteo reads the file up to four times a day, at times you schedule in UTC. An edit you publish reaches Criteo at its next scheduled import. A feed with no scheduled imports can't be reactivated, so leave at least one in place.
  • Compression needs both switches. Turning on Compress feed file (.gz) changes the feed address (it gains a .gz), and Criteo's own Compressed Feed setting must be on to match. Do it before you hand over the URL, or do both at once.
  • A big catalog change can block an import. Criteo lets you set the maximum share of products that may become non-displayable between imports, and blocks an import that crosses it until someone reviews it in Criteo. Keep this in mind before a large re-categorisation or a seasonal clear-out.
  • Renable can also push to Criteo's SFTP server, using SFTP delivery on the Settings tab, if that's how Criteo set up your account.

Checking the output#

Check a product on the Preview tab's Source view, and fill rates on the Fields tab. Run results and warnings show on the Activity tab (see Channel events and troubleshooting).

  • Required fields: the Fields tab marks id, title, description, link, image_link and price as required.
  • gtin and mpn are both recommended, because Criteo asks for one or the other on every product and Renable can't express that. Watch the fill rates across the pair.
  • item_group_id is recommended although Criteo's specification calls it required, because it only matters for variants. Without it on a catalog that has variants, Criteo treats each size and colour as a separate product.
  • IDs can be up to 50 characters, plain ASCII, with no quotation marks, which break Criteo's parser. An ID must differ from item_group_id, be unique per variant, and stay the same once products are live, because Criteo keys display and reporting to it. Renable checks the length and the characters.
  • google_product_category is read as ASCII, so an accented path may not land; the numeric ID (like 2271) always does. Renable doesn't check this one.
  • Images must be at least 800 × 800 pixels, under 16 MB, and PNG, GIF or JPEG. Renable can't measure a remote image while writing the feed, so check your own product photos.
  • Availability reads in stock, out of stock and preorder, which is what this channel type writes. There is no backorder value.

Related articles#