Advertising · Criteo SA

Criteo: cookies and consent

Retargets visitors with ads on other sites.

Cookies and how long they last

What Criteo SA declares it stores in visitors’ browsers, from its disclosure to the IAB TCF registry.

NameTypeLifetime
uidCookie13 months
optoutCookie13 months
cto_bundleCookie13 months
cto_optoutCookie13 months
cto_bundleLocal storageNo expiry
cto_optoutLocal storageNo expiry

Source: Criteo SA’s disclosure, published for IAB Europe’s Transparency & Consent Framework.

Spot it on your site

  1. Open your site in a private window, without clicking the banner.
  2. Developer tools › Application › Cookies.
  3. cto_bundle is already there? Criteo fires before consent.

Block Criteo until consent

When the scan finds Criteo, Nodbar files it under “Advertising” and holds its scripts back until the visitor chooses. After the install, a new scan checks that nothing fires before consent any more.

Your banner in your colours, with Criteo blocked until the visitor chooses.

Create my banner

FAQ

Is the cto_bundle cookie required?

No. It is used for advertising: the site works without it, so it may only be set with the visitor’s consent.

Can I use Criteo without a cookie banner?

No. An advertising tracker needs the visitor’s prior consent: without a banner to collect it, it must not load.

What happens if the visitor rejects it?

Criteo must not load, on this page or the next ones. The visitor must be able to change their mind at any time, as easily as they chose.

Sources: Nodbar’s tracker database and Open Cookie Database, EDPB guidelines on the ePrivacy Directive. Updated on . This is not legal advice.