Enforce
BetaThe embed that sets a cookie before anyone pressed play.
Video players, maps, chat widgets and scheduling tools contact their vendor as soon as they load. Gating replaces them with a placeholder that explains what loading it will do, and loads it when the visitor agrees.
Content Gating
- Video & map placeholders
- Chat & scheduling widgets
- Explain-then-load
- Per-embed category
How it helps
What you get with Content Gating
A placeholder that says why
"This video is provided by YouTube and sets cookies" is a better experience than a blank space, and a better one than a silent load.
One click to accept
The visitor can allow that category from the placeholder, without opening the full preference centre.
Covers the usual suspects
Video, maps, chat, scheduling and social embeds are the recurring cases; anything else can be gated explicitly.
Control & Blocking
The rest of Control & Blocking
Hold, gate or release services according to the visitor's actual choice.
Automatic Blocking
Hold known scripts and domains until their category is allowed.
Learn moreNative Blocking
In supported builders and frameworks, the service is never emitted until it is allowed.
Learn moreScript Control
Explicit controls: consent categories on tags, deferred sources, tag-manager triggers and SDK callbacks.
Learn moreConsent Manifest
A machine-readable map from service to purpose, vendor, rule and signal.
Learn moreKnow what runs before you ask visitors to trust it.
Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.
No code to install for a scan Public pages only DotCensus runs on DotCensus