Platforms

Integrations built for the way teams actually ship

Browse every Cookiezy adapter in one place. Each platform page explains the buying flow, installation path, licensing expectations, and testing checklist.

Start free Open docs

From no-code builders to engineering-led frontends, each adapter has a dedicated rollout path.

Cookie banner preview

Lightweight. Fast. Clear by default.

Cookie consent. Done easy.

Lightweight consent that keeps your site fast and your data intact.

Necessary

Analytics

Marketing

Integrations

All supported adapters

Choose the platform you want to deploy on and open its dedicated landing page. Each platform path reflects the current package structure, hostname registration flow, and runtime verification model.

Webflow

Custom code, hosted assets, policy embed, and verification flow.

Shopify

Theme app extension rollout with storefront embed, consent-aware loading, and optional embedded admin flow.

Wix

Private or unlisted Wix app with account linking, runtime publish, and policy-page audit.

WordPress

Dedicated plugin ZIP, wp-admin settings, embedded licensing, and shortcode-based audit.

Headless

Canonical plain adapter for custom shells, helper methods, and runtime verification.

React

SPA-friendly rollout with the canonical plain adapter and consent-aware gating from the app shell.

Next.js

Root-layout integration for App Router, localized policy routes, and runtime verification.

Strapi

Headless CMS bridge for locale-aware config, policy mapping, and frontend-controlled consent runtime.

How to use this page

Pick a platform, then follow the same rollout sequence

Every integration page leads into the same production-safe path: choose the correct package, register the hostname, install the adapter, and test consent plus verification before launch.

• Read the platform page for a simple buying and install overview.
• Open Developers docs for the exact technical steps after purchase.
• Use Customer docs after billing to move through downloads, billing, and verification.
• Expect non-compliant installs to fall back to necessary-only restricted mode until billing and hostname checks are healthy.

Platform FAQ

Common integration questions

Short, structured answers make it easier to compare platforms and understand how Cookiezy behaves across different stacks.

Does Cookiezy use the same consent model across platforms?

Yes. Cookiezy is built around a shared core consent model, even when the install path differs between WordPress, Shopify, Webflow, Wix, headless frontends, or Strapi-driven setups.

Which platforms have the most mature rollout path today?

WordPress, Shopify, Webflow, Wix, headless, React, and Next.js currently have the clearest production rollout paths. Strapi is positioned as a headless CMS bridge with plugin-oriented configuration support.

Do all platforms support hostname verification and restricted mode?

That is the intended rollout model. Supported adapters are designed to verify the active hostname and fall back to necessary-only restricted mode if billing, licensing, or hostname checks are not healthy.

Where should a new team start?

Start with the platform page for the target stack, then open the adapter guide in Developers docs, complete billing and hostname setup, and finally generate the issued package from customer downloads.