Does Criteo require cookie consent?

Consent is normally required when the tracker stores or accesses non-essential device information, collects analytics identifiers, powers advertising, records sessions, or transmits personal data before a user has opted in.

How does ConsentLens detect Criteo?

ConsentLens checks known network domains, JavaScript globals, script source patterns, and inline script snippets, then compares the matched tracker against the page load timing and consent banner state.

How often does Criteo fire before consent?

In the latest public ConsentLens scan dataset, 0% of sites where Criteo was detected fired it before consent.

MarketingHigh consent risk

Criteo GDPR compliance and consent risk

Criteo provides personalized retargeting ads. This page combines ConsentLens detection rules with live public scan data so you can see how often Criteo appears, whether it fires before consent, and which compliance issues it tends to create.

Scan your website View global tracker stats

Of scanned sites

1 of 384 public sites include Criteo.

Fire before consent

0 detected sites fired it before a user could consent.

Seen after rejection

No post-rejection evidence found in public scan data.

HIGH

Consent risk

Marketing tracker classified from ConsentLens tracker database.

How ConsentLens detects Criteo

Domains

static.criteo.net
dis.criteo.com

Globals

window.criteo_q

Script patterns

criteo.js

ConsentLens combines these signals with request timing. If Criteo sends a data request during the first 500ms of page load, it is treated as a pre-consent tracking risk and connected to the relevant scan evidence.

Common compliance issues

Advertising / remarketing trackers detected

Pre-consent tracking guide Cookie consent requirements How scoring works

Example public scans detecting Criteo

Domain	Score	Consent timing
gravelsoft.com	78/100	No early fire