Complianz's consent banner and script-blocking markup are served static; blocked third-party embeds show a static placeholder until consent is given, then swap in client-side. The frontend JS calls one specific bridge route for cookie/category metadata.
Hybrid
The consent banner and script-blocking markup are served from the static release, along with pre-consent embed placeholders.
Nothing needs to stay fully dynamic — consent state is resolved client-side after the page loads.
One rate-limited REST route provides cookie/category metadata to the frontend consent script.
No special setup — detected automatically once active, free or Premium.
Any HTML-cleanup step in a static build pipeline that strips unrecognized script attributes could break Complianz's consent-based script blocking, so that specific interaction needs care. Despite having a bridge-friendly consent feature, Complianz's overall capabilities are what actually steer the site-wide mode recommendation toward Hybrid rather than Static + Bridges — worth knowing if you were expecting the lighter mode.
Static Shield Lite is free to install and inspects your actual plugins, not just what's publicly visible.
Get Static Shield
Tulapp