Other Platforms
Find the correct installation surface for a builder or custom site.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Start with platform capabilities
You need a supported site-wide script area that can initialize consent before tracking. Some builders restrict this by plan; some hosted checkout, frames or app surfaces cannot be edited through the site's head.
Choose a specific guide
- Custom server-rendered HTML: use Manual HTML Installation.
- React/Vite: use the document shell, not per-route effects.
- Next.js: choose App Router or Pages Router.
- Webflow, Wix, Jimdo, Shopify and Squarespace: check the dedicated guide and platform boundaries.
Unsupported injection
If the platform cannot run consent initialization before optional scripts, adding a late banner is not a workaround for prior-consent requirements. Use the platform's supported consent controls or change the tracking setup.
Verify, do not assume
Publish the change, inspect script order and run the complete installation checklist. Treat installation editor previews and dashboards as configuration—not proof of runtime enforcement.
Ask support about your exact platform/version and surface, supplying a public test URL and redacted observations, not API keys or visitor data.