Cookie Consent for Strapi
Cookiezy fits Strapi best as a headless CMS bridge rather than as a native storefront runtime. The recommended pattern is to keep the consent banner and scanner on the frontend, while Strapi stores the locale-aware policy routes and shared runtime settings your frontend reads at boot.
Built for teams that use Strapi to drive content but still want frontend-controlled consent behavior.
Cookie banner preview
Lightweight. Fast. Clear by default.
Cookie consent. Done easy.
Lightweight consent that keeps your site fast and your data intact.
Strapi should own config, not the browser runtime
Strapi is a strong place to store Cookiezy configuration, but the browser runtime should still be loaded by the frontend shell. That keeps consent behavior close to the app that actually renders scripts, analytics, policy pages, and locale routes.
- • Store `defaultLocale`, `localeRoutes`, and policy URL mappings in Strapi.
- • Load Cookiezy from the frontend shell, not from Strapi admin.
- • Use the shared runtime config model so Strapi and the frontend stay aligned.
- • Keep licensing verification and hostname enforcement in the frontend runtime.
The Strapi adapter follows the headless core pattern
The package includes a Strapi-focused bridge helper that turns CMS-managed values into the same shared Cookiezy runtime config used by other adapters.
Code snippet
<script src="/cookiezy/cookiezy-strapi-adapter.js"></script>
<script>
const strapiCookiezySettings = {
defaultLocale: "en",
localeRoutes: {
en: { policyUrl: "/en/cookie-policy", pathPrefixes: ["/en"] },
sl: { policyUrl: "/sl/politika-piskotkov", pathPrefixes: ["/sl"] }
},
storageKey: "strapi_cookie_consent_v1",
license: {
siteKey: "ck_live_cookiezy_demo",
verifyUrl: "https://cookiezy.com/api/licensing/verify",
billingUrl: "https://cookiezy.com/en/billing"
}
};
window.CookiezyStrapiAdapter.boot(
window.CookiezyStrapiAdapter.buildConfigFromStrapiSettings(strapiCookiezySettings)
);
</script>Use the same live cookie scan on the frontend policy page
Even when Strapi manages the content model, the live cookie scan still belongs on the frontend policy page. Cookiezy can mount the same audit view there so the published page reflects the current browser session and category mapping.
Live cookie scan for this browser session
This audit reads the cookies currently visible on the domain in your browser and maps known cookies to categories and purposes. Re-scan after changing consent to verify what stays active.
How Cookiezy handles cookies on this site
Necessary cookies stay active so the site, login flow, and consent preferences keep working. Optional categories can be enabled or disabled by the visitor through Cookiezy settings.
This scan reflects the current browser session and the current state of consent on this device.
Cookie categories used on the site
Necessary
Required for security, routing, authentication, and storing the consent choice itself.
Analytics
Used to understand traffic and site usage when the visitor has granted analytics consent.
Marketing
Reserved for advertising, retargeting, and campaign tracking when marketing consent is granted.
A stronger consent fit for Strapi-driven websites
Use Strapi for content and configuration, while Cookiezy keeps consent behavior consistent across the frontend.
Shared config model
Keep Strapi-managed locale routes and policy URLs aligned with the frontend runtime.
Frontend-controlled blocking
The consent runtime still lives where scripts actually load, which is safer than trying to push all logic into the CMS.
Multilang-ready
A good fit for Strapi projects that already manage localized content and route structures.
Plugin-ready direction
The adapter is ready to grow into a proper Strapi admin/plugin flow for settings and generated config preview.
Strapi consent FAQ
Short answers for teams evaluating Cookiezy on top of Strapi.
Does Cookiezy already ship as a native Strapi plugin?
Not yet as a full production plugin. The current Strapi adapter is a headless/CMS bridge scaffold designed to keep configuration in Strapi and runtime behavior in the frontend.
Where should the banner actually run?
On the frontend site that Strapi powers. That is where Cookiezy can block optional scripts before consent, mount the audit view, and keep locale-aware policy links in sync.
Can Strapi still manage locale-aware policy URLs?
Yes. That is one of the best uses for the Strapi integration. The adapter can turn Strapi-managed locale routes into the shared Cookiezy runtime config.