Overview

React adapter: post-purchase rollout

Use this guide after payment to move from ZIP download to a tested React integration.

• Download `platform-cookie-core.zip` from the customer area.
• Copy the plain adapter and shared assets into `public/` or your CDN.
• Register the live hostname in billing.
• Load the runtime once from the React shell and boot it with `siteKey` and `verifyUrl`.
• Validate SPA navigation, consent state, and audit behavior.

Developer documentation screenshot for the Cookiezy React adapter showing shell bootstrap and consent-aware runtime gating. — React technical reference: global shell bootstrap and consent-aware analytics gating.

Step 1

Serve the assets globally

Place the plain adapter files and shared assets where the React app can serve them globally from the shell.

Code snippet

public/headless-bootstrap.js
public/cookie-consent.js
public/cookie-consent-ui.js
public/cookie-consent-scanner.js
public/cookie-consent.css

Step 2

Boot Cookiezy from the shell

Boot the adapter before optional integrations run. Include the site key and verify URL in production.

Code snippet

window.CookiezyPlainAdapter.boot({
  locale: "en",
  policyUrl: "/en/cookie-policy",
  siteKey: "pk_live_cookiezy_demo",
  verifyUrl: "https://cookiezy.com/api/licensing/verify"
});

Step 3

Gate integrations and test SPA behavior

Optional analytics and marketing services must wait for consent, even after route changes.

• Banner appears on first visit.
• Consent state survives client-side navigation.
• Optional analytics starts only after explicit consent.
• Policy page audit mounts correctly on the policy route.
• Verification endpoint returns `allowed: true` on the live hostname.