CookiezyCookiezy
ProductPlatformsDocsPricingBlogContact
  1. Home/
  2. Docs/
  3. Wix Adapter Setup

Docs navigation

Overview

DocsDeveloper-first documentation for installing, configuring, and verifying Cookiezy across every supported adapter.Getting StartedCheck readiness, generate the right package, then ship the core flow.InstallationInstallation follows the same core pattern everywhere: generate the issued package, register the hostname, install the adapter, and validate runtime verification before launch.ConfigConfiguration keeps locale, policy, categories, layout, and licensing context in sync.

Reference

APIDeveloper-facing runtime methods, browser events, and verification-aware integration notes.

Adapters

Webflow Adapter SetupTechnical Webflow setup guide for Cookiezy: what you receive after purchase, where each file goes, and how to validate the runtime on a published Webflow site.Shopify Adapter SetupTechnical Shopify setup guide for Cookiezy: download Platform Core, deploy the theme app extension, expose the Theme Editor fields, and validate storefront consent behavior before publish.Wix Adapter SetupTechnical Wix setup guide for Cookiezy: host the custom-code package, wire head and footer snippets, and validate licensing and audit behavior after purchase.Headless Adapter SetupTechnical headless setup guide for Cookiezy: boot the plain adapter, wire runtime verification, and validate the audit, settings, and restricted-mode recovery flow in custom frontends.WordPress Adapter SetupTechnical WordPress setup guide for Cookiezy: upload the plugin ZIP, configure licensing-aware settings, and validate shortcode-based settings and audit behavior.React Adapter SetupTechnical React setup guide for Cookiezy: load the plain adapter from the app shell, gate optional services with consent state, and validate SPA behavior.Next.js Adapter SetupTechnical Next.js setup guide for Cookiezy: load the plain adapter from the root layout, keep policy routing localized, and validate consent gating across App Router pages.Strapi Adapter SetupTechnical Strapi setup guide for Cookiezy: keep the runtime on the frontend, use Strapi as a configuration bridge, and map locale-aware policy URLs through the shared core model.
Overview

Wix adapter: post-purchase rollout

Use this guide after payment to move from the downloaded ZIP package to a working Wix production setup.

  • • Download `platform-cookie-core.zip` from customer downloads.
  • • Host the files from `packages/adapters/wix/custom-code/` on a public asset path.
  • • Register the live Wix hostname in billing.
  • • Paste the Wix head and footer snippets into Custom Code.
  • • Publish and test banner, settings, audit, and licensing behavior.
Developer documentation screenshot for the Cookiezy Wix adapter showing custom-code setup and testing flow.
Wix technical reference: asset hosting, global code snippets, and policy audit validation.
Step 1

Host the Wix assets

Upload the Wix custom-code assets and keep their names stable so the snippets continue to reference the correct files. The canonical adapter entry file is `cookiezy-wix-adapter.js`.

Cookiezy

Lightweight consent platform for modern websites.

Product

FeaturesPlatformsPricingDocsBlogContact

Legal

Cookie PolicyPrivacy PolicyTerms

Language

Privacy controls

© 2026 Cookiezy. All rights reserved.

Code snippet

cookiezy-wix-adapter.js
cookie-consent.js
cookie-consent-ui.js
cookie-consent-scanner.js
cookie-consent.css
global-head-snippet.html
global-footer-snippet.html
policy-page-embed.html
Step 2

Configure head and footer custom code

Insert the head snippet for all pages, then add the footer snippet. Cookiezy does not currently provide a public CDN for these files, so replace `__COOKIEZY_ASSET_BASE_URL__`, policy route, and licensing values from the issued package.

Code snippet

<link rel="stylesheet" href="__COOKIEZY_ASSET_BASE_URL__/wix/cookie-consent.css">
<script src="__COOKIEZY_ASSET_BASE_URL__/wix/cookiezy-wix-adapter.js"></script>
<script>
  window.CookiezyWixAdapter.boot({
    defaultLocale: "en",
    localeRoutes: {
      en: { policyUrl: "/en/cookie-policy", pathPrefixes: ["/en"] },
      sl: { policyUrl: "/sl/politika-piskotkov", pathPrefixes: ["/sl"] }
    },
    storageKey: "wix_cookie_consent_v1",
    license: {
      siteKey: "ck_live_cookiezy_demo",
      verifyUrl: "https://cookiezy.com/api/licensing/verify",
      billingUrl: "https://cookiezy.com/en/billing",
      adapter: "wix",
      version: "1.0.0"
    },
    texts: {}
  });
</script>
<script src="__COOKIEZY_ASSET_BASE_URL__/wix/cookie-consent.js"></script>
<script src="__COOKIEZY_ASSET_BASE_URL__/wix/cookie-consent-ui.js"></script>
<script src="__COOKIEZY_ASSET_BASE_URL__/wix/cookie-consent-scanner.js"></script>
Multilang

Map Wix localized paths to policy routes

If the Wix site uses localized folders or locale-specific pages, define `localeRoutes` so Cookiezy can choose the correct banner language and policy page from the current path.

  • • Use one entry per locale with the matching `policyUrl`.
  • • Use `pathPrefixes` when Wix routes are localized under folders such as `/en` or `/sl`.
  • • If the site is single-language, keep the simpler single `policyUrl` setup.
Step 3

Publish and validate the Wix site

After publish, test the consent flow on the live hostname that is registered in billing.

  • • Banner appears on first visit.
  • • Reject optional blocks optional categories.
  • • Footer settings link reopens the modal.
  • • Cookie policy audit renders and re-scan works.
  • • Verification endpoint returns `allowed: true` for the live Wix hostname.
  • • If billing is inactive or the hostname is not registered, the runtime falls back to necessary-only restricted mode.