Does Osano actually block trackers before consent?
When it's installed and configured correctly — yes, that's its job. The problem is that plenty of real-world setups leak anyway, for reasons that have nothing to do with Osano itself. Here's where the leaks come from, and how to verify yours in 30 seconds.
Osano pairs its consent banner with a broader data-privacy platform — cookie discovery and categorization, consent records, and data-subject-request and vendor tooling — aimed at teams that want consent and privacy operations in one place.
RegSentry is not a consent platform and doesn't replace Osano — it's the independent check that your Osano setup is actually holding trackers back until visitors consent. The two are complementary: one manages consent, the other verifies enforcement.
Verify your Osano setup — free real-browser scan, 30 seconds.
Real browser scan, no signup to run it. You see a summary of the findings; the full report with every tracker unlocks with your email.
What Osano does well
A straightforward consent banner backed by cookie discovery and categorization
Consent records and privacy-operations tooling (DSARs, vendor tracking) in the same platform
Blocking of categorized scripts until the visitor consents
A good fit for teams standardizing privacy workflows, not just the banner
The 5 ways a correctly-installed Osano banner still leaks
None of these are bugs in Osano. They're the coverage and configuration gaps that show up on real sites — the reasons a banner that looks right can still fire trackers before consent:
1. Tags added outside Osano A new marketing pixel pasted into the page or added by a plugin never enters Osano's categorization — so its blocking never applies to it.
2. Hardcoded pixels in templates Scripts embedded directly in themes and page templates fire with the page, ahead of any consent logic.
3. Tag-manager triggers that ignore consent state If GTM fires tags on page-load rather than on consent events, trackers launch regardless of what the banner says.
4. Blocking not enabled or left in notice-only mode A banner that displays and records choices but was never configured to actually block scripts is cosmetic — everything loads as if it weren't there.
5. A tracker categorized as “essential” One session-replay or analytics script filed in the always-allowed category and it will fire pre-consent on every page load.
Why independent verification matters
In our 2026 scan of 1,478 small-business websites, 58% fired at least one tracker before the visitor consented — and nearly every affected site already had some consent setup in place. That's not an argument against using Osano; it's the argument for verifying that any consent setup, from any vendor, is actually enforcing. A banner that displays and a banner that blocks look identical to the naked eye. The network tells the truth.
How RegSentry independently verifies enforcement
A real headless browser, not a checklist RegSentry loads your public pages the way a first-time visitor's browser would — with no stored cookies and no prior consent.
It never touches the banner The scan deliberately makes no consent interaction. Whatever contacts a third-party server in that window did so before consent — which is exactly what wiretapping and privacy claims turn on.
Every tracker's first contact, timestamped The scan records the precise moment each session-replay, analytics, chat, and ad-pixel script first calls home, so you get evidence — script, page, and timing — not a guess.
Independent by design RegSentry has no stake in your Osano configuration. It doesn't know or care which scripts are supposed to be gated — it just reports what actually fired. That independence is the point of a verification layer.
Then it keeps watching Monitoring re-scans on a schedule and emails you when a NEW tracker shows up firing before consent — so the tag someone adds next month doesn't quietly undo today's clean result.
How to verify your Osano setup in 30 seconds
Enter your domain below. No signup, no code to install, nothing changes on your site.
RegSentry loads your site in a real browser and never touches the Osano banner — it just watches the network, the way a plaintiff firm's scanner would.
Anything that fired before consent shows up in the report — which script, which page, when — plus the specific fix for each tool (gate it through Osano, correct its category, or wire the tag-manager trigger to consent).
Prefer to eyeball it first? Open your site in a fresh incognito window with DevTools → Network open, reload, and don't click the banner — requests to tracking domains before you consent are the leak. The scan just does that check thoroughly, on every page that matters, with evidence.
See whether your Osano banner is actually blocking — free, no signup.
Real browser scan, no signup to run it. You see a summary of the findings; the full report with every tracker unlocks with your email.