r/squarespace
Squarespace's cookie banner restricts "some" third-party services, and a pixel pasted into Code Injection isn't one of them
- upvotes
- 1
- comments
- 0
Post
Highlighted: the lines this signal was extracted from
Squarespace's own help page on the cookies it uses says it plainly: "Adding a cookie banner disables or restricts cookies placed by some third-party services connected to your site, but not all." Their example is tracking added to an audio block. The bigger one for most sites is Code Injection. A Meta Pixel, TikTok Pixel or Google Ads tag pasted there as a plain script runs on page load, banner or not, because nothing in it asks the banner first. And you won't notice from your own browser, because Squarespace says the banner doesn't display while you're logged in. A five-minute check: Open your site logged out, in a private window, with dev tools on the Network tab. Reload. Don't touch the banner. Filter for facebook, doubleclick, googleadservices, google-analytics, tiktok and pinterest one at a time. Anything listed went out before the visitor chose. Click Decline, reload, filter again. Anything still there ignores the choice. If something shows up, the fix is code, not a setting: In Cookies & Data Privacy, set the banner type to Opt In and Out, the one with a decline button. Wrap each pasted pixel so it only runs when window.getSquarespaceCookies() returns marketing as "accepted". Run that on page load for returning visitors, and again from window.onCookieBannerInteraction for visitors who accept now. Google's Analytics help has a Squarespace page with a ready...
Keep reading with a free account
The rest of this post, and every signal for Squarespace, is in your free account.
Also quoted as evidence
Why it matters in the US, where there's no general opt-in rule: California Invasion of Privacy Act suits over pixels center on that order, a tag sending visitor data before the banner was answered.
From the post