Documentation last updated May 29, 2026
Installation
Installation follows the same core pattern everywhere.
Cookiezy is one core product with several implementation paths. The exact files differ by platform, but the production-safe sequence stays the same. `plain-html` is the base adapter lane for static or custom shells, `headless` describes the custom-frontend rollout pattern, and `Next.js` is the framework-specific integration path that still uses the plain adapter files.
Code snippet
1. Open customer downloads and generate the correct issued ZIP.
2. Register every live hostname in billing before publish.
3. Follow the matching guide for Webflow, Shopify, Wix, WordPress, plain HTML, headless custom frontends, React, or Next.js.
4. Confirm the package carries the correct license.siteKey, license.verifyUrl, and license.billingUrl values where applicable.
5. In config-based adapters such as Hugo, copy the issued values exactly and do not wrap them in extra escaped quotes.
6. For manual bootstrap adapters, run the adapter boot or config script before loading `cookie-consent.js`.
7. Inspect page source and confirm window.CookiezyConfig renders real values, not empty strings and not values like '"https://..."'.
8. Publish only after /api/licensing/verify returns allowed: true on the live hostname.
9. Test first visit, reject optional, accept all, settings reopen, audit page, and restricted-mode fallback.