Skip to documentation content
CookieBeam

Webflow, Wix and Squarespace

Add the CookieBeam loader to a Webflow, Wix or Squarespace site through the platform's head code setting, and what the platform's own features do outside it.

CookieBeam has no app for these site builders. You add the same loader as the script tag method, through the platform's setting for code in the page head. All three only add custom code on paid plans, so check that your plan includes it.

Before you start, add every hostname the site uses under Banner domains, including the platform's own subdomain if visitors can reach it, and publish the banner. Then copy the loader from Deployment → Install.

Menu names below are the platforms' own and can change. The rule stays the same: the loader goes first in the head, on every page, without async or defer.

Webflow

  1. In Webflow, open Site settings → Custom code.
  2. Paste the loader as the first line of Head code, above Google Tag Manager or any pixel.
  3. Save, then publish the Webflow site.

Webflow Analyze and Optimize are built into the platform and cannot be blocked like a script. CookieBeam reaches them through Webflow's tracking consent API instead. The Webflow bridge is on by default under Vendor Consent Signals on the banner's App Integrations page. See Webflow Analyze and Optimize.

Analytics or advertising IDs entered in Webflow's own integration settings load outside your consent banner. Move those tags to code that CookieBeam controls.

Wix

  1. In the Wix dashboard, open Settings → Custom Code and add new custom code.
  2. Paste the loader.
  3. Apply it to All pages and place it in the Head.
  4. Save, then check the published site.

Turn off Wix's own cookie banner so visitors see one prompt. CookieBeam does not connect to Wix's consent policy, so pixels connected through Wix's built-in marketing integrations follow Wix's settings, not your banner. Add those pixels as tags CookieBeam controls instead.

Test on the published domain, not in the Wix editor preview.

Squarespace

  1. Open Settings → Advanced → Code Injection.
  2. Paste the loader at the top of the Header box, before any other tag.
  3. Save.

Turn off Squarespace's own cookie banner so visitors see one prompt. IDs entered in Squarespace's built-in analytics and marketing fields load outside your consent banner; move those tags to code that CookieBeam controls.

Test on the live site in a logged-out window, not inside the Squarespace editor.

For every site builder

  • Code you add elsewhere on the site, such as an embed block or a footer snippet, runs when the page renders. Mark optional scripts inert with type="text/plain" and data-category; see Script blocking.
  • Add a "Cookie settings" link to your footer: <a href="#" data-cb="show-preferencesModal">Cookie settings</a>.
  • Run a scan to find what the platform and its add-ons load.
  • Follow Verify your installation.