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

Documentation last updated May 29, 2026

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: install the private or unlisted Wix app, connect the correct Cookiezy account, publish the app-hosted runtime, and keep custom code only as a fallback.Hugo Adapter SetupTechnical Hugo setup guide for Cookiezy: generate the dedicated Hugo package, copy the issued config scaffold, align locale routes, and validate banner plus cookie audit behavior.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.DatoCMS Adapter SetupTechnical DatoCMS setup guide for Cookiezy: keep the visitor-facing runtime in the frontend app, use Platform Core for runtime assets, and use the standalone DatoCMS plugin only for editor-side configuration and generated frontend config preview.
Adapter versioningWix app

Wix app release status

Current Wix app version and rollout notes for the primary app-first installation path.

Current version

3.2.0

Delivery lane

Private or unlisted app

Compatibility notes

Wix now uses the dedicated app-first lane. Platform Core custom code remains fallback-only.

Key rollout changes

1. Install the Wix app from Downloads.

2. Link the Cookiezy account in Overview and publish runtime from Settings.

3. Use Platform Core custom-code files only for support or recovery.

Overview

Wix adapter: app-first rollout

Use this guide after purchase to move from Cookiezy account access to a working Wix setup without making merchants manage global Custom Code manually.

  • • Install the private or unlisted Wix app from the Cookiezy install link.
  • • Connect the Wix installation to the correct Cookiezy account and billing profile.
  • • Register the live Wix hostname in billing.
  • • Use the app-hosted runtime URL in Cookiezy Settings.
  • • Publish and test banner, settings, audit, and licensing behavior on the Wix site.
  • • Keep Platform Core custom-code files only as a fallback path.
Developer documentation screenshot for the Cookiezy Wix adapter showing the app-first rollout with account linking, readiness checks, and runtime publish.
Wix technical reference: install link, account linking, readiness, and app-hosted runtime publish.
Step 1

Connect the Wix app to the right Cookiezy account

Open `Cookiezy Overview` inside the Wix app and link the install to the billing email and live hostname that belong to the correct Cookiezy account.

  • • Activate the explicit 14-day Trial or complete paid billing first.
  • • Enter the billing email that owns the target site key.
  • • Register the exact live Wix hostname before publishing the runtime.
  • • Wait until `Cookiezy account linked`, `Site key is present`, and `Hostname is registered` all show `Ready`.
Install flow

How a new Wix customer installs Cookiezy

Use this exact flow for a brand-new Wix merchant. The Wix app is the product surface, while Cookiezy handles billing, hostname registration, site key assignment, and runtime verification.

  • • Start on Cookiezy, activate the explicit 14-day Trial or complete paid billing, then open the Wix app install link from Downloads.
  • • Use that private or unlisted Wix app install link to add the app to the target Wix site.
  • • Open `Cookiezy Overview` in Wix, enter the Cookiezy billing email and the live Wix hostname, then click `Link Cookiezy account`.
  • • If hostname readiness is still pending, go back to Cookiezy billing and register the exact live Wix hostname before continuing.
  • • Open `Cookiezy Settings`, use the current app-hosted runtime URL, save the settings, and publish the runtime on the Wix site.
  • • Visit the real Wix site or the app-managed preview and confirm that the banner appears without any manual Custom Code step.
Step 2

Publish the app-hosted runtime from Cookiezy Settings

In `Cookiezy Settings`, use the current app-hosted runtime URL, save the settings, then publish the runtime on the Wix site. This is the intended primary merchant flow.

Code snippet

Cookiezy Settings
1. Use current app-hosted runtime URL
2. Save settings
3. Publish runtime on Wix site

Expected result
- Runtime publish confirmed: Ready
- No manual Wix Custom Code step required
Scanner and audit

How cookie scanning works on Wix

Wix merchants do not install a separate scanner plugin. The audit and scanner runtime are delivered together with the app-hosted consent runtime that the Wix app publishes to the site.

  • • Do not ask the merchant to upload a separate scanner file or install a second Wix plugin.
  • • After the runtime is published, open the Cookie Policy page and confirm that the audit block renders on the site.
  • • Use the policy page and settings reopen flow to confirm that the scanner output stays in sync after consent changes.
  • • Keep the Platform Core custom-code files only as a support or recovery fallback if app-managed publish needs debugging.
Step 3

Validate the live Wix site

After publish, test the visitor-facing consent flow on the real Wix site or app-managed preview surface.

  • • Banner appears on first visit.
  • • Reject optional keeps optional categories blocked.
  • • Accept all unlocks the optional categories that the merchant configured.
  • • Settings UI can be reopened after the first choice.
  • • Cookie policy audit renders and re-scan works.
  • • Verification returns `allowed: true` for the registered Wix hostname.
  • • If billing is inactive or the hostname is not registered, the runtime falls back to necessary-only restricted mode.
Fallback only

When to use Platform Core custom-code files

Use `cookiezy-platform-core.zip` and the Wix custom-code assets only for support, debugging, or recovery. They are no longer the primary merchant-facing rollout path.

Cookiezy

Lightweight consent platform for modern websites.

Product

FeaturesPlatformsPricingDocsBlogContact

Legal

Cookie PolicyPrivacy PolicyTerms

Language

English
EnglishenSlovenščinaslHrvatskihrItalianoit

Privacy controls

© 2026 Cookiezy. All rights reserved.