CookiezyCookiezy
ProductPlatformsDocsPricingBlogContact
  1. Home/
  2. Docs/
  3. WordPress 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 versioningWordPress plugin

WordPress plugin release status

Current WordPress package version and rollout notes for the dedicated plugin lane.

Current version

1.2.0

Delivery lane

Issued ZIP

Compatibility notes

WordPress Lite is now a separate public lane, while issued or Premium packages keep licensing-aware runtime behavior.

Key rollout changes

1. Use `cookiezy-wordpress-plugin.zip` for issued installs.

2. Cookie audit no longer ships inside WordPress Lite.

3. Consent-driven GTM or GA loading stays in the dedicated plugin lane.

Overview

WordPress adapter: post-purchase rollout

Use this guide after payment to move from `cookiezy-wordpress-plugin.zip` to a tested WordPress production install.

  • • Generate `cookiezy-wordpress-plugin.zip` from customer downloads.
  • • Register the live WordPress hostname in billing.
  • • Upload and activate the plugin in wp-admin.
  • • Enter policy URL and category settings in the plugin settings screen, then confirm the embedded license status is healthy.
  • • Validate shortcode-based settings reopen, cookie audit behavior, and necessary-only fallback if licensing is not healthy.
Developer documentation screenshot for the Cookiezy WordPress adapter showing plugin settings and shortcode-based setup.
WordPress technical reference: plugin upload, settings configuration, and shortcode testing.
Step 1

Upload and activate the plugin

Install the plugin via `Plugins > Add New > Upload Plugin` and activate it before any front-end testing.

Code snippet

Plugin package: cookiezy-wordpress-plugin.zip
wp-admin > Plugins > Add New > Upload Plugin
Step 2

Configure production settings

Set locale and policy route in the plugin settings, then confirm the issued package already exposes the correct licensing values in the plugin status area.

Code snippet

Locale: en
Policy URL: /en/cookie-policy
Licensing status: healthy
Settings link shortcode: [cookiezy_settings_link] or [site_cookie_settings_link]
Audit shortcode: [cookiezy_cookie_audit] or [site_cookie_audit]
Multilang

WordPress follows the site locale, with optional locale route mapping

The plugin runtime already uses `determine_locale()` for the active WordPress locale. For multilingual sites, the remaining requirement is to keep the cookie policy URL aligned with the active translated page.

  • • On a single-language WordPress site, one `Policy URL` setting is enough.
  • • On WPML or Polylang sites, use the `cookiezy_locale_routes` filter to pass per-locale policy URLs into the runtime config.
  • • If you do not provide locale routes, the banner text still follows the WordPress locale, but the policy link remains the single URL from plugin settings.

Code snippet

add_filter('cookiezy_locale_routes', function ($routes, $options, $locale) {
  return array(
    'en' => array(
      'policyUrl' => '/en/cookie-policy'
    ),
    'sl' => array(
      'policyUrl' => '/sl/politika-piskotkov'
    )
  );
}, 10, 3);
Step 3

Place shortcodes and validate the install

Use the settings link and audit shortcodes in the footer and policy page, then test the live hostname.

  • • Banner appears on first visit.
  • • Reject optional keeps optional tools blocked.
  • • Settings shortcode reopens the modal.
  • • Audit shortcode renders the scan on the policy page.
  • • Verification endpoint returns `allowed: true` for the registered hostname.
  • • If billing is inactive or embedded licensing is missing, the plugin stays in necessary-only restricted mode.
Cookiezy

Lightweight consent platform for modern websites.

Product

FeaturesPlatformsPricingDocsBlogContact

Legal

Cookie PolicyPrivacy PolicyTerms

Language

English
EnglishenSlovenščinaslHrvatskihrItalianoit

Privacy controls

© 2026 Cookiezy. All rights reserved.