Osano fix guide
Osano and Global Privacy Control: is the toggle on, and is it enough?
In Osano, honoring Global Privacy Control is an optional toggle in the Consent Manager, and it only takes effect after you republish. Osano frames the signal as an opt-out of sale, so tags have to be in the right categories, and under Osano's control, for it to stop them.
Free. No account. Results in about a minute.
What Osano says it does
- GPC handling is a toggle in the Consent Manager. It's optional, and Osano strongly recommends turning it on.
- The change applies only after you republish your configuration.
- Osano treats the signal as an opt-out of the sale of personal information.
From Osano's own documentation, linked below.
How to set it up
- In Osano's Consent Manager, turn on the Global Privacy Control toggle.
- Republish the configuration.
- Check that every advertising and sharing tag is classified so the sale opt-out blocks it.
- Test with a browser that sends GPC.
Why tags still fire with Osano
- Toggle off, or never republished. Because it's optional, the setting is easy to miss, and flipping it without republishing changes nothing on the live site.
- Ad tags not treated as sale or sharing. If a pixel is classified somewhere the sale opt-out doesn't reach, it keeps firing for visitors who sent the signal.
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 Osano support Global Privacy Control?
In Osano, honoring Global Privacy Control is an optional toggle in the Consent Manager, and it only takes effect after you republish. Osano frames the signal as an opt-out of sale, so tags have to be in the right categories, and under Osano's control, for it to stop them.
Why do trackers still fire after GPC with Osano?
Usually because the tag isn't under Osano'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 Osano 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: Osano: Global Privacy Control enabled reporting
Other platforms: OneTrust · Cookiebot · Didomi · TrustArc
This is a technical guide, not legal advice. Osano is a trademark of its owner; Consentinel isn't affiliated with it.
See what Osano 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.