Consentinel documentation
Consentinel is a consent management platform built around one claim: synchronous block-until-consent, provable.
Two halves, and they only mean something together.
Enforcement. The SDK loads as the first synchronous script on your page and
patches the browser's network APIs — fetch, XMLHttpRequest, sendBeacon,
document.createElement, plus a MutationObserver backstop — before any
tracker has a chance to run. Trackers are not loaded and then cleaned up
afterwards. They never execute.
Proof. A headless browser crawls your site twice: once with no consent, once with consent granted. The difference between the two passes is the evidence of what actually fired before anyone agreed to anything. The crawler records every outbound request and every cookie set, so it reports vendors that no signature list knows about.
Most consent banners load asynchronously and race the trackers they claim to gate. That race is the thing this product is designed not to have.
The one rule
The snippet must be the first synchronous script in
<head>— above every analytics tag, pixel, and tag manager, including inline ones.
This is not a best practice. It is the mechanism. Consentinel blocks trackers by owning the network APIs before anything else runs; anything loaded above it has already won. A correctly configured account with a misplaced snippet protects nothing, and it will look fine until someone checks.
Install guide → · Verify it yourself →
Quickstart
- Add a site in the dashboard and verify the domain (a DNS TXT record).
- Customize the banner and hit Save & publish. Publishing is what builds your bundle — until you publish, the snippet loads nothing.
- Paste the snippet as the first thing inside
<head>.
<script src="https://api.consentinel.co/storage/v1/object/public/bundles/s/cs_YOUR_SITE_KEY.js"></script>
Your exact snippet, with your site key, is on the site's Embed tab.
Then verify the install — do not assume it worked.
How the bundle works
Your configuration is compiled into a per-site JavaScript bundle at publish time and served from a CDN. There is no API call before blocking starts: the banner copy, the block rules, the tracker catalog and the cookie rules are all baked into the file. A round trip to fetch configuration would reintroduce exactly the race the product exists to avoid.
Practical consequences worth knowing:
- Republish after changing anything. The bundle is a build artifact. Config changes do not reach live visitors until you publish again.
- It is small and synchronous on purpose. A typical bundle is around 12 KB gzipped. Loading it synchronously costs a few milliseconds of parse time and is what makes the ordering guarantee real.
- Block rules are generated server-side from the tracker catalog, not from the browser. The full catalog ships in every bundle, so a known tracker is gated whether or not your last crawl happened to see it.
What this product does not claim
Being straight about the boundaries is deliberate. Blocking is not purely a property of our software — it is a property of where your platform lets our script run, and on some platforms nobody can block certain tags, including the platform's own consent tool.
Three things are worth reading before you form expectations:
- On locked site builders, platform-native marketing tags (for example Wix's Marketing Integrations GA4) load above all custom code and cannot be blocked client-side by any tool.
- A tag sitting below our snippet has its execution blocked, but the browser has usually already started fetching the file.
- Stylesheet-delivered resources — web fonts and icon kits — cannot be blocked by any client-side consent tool on any platform. This one surprises people because the dashboard lets you set a rule for them.
Each of these is measured, not estimated. The details, the numbers, and what each one means for you are in What can and cannot be blocked.
Where to go next
| Install | The snippet, placement rules, per-platform guides, and the optimizer settings that silently break it |
| What can and cannot be blocked | The three tiers of tracker, with measurements |
| Verify your install | Check it yourself in DevTools, including the mistake that makes a working install look broken |
| SDK reference | Preferences modal, consent events, the consent cookie, Google Consent Mode |