Didomi fix guide
Didomi and Global Privacy Control: why some tags still fire
Didomi says it detects Global Privacy Control automatically, stops data sharing and targeted advertising, and shows an Opt-Out Request Honored message. That only reaches tags and vendors wired through Didomi. Anything loaded around it keeps running.
Free. No account. Results in about a minute.
What Didomi says it does
- Didomi says it reads the GPC signal in real time with no custom code.
- When the signal is present, Didomi says sharing and targeted advertising stop.
- It can show an Opt-Out Request Honored message, which California requires from 2026.
- Didomi lists obligations that stay with the site, including making sure downstream recipients honor the opt-out and monitoring it continuously.
From Didomi's own documentation, linked below.
Setting it up
Didomi doesn't publish step-by-step GPC settings. Ask your Didomi contact which categories the signal opts out of, then test the live site. The settings page saying it's on isn't proof that tags stop.
Why tags still fire with Didomi
- Tags that don't wait for Didomi. Pixels added directly to the page, or tag manager tags that don't check Didomi's consent state, run before or regardless of it.
- Vendors missing from the vendor list. Didomi can only withhold consent from vendors it knows about. A new ad partner added without updating the notice isn't covered.
Gaps on every consent platform
- Pixels hardcoded outside the consent platform. A Meta or TikTok pixel pasted into the theme, or injected by a store app, never asks the consent platform for permission. It fires no matter what the banner says.
- Tag manager tags with no consent condition. Google Consent Mode only governs Google's own tags. Meta, TikTok, Pinterest and other tags in Google Tag Manager need their own triggers or consent checks, or they run for everyone.
- Ad tags filed under the wrong category. The opt-out only blocks the categories it's applied to. An advertising pixel sitting in a functional or performance category keeps running after the signal.
- Tags loading other tags. One ad script can pull in several more. The consent platform may gate the first one and never see the rest.
- Server-side forwarding. Conversion APIs and server containers send data from your server, not the browser, so the browser's opt-out never reaches them unless you pass it along.
Which tags do this most? See pixels that ignore opt-outs.
Questions
Does Didomi support Global Privacy Control?
Didomi says it detects Global Privacy Control automatically, stops data sharing and targeted advertising, and shows an Opt-Out Request Honored message. That only reaches tags and vendors wired through Didomi. Anything loaded around it keeps running.
Why do trackers still fire after GPC with Didomi?
Usually because the tag isn't under Didomi's control: it's hardcoded in the page, loaded by an app or another tag, or sits in a category the signal doesn't reach.
How do I test whether Didomi honors GPC on my site?
Load the page with Global Privacy Control on, without touching the banner, and record every request. Consentinel's free scan does exactly this and names every ad vendor that ran, with the request as proof.
Sources: Didomi: Global Privacy Control compliance
Other platforms: OneTrust · Cookiebot · Osano · TrustArc
This is a technical guide, not legal advice. Didomi is a trademark of its owner; Consentinel isn't affiliated with it.
See what Didomi is missing on your site.
Free, about a minute. We test reject, accept and Global Privacy Control, and name every tag that ran when it shouldn't have.
Free. No account. Results in about a minute.