Criteo: tracking for retargeting shoppers

Your store tells Criteo about product views, the cart and purchases, so it can show shoppers ads with the products they looked at after their visit. What we set up and where you check that data is arriving.

⏱ 4 minBeginnerUpdated 8 Oct 2026

Criteo shows ads with your products to visitors who have already been to your store and didn't buy. So that it knows which products interested whom, the store sends it a short message on every page: on the home page a visit, in categories and search the list of products shown, on the product page the SKU, price and stock, in the cart its contents, and on purchase the order number with the products.

Before you start

  • a contract with Criteo and access to Criteo Management Center,
  • a product catalogue that Criteo receives as agreed with your Criteo account manager (usually the same list as for Google Shopping).

We set it up for you

We enter the account number you get from Criteo. Send it to us together with the contact details of your Criteo account manager, who will check the setup.

Stores › Configuration › Magelan › Criteo OneTag

You can stop tracking yourself at any time: set Enable to No, click Save Config and flush the cache. Don't change the Account ID field.

Criteo works with marketing cookies, so tracking must be tied to the cookie banner (GDPR: cookies and consent): messages are only sent once the shopper allows marketing. We set this up during installation. For a logged-in shopper, the store sends the email address in a hashed form from which the address can't be read; Criteo only uses it to match against its own users.

Where you see the data

  1. In Criteo Management Center, open your advertiser account and the tag checking section (Event Tracking or Criteo OneTag).

  2. Open your store, accept cookies, view a product, add it to the cart and open the cart. Criteo shows the events it received within a few minutes, including whether each product SKU matches the catalogue.

  3. Purchases appear in the sales reports the next day.

The product SKUs in the catalogue Criteo has must match the SKUs in your store. If Criteo reports a mismatch, check that the catalogue contains the product SKU and not some other identifier.

Common problems

Criteo doesn't receive events

Check Enable for the right store view, and that you allowed marketing cookies during your test. Then write to us; we'll check the account number.

Criteo reports that products aren't in the catalogue

The SKUs in the catalogue at Criteo don't match the SKUs in your store. Sort out the catalogue with your Criteo account manager.

Purchases aren't counted

The shopper didn't return to the thank-you page after paying (for example they closed the bank window) or declined marketing. That's why a small share of purchases is always missing.

Was this article helpful?

Related