Squarespace cookie banner

It holds what Squarespace loads.
Not what you pasted in.

Squarespace’s cookie banner holds back Squarespace’s own analytics cookies and the integrations it runs for you, such as Google Analytics connected with its measurement ID, until a visitor accepts. It doesn’t hold code you paste into Code Injection or a Code Block: Squarespace says its banner restricts some third-party services “but not all”. Which of your tags waits depends on how each one got onto the site and on which buttons the banner shows. Tick what yours runs below and the checker says what is held, what isn’t and what to change.

Squarespace and Google help pages Read 11 November 2026

By the Builderify team

  • Accept only: Restricted until a yes. Manage cookies off · Decline all off. Visitors can accept. Squarespace says the banner stays away for 30 days after.
  • Accept and Manage cookies: Restriction required. Manage cookies on · Decline all off. Visitors accept or choose by category. Non-essential cookies must stay restricted.
  • Accept, Decline all and Manage: The full set. Manage cookies on · Decline all on. The one-click refusal YouTube’s consent needs, Squarespace says.
  • Remove Restriction: Nothing waits. Advanced Privacy settings. Analytics cookies are placed straight away, without consent.
Illustration · The banner settings, from Squarespace’s help article on cookie banners.
01 / What it holds

Squarespace cookie banner settings:
what each combination does.

You switch the banner on in the Cookies & Data Privacy panel and choose two buttons: Manage cookies and Decline all. With both off, visitors can only accept, and you may leave non-essential cookies restricted until they do or click Remove Restriction. Switch on Manage cookies and Squarespace requires the restriction: visitors accept or choose by category, and you can’t remove it.

What the restriction holds is the second table: Squarespace’s own analytics cookies and some third-party services connected through Squarespace, “but not all”. Squarespace’s help pages don’t agree on the panel’s name (Cookies & Data Privacy in one, Cookies & visitor data in others) and Google’s page still says “Opt in and out” for the banner type, so look for the switches by what they do. The setup for other platforms is in the guide to adding a cookie banner, and the guide to whether you need one starts a step earlier.

Squarespace’s own advice, on its cookies page: if you use third-party cookies or similar tracking technologies, talk to a professional or use a specialist consent tool. Its banner article lists no plan requirement for the banner; Code Injection, where pasted code goes, is on the Core, Plus and Advanced plans and some legacy plans.

The two buttons, from Squarespace’s own table, 11 November 2026
Buttons on Visitors can The banner comes back Non-essential cookies
Neither Accept all cookies. Not for 30 days after they accept, unless they clear their cookies. Restricted until they accept, or you click Remove Restriction.
Manage cookies Accept all, or manage their preferences. After a choice the banner goes and a manage-cookies sub-footer shows for 30 days, then the banner returns. Must be restricted until a visitor accepts. You can't choose Restrict or Remove Restriction.
Manage cookies and Decline all Accept, decline all, or manage their preferences. Not listed separately in Squarespace's table. Not listed separately in Squarespace's table.

Source: Squarespace Help, Providing cookie consent options with a banner.

What the banner does with each kind of tag, 11 November 2026
Kind of tag What Squarespace says So
Squarespace Analytics Its analytics and performance cookies (ss_cid, ss_cpvisit, ss_cvr, ss_cvisit, ss_cvt) are the non-essential cookies the banner restricts. Held until a yes.
Google Analytics added with the measurement ID After you save the ID, enabling the banner is the set-up. Google's consent mode is shared with it. Held, and Google is told the choice.
YouTube Enable the banner with the option to accept or decline. Held with Decline all on.
Google Ads or Google Analytics added as code Review the steps in the code injection article. Squarespace doesn't send the signal for code you pasted. Not held by itself.
OpenTable, Tock Not blocked or restricted; they offer their own cookie consent process. Check each one's settings.
Weglot, Acuity They place necessary cookies, which the banner does not restrict. Never restricted.
An audio block with tracking you added Squarespace's own example of content the banner won't block. Not held.

Sources: Squarespace Help, The cookies Squarespace uses and code injection. The row on code you pasted is our reading of those two pages: Squarespace says the banner restricts some services “but not all” and that you can use code injection to adjust code to follow it.

02 / Banner check

Does the Squarespace cookie banner
block my tags?

Say how your banner is set up and tick what the site runs. The checker marks each one held, held if you change a setting, worth testing or not held, and lists the changes in order. It runs in your browser and sends nothing anywhere.

1. How is the banner set up?
2. What does the site run? Tick all that apply.

accept + manage · 3 items

Your banner · Accept and Manage cookies: Decline all off

Of 3 you run: 2 held as set up below, 1 can’t be promised.

  • Google Analytics, connected with its measurement ID in Squarespace Held

    Held. Squarespace says to save the measurement ID, switch the banner on and switch on Manage cookies; Decline all is the optional one-click refusal. Squarespace lists Google Analytics added this way among the services that use consent mode.

  • YouTube videos on your pages If set up

    Squarespace says YouTube follows the banner when the banner offers accept and decline. Switch on Decline all.

  • Other scripts in Code Injection or a Code Block (a pasted pixel, Hotjar, TikTok, a chat widget) Not held

    Not held. Squarespace says its banner restricts some third-party services “but not all”, and that you can use code injection to adjust such code to follow the banner. Its support can’t help with custom code.

What to change, in order

  1. 01In the Cookies & Data Privacy panel, keep Manage cookies on. Add Decline all if you want a one-click refusal.
  2. 02Switch on Decline all, so the banner offers accept and decline, which is what Squarespace says YouTube needs.
  3. 03Make each pasted script wait: start it from a function that runs only when getSquarespaceCookies().marketing is “accepted” (chapter 03), or use a banner that holds scripts for you.
  4. 04Open the live site in a private window. Squarespace says the banner doesn’t display while you’re logged in.

The other way
One banner that holds scripts for you: Builderify Cookie Consent is a single tag in the Header field that loads Google Analytics and pixels from their IDs and holds the scripts you mark until a visitor agrees. Squarespace’s own banner then has to be switched off so visitors are asked once, and with it off and Restrict chosen, Squarespace’s own analytics and built-in integrations stay restricted for everyone. It was not tested on a live Squarespace site for this page.

The checker applies what Squarespace and Google say on the pages read on 11 November 2026; it can’t see your site. A “held” row is Squarespace’s description, not a test result, and no banner is a compliance guarantee. Sources are listed at the end of the page.

03 / Pasted code

Squarespace cookie banner and code injection:
making your own tags wait.

Google’s help page for Squarespace shows the pattern Squarespace expects. Its snippet goes in the Header field, above a Google Ads snippet: it denies ad_storage, ad_user_data and ad_personalization by default, reads window.getSquarespaceCookies().marketing and sets them to granted when it is “accepted”, and runs the same check again in window.onCookieBannerInteraction when a visitor answers.

The same two hooks can start any script you pasted. The snippet on the right is ours, not Squarespace’s or Google’s, written from those hooks, and it hasn’t been run on a live Squarespace site: paste it into a test page first. Squarespace says its support can’t help with custom code, and that checkout pages don’t support code, so nothing pasted runs there. What Google actually receives is for Tag Assistant to show: the Consent Mode v2 guide has the test.

Google Ads or a Google tag you pasted, in order

  1. 01Switch the cookie banner on and choose a type that offers accept and decline. Squarespace's code injection article calls it Opt in & out; the newer banner article calls the buttons Decline all and Manage cookies. Save.
  2. 02Open the Code Injection panel (Core, Plus, Advanced and some legacy plans) and put Google's consent-mode snippet at the top of the Header field, before the Google tag. Copy it from Google's help page, not from a summary.
  3. 03If you use Google Analytics, don't paste its code here: Squarespace says to save the measurement ID and switch on the banner instead.
  4. 04Run Tag Assistant on the published site: the default state should be denied before the first choice, and update after it.

A script that loads after a yes

For a pixel, a heat map or a chat widget pasted into the Header field. Replace the address with the script’s own. It waits for the marketing flag, which is stricter than an analytics-only flag would be.

<script>
(function () {
  function accepted() {
    return window.getSquarespaceCookies &&
      window.getSquarespaceCookies().marketing === 'accepted';
  }
  function load() {
    if (window.__tagLoaded || !accepted()) return;
    window.__tagLoaded = true;
    var s = document.createElement('script');
    s.src = 'https://example.com/tracker.js';
    document.head.appendChild(s);
  }
  // One function only: if you also use Google's snippet,
  // call both from the same onCookieBannerInteraction.
  window.onCookieBannerInteraction = load;
  load();
})();
</script>

Or one banner that holds scripts for you

Builderify Cookie Consent is a single tag at the top of the Header field. It loads Google Analytics, Google Ads and the Meta Pixel from their IDs and holds the scripts you mark with type="text/plain" and a category until a visitor agrees. It bills 10 credits per 1,000 page loads: your 250 free credits a month cover about 25,000 loads before other modules use them, and packs start at $9 and never expire. It needs a plan with Code Injection.

The catch is Squarespace’s own banner. Visitors should be asked once, so switch it off. Squarespace says that with the banner off and Restrict chosen, visitors can’t accept, so its analytics and the integrations it runs for you stay restricted for everyone. Whether a tag that Builderify loads is affected by that was not tested on a live Squarespace site for this page. The step-by-step is in the cookie banner guide and the header and footer boxes themselves in the guide to adding custom code.

Sources: Google Analytics Help, Set up Squarespace to obtain user consent; Squarespace Help, code injection, adding custom code and the cookies Squarespace uses.

04 / Test it

Squarespace cookie banner not showing?
And what it still won’t hold.

Squarespace says the banner doesn’t display while you’re logged in, and that a visitor who answered doesn’t see it for a while. Then a short list of what it leaves alone, from Squarespace’s own pages.

If the banner doesn’t show

  1. 01Log out of Squarespace or open the site in a private window. Squarespace says the banner doesn't display when you're logged in.
  2. 02Check that the Cookie banner toggle is on and that you clicked Save.
  3. 03Remember the last answer. With both buttons off, an accepted banner stays away for 30 days; with Manage cookies on, a manage-cookies sub-footer shows for 30 days and then the banner returns. Squarespace lists two cookies, ss_performancecookiesAllowed and ss_marketingcookiesAllowed, that remember the choice for 30 days.
  4. 04Look at the Cookie banner layout: Squarespace lets you hide the cookie preferences option, which is a different thing from hiding the banner.

Sources: Squarespace Help, Providing cookie consent options with a banner and The cookies Squarespace uses.

What the banner still leaves alone

  • Scripts and embeds you paste into Code Injection or a Code Block. Squarespace says custom code falls outside its support.
  • An audio block with tracking you added: Squarespace's own example of content the banner won't block.
  • OpenTable and Tock, which run their own consent process.
  • Weglot and Acuity Scheduling, which place necessary cookies. The banner never restricts necessary cookies.
  • Checkout pages. Squarespace says they don't support code, so nothing you paste runs there.

Sources: Squarespace Help, The cookies Squarespace uses, code injection and custom code.

The five-minute test

  1. 01Open the published site in a private window with the browser's developer tools on the Network tab and the Application tab on Cookies. Reload before you click anything.
  2. 02Before an answer, none of ss_cid, ss_cpvisit, ss_cvr, ss_cvisit or ss_cvt should be set, and no request should go to Google Analytics or to your pixels.
  3. 03Click Accept all. The analytics cookies and the tags you allowed should now load, and the two choice cookies should appear.
  4. 04Reload, open Manage cookies, switch the categories off and save. The tags should stay away on the next page.
  5. 05Repeat on a phone, and once with Decline all if you switched it on.

One effect to expect: Squarespace says that when visitors don’t accept analytics cookies, Squarespace Analytics may count a visitor who views ten pages as ten, so its numbers can run far above Google Analytics, which fills the gap with modelling. The Squarespace vs Google Analytics guide works out the rest of the gap. Whether a banner is enough for your visitors’ country is a legal question: the GDPR guide is the start, and Journey records visitors only once they allow analytics.

Source: Squarespace Help, Connect Google Analytics to your site.

Questions

Squarespace cookie banners, before you ask.

Yes. You switch it on in the Cookies & Data Privacy panel and choose whether to show Manage cookies and Decline all buttons. Squarespace's banner article lists no plan requirement. The banner restricts Squarespace's non-essential cookies and some third-party services connected through Squarespace until a visitor accepts, but not all of them.

It does for Google Analytics connected with its measurement ID in Developer tools > External API keys: Squarespace says to save the ID, switch on the banner and switch on Manage cookies, and that Google Analytics then isn't placed unless the visitor consents. It does not hold Google Analytics or Google Ads pasted into Code Injection, which load as written unless you add Google's consent-mode snippet.

Not scripts pasted into Code Injection or a Code Block. Squarespace says its banner restricts some third-party services "but not all", and that you can use code injection to adjust such code to follow the banner; its support can't help with custom code. Its cookie pages name Google and YouTube as the services that use consent mode, not Meta's pixel, so test the pixel integration in a private window with the Network tab open.

Squarespace says the banner doesn't display while you are logged in, so log out or open the site in a private window. Also check that the Cookie banner toggle is on and saved. A visitor who already answered won't see it again for 30 days with the accept-only setting, or sees a manage-cookies sub-footer for 30 days and then the banner returns.

Not on its own. Squarespace says laws may require you to tell visitors about cookies and get permission for non-essential ones, and that if you use third-party cookies or similar tracking you should talk to a professional or use a specialist consent tool. The banner holds what Squarespace loads for you; what you pasted in is yours to hold, and which rules apply to your visitors is a question for a professional.

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.