Getting started

Check readiness, generate the package, then test the live flow.

This is the shared rollout path for every adapter after purchase, including readiness checks, hostname registration, and restricted-mode recovery if billing is not active.

• Choose the correct package from customer downloads and confirm it is ready to generate.
• Register every live hostname in billing before publish.
• Install the adapter with the matching Developer guide.
• Review the issued package and confirm the embedded site key, verification URL, and billing portal URL match the account before launch.
• Test first visit, reject optional, accept all, settings reopen, audit page, runtime verification, and restricted-mode recovery.

Code snippet

1. Open customer downloads and confirm the package is ready to generate.
2. If billing or the account site key is missing, resolve that in billing first.
3. Generate the correct issued ZIP.
4. Register the production hostname in billing.
5. Follow the adapter-specific Developer docs page.
6. Set locale and policy URL, then verify the embedded siteKey, verifyUrl, and billingUrl from the issued package.
7. Confirm /api/licensing/verify returns allowed: true and only publish after the live hostname passes all checks.

Cookiezy getting started screenshot showing the shared post-purchase rollout from downloads to billing and adapter setup. — Shared rollout reference: downloads, domain registration, adapter install, and live verification.

Adapter map

Choose the correct guide for your platform

Use the guide that matches the package and runtime you are actually deploying.

• Webflow: `/en/docs/adapters/webflow`
• Shopify: `/en/docs/adapters/shopify`
• Wix: `/en/docs/adapters/wix`
• WordPress: `/en/docs/adapters/wordpress`
• Headless: `/en/docs/adapters/headless`
• React: `/en/docs/adapters/react`
• Next.js: `/en/docs/adapters/nextjs`

1. Open customer downloads and confirm the package is ready to generate. 2. If billing or the account site key is missing, resolve that in billing first. 3. Generate the correct issued ZIP. 4. Register the production hostname in billing. 5. Follow the adapter-specific Developer docs page. 6. Set locale and policy URL, then verify the embedded siteKey, verifyUrl, and billingUrl from the issued package. 7. Confirm /api/licensing/verify returns allowed: true and only publish after the live hostname passes all checks.