Overview

Headless adapter: post-purchase rollout

Use this guide for any custom frontend that relies on the plain adapter runtime from the ZIP package.

• Download `platform-cookie-core.zip` from the customer area.
• Copy the plain adapter and shared core assets into your global shell or CDN.
• Register every live hostname in billing.
• Boot the runtime with `license.siteKey`, `license.verifyUrl`, and `license.billingUrl` before UI and scanner load.
• Validate `allowed: true`, consent state gating, policy page audit behavior, and the necessary-only fallback when licensing is not active.

Developer documentation screenshot for the Cookiezy headless adapter showing shell bootstrap and licensing verification. — Headless technical reference: plain adapter boot, verify URL, and shared runtime helpers.

Step 1

Load the runtime from the app shell

Serve the shared CSS, core runtime, UI, scanner, and `headless-bootstrap.js` from a path available to every route.

Code snippet

<link rel="stylesheet" href="/cookie-consent.css" />
<script src="/headless-bootstrap.js"></script>
<script src="/cookie-consent.js"></script>
<script src="/cookie-consent-ui.js"></script>
<script src="/cookie-consent-scanner.js"></script>

Step 2

Boot with licensing verification enabled

Runtime verification is mandatory for production so the adapter cannot be copied to unlimited domains without an active licensed hostname.

Code snippet

window.CookiezyPlainAdapter.boot({
  locale: "en",
  storageKey: "cookiezy_headless_v1",
  policyUrl: "/en/cookie-policy",
  license: {
    siteKey: "ck_live_cookiezy_demo",
    verifyUrl: "https://cookiezy.com/api/licensing/verify",
    billingUrl: "https://cookiezy.com/en/billing"
  }
});

Step 3

Wire helpers and run production tests

Use the helper methods on every production frontend so visitors can reopen settings and inspect the policy page audit.

Code snippet

window.CookiezyPlainAdapter.registerSettingsLink(document);
window.CookiezyPlainAdapter.mountAudit(document);

Testing

Headless test checklist

Do these checks before launch on each hostname.

• Verification endpoint returns `allowed: true` for the registered hostname.
• First visit shows the banner.
• Optional analytics stays gated until consent.
• Settings link reopens the modal.
• Policy page audit mounts and re-scan reflects the current state.
• If licensing is missing or inactive, the runtime falls back to necessary-only mode and shows a billing recovery path.

<link rel="stylesheet" href="/cookie-consent.css" /> <script src="/headless-bootstrap.js"></script> <script src="/cookie-consent.js"></script> <script src="/cookie-consent-ui.js"></script> <script src="/cookie-consent-scanner.js"></script>

window.CookiezyPlainAdapter.boot({ locale: "en", storageKey: "cookiezy_headless_v1", policyUrl: "/en/cookie-policy", license: { siteKey: "ck_live_cookiezy_demo", verifyUrl: "https://cookiezy.com/api/licensing/verify", billingUrl: "https://cookiezy.com/en/billing" } });