Moving to Strict Mode in Osano’s Cookie Consent Manager

Let’s start simple: What is Strict Mode?

Strict Mode is Osano’s most privacy-forward setting.
It gives your visitors the highest level of privacy protection — but it’s also the most restrictive.

When a configuration moves into Strict Mode, Osano follows a simple rule:
If something isn’t known or classified, it doesn’t run.

What Happens in Strict Mode?

When you turn on Strict Mode:

• All classified content (scripts, cookies, and iframes) will run or be blocked based on two things:

  1. The category you assigned it (Essential, Analytics, Marketing, etc.)

  2. The visitor’s consent choices

• All unclassified or unknown content will be blocked by default, no matter what consent the visitor gives.

That means:

• Anything sitting in your Discoveries section that hasn’t been classified yet will be blocked.

• Any items that are ignored, hidden, or not actively managed will also be blocked.

• In short: if Osano doesn’t know what it is, it won’t let it run.

Why Does This Matter?

Strict Mode keeps you safe from accidentally tracking visitors without consent — but it can also cause disruptions if you’re not prepared.

For example:

• If a new vendor script gets added to your site and isn’t classified yet, it will be blocked.

• If an existing vendor changes their script or cookie (which happens occasionally), Osano will block that updated version until you reclassify it.

This means classification should be part of your regular release schedule — just like testing or deployments — to prevent data loss or tracking gaps.

Will Osano Block Browser Extensions?

Usually, no.
Osano only blocks what runs inside your website’s environment, not tools or extensions that live entirely in a visitor’s browser.

However, some extensions that try to track users across sessions may stop working as expected — that’s a rare edge case, but worth knowing.

How to Prepare Your Team

If you’re moving to Strict Mode, communication is key.
Everyone who touches your website — from marketing to developers — should know what Strict Mode does.

For example:

• If marketing adds a new vendor tag in Google Tag Manager and doesn’t see it firing, Osano might be blocking it because it’s unclassified.

• Without knowing that, your team could waste time troubleshooting something that’s actually working as designed.

To avoid confusion, make sure teams know:

• Osano is running in Strict Mode.

• New or updated scripts must be classified before they’ll work.

The Bottom Line

Strict Mode gives you peace of mind that you’re meeting the strictest privacy standards — but it also requires good housekeeping.
Keep your classifications up to date, make it part of your release rhythm, and make sure your teams understand how it works.

That way, you get both privacy and performance.