Squarespace's built-in cookie banner manages Squarespace's own cookies and records a preference. It does not stop the third-party scripts you add (Google Analytics, Meta Pixel, marketing tags) from firing before a visitor agrees. ConsentStack adds a real consent layer to any Squarespace site: it blocks those scripts until the visitor opts in and covers GDPR, CCPA, and 70+ other regulations.
Why ConsentStack on Squarespace
- Covers GDPR, CCPA, and 70+ regulations from one snippet, not just Squarespace's own cookies.
- Third-party trackers actually stop when a visitor declines, and your consent log proves it.
- Flat pricing from $29/mo. No per-page or per-domain scanning fees.
- Pixel-perfect brand matching, so the banner looks built into your Squarespace site, never bolted on.
Add ConsentStack to Squarespace
In Squarespace, go to Settings > Advanced > Code Injection and paste the tags into the Header field.
<link rel="preconnect" href="https://cdn.consentstack.io" />
<script src="https://cdn.consentstack.io/consent.js?k=YOUR_SITE_KEY"></script>
<script src="https://cdn.consentstack.io/consent-core.js?k=YOUR_SITE_KEY"></script>Replace YOUR_SITE_KEY with the site key from your ConsentStack dashboard.
Code Injection is available on Squarespace Business and Commerce plans.
Common questions
Squarespace offers a cookie banner, but it manages Squarespace's own cookies and records a preference rather than blocking third-party trackers. Scripts you add, like Google Analytics or the Meta Pixel, can still fire before consent. ConsentStack blocks those scripts until the visitor opts in.
Add the three tags to Settings > Advanced > Code Injection > Header, then save. There is no plugin or build step. Code Injection is available on Business and Commerce plans.
The SDK is around 30 KB gzipped with zero dependencies and loads from a global CDN. It runs at parse time so it can catch trackers before they fire, without blocking your page from rendering.
100+ happy customers
Ship consent on Squarespace. In minutes.
Scan your site free to see what is firing before consent, then turn on real blocking from one install.