Squarespace

Use supported code injection; checkout is not covered by it.

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.

Check code-injection access

Squarespace documents site-wide code injection for Core, Plus and Advanced plans and supported legacy Business/Commerce plans. Check the actual subscription and current Squarespace guidance; plan names and access can change.

Install on supported site pages

Open the site's code-injection settings and paste the full ConsentEase dashboard snippet into the Header area. Save and inspect the published pages and script order. Do not add a second loader using a page code block.

Checkout limitation

Squarespace checkout does not support code injection. A banner added to the site header is not proof of checkout coverage. Order confirmation and other hosted surfaces have their own platform restrictions; review them separately.

Cookies and payments

Classify cookies by actual purpose. A cookie is not automatically Necessary because it belongs to a payment provider. Distinguish payment/session/security needs from analytics, advertising or cross-site profiling.

Competing settings

Review Squarespace's native banner and analytics settings and avoid conflicting consent interfaces. Verify external scripts independently. Do not promise universal third-party blocking from a header installation.

Verify the published site

Use separate fresh browser contexts for no choice, accept, reject and custom preferences. Check tag consent requirements, network traffic, storage and reopening preferences. Test relevant routes and mobile layouts. A theme installation does not prove coverage of checkout, embedded frames or hosted third-party pages.

Related articles

Still need help?

Contact the ConsentEase team and include the website and steps you tried.