Cookie Consent for Headless Websites
Cookiezy is a strong fit for headless teams that want API-first control, flexible rendering, and a consent model that can be shared across custom frontends. The packaged flow uses the plain-headless adapter plus the shared core runtime, UI, scanner, and CSS files.
Built for custom stacks where control, performance, and consistency matter.
Cookie banner preview
Lightweight. Fast. Clear by default.
Cookie consent. Done easy.
Lightweight consent that keeps your site fast and your data intact.
What the headless ZIP includes
After payment you download `platform-cookie-core.zip`. For custom frontends the relevant files are the shared core assets in `packages/core/dist/` plus the plain-headless adapter in `packages/adapters/plain-html/`.
- • `packages/adapters/plain-html/headless-bootstrap.js`
- • `packages/adapters/plain-html/example.html`
- • `packages/core/dist/cookie-consent.js`
- • `packages/core/dist/cookie-consent-ui.js`
- • `packages/core/dist/cookie-consent-scanner.js`
- • `packages/core/dist/cookie-consent.css`
Place the headless bootstrap and core assets in your app shell
Extract `platform-cookie-core.zip`, then host `headless-bootstrap.js` and the shared core files from `packages/core/dist/` on a public asset path or CDN. These files are loaded once from your global layout or shell.
Code snippet
<link rel="stylesheet" href="https://assets.cookiezy.com/headless/cookie-consent.css">
<script src="https://assets.cookiezy.com/headless/headless-bootstrap.js"></script>
<script src="https://assets.cookiezy.com/headless/cookie-consent.js"></script>Boot the plain adapter with your locale and policy URL
Use the same pattern shown in `packages/adapters/plain-html/example.html`. Boot the adapter before loading the UI and scanner scripts so the runtime knows your locale, storage key, and policy route.
Code snippet
<script>
window.CookiezyPlainAdapter.boot({
locale: "en",
storageKey: "cookiezy_headless_v1",
policyUrl: "/en/cookie-policy",
theme: { layout: "bottom-right", themeClass: "" },
texts: {}
});
</script>
<script src="https://assets.cookiezy.com/headless/cookie-consent-ui.js"></script>
<script src="https://assets.cookiezy.com/headless/cookie-consent-scanner.js"></script>Register the settings link and mount the cookie audit
After the scripts load, wire the helper methods from the plain adapter into your frontend. Use `registerSettingsLink(document)` for the footer link and `mountAudit(document)` on the policy page so visitors can inspect the live cookie scan.
Code snippet
<script>
window.CookiezyPlainAdapter.registerSettingsLink(document);
window.CookiezyPlainAdapter.mountAudit(document);
</script>Built for API-first consent workflows
A better fit for engineering-led teams that need flexibility rather than rigid plugin behavior.
Custom rendering control
Bring consent logic into your own frontend architecture and visual system.
Shared consent logic
Use one consent model across several frontend experiences and locales.
Policy page audit
The plain adapter includes helper methods for the settings link and audit mount flow.
Headless-ready rollout
A stronger foundation for teams that do not want framework lock-in.
Headless consent FAQ
Answers for teams building custom websites and composable frontends.
Which ZIP should I use for a custom frontend?
Use `platform-cookie-core.zip` and combine the shared core files from `packages/core/dist/` with the plain adapter files in `packages/adapters/plain-html/`.
Which file boots the headless integration?
The adapter bootstrap file is `headless-bootstrap.js`, and the intended runtime pattern is shown in `packages/adapters/plain-html/example.html`.
How do I connect the footer settings link?
Use `window.CookiezyPlainAdapter.registerSettingsLink(document)` after the scripts load.
How do I show the cookie audit on the policy page?
Call `window.CookiezyPlainAdapter.mountAudit(document)` on the policy page after the scanner script is loaded.