Webflow cookie consent, added through custom code.
Add the CookieHub implementation code to your Webflow site’s Head code to hold back supported non-essential scripts until consent, show a customizable cookie banner and keep records of visitor consent where consent records are enabled on your plan. No Webflow App required.
- Custom code — no Webflow App
- Added once in Site settings › Custom code
- No site redesign or code refactoring
Why use CookieHub with Webflow.
Webflow gives you visual control over your website, but it doesn’t provide native consent management for analytics tools, marketing platforms or custom scripts. Webflow also lets you load scripts in several places — site settings, page settings, embeds and custom code blocks — and those scripts can fire as soon as the page loads, before a visitor has made a choice.
CookieHub adds the structured consent layer Webflow lacks. It governs when supported scripts, and scripts you tag for consent, are allowed to run and set cookies, wherever they are loaded — without forcing you to restructure your site.
Reliable consent enforcement
Supported non-essential tracking scripts are held back until the relevant consent category is allowed.
Site-level implementation
CookieHub is added once as custom code in your site’s Head code. There is no Webflow App to install and no code refactoring to do.
Brand-friendly customization
Match the consent banner’s layout, colors, positioning and behavior to your Webflow design, without touching HTML.
Added in your site’s Head code. No Webflow App required.
CookieHub does not use a Webflow App. You paste the CookieHub implementation code into the Head code field in Site settings › Custom code, and it loads on every page of your published site. Once it is in place, CookieHub:
- holds back supported non-essential scripts until consent is given
- shows your cookie consent banner to visitors
- manages visitor consent preferences
- records consent decisions in a consent log, where consent records are enabled on your plan
- scans your site for cookies introduced by embeds and integrations
Webflow Custom Code must be available for the site or Workspace. Make sure the domain in your CookieHub dashboard matches the domain your Webflow site is published on.
Webflow steps in the CMS installation guideCookie consent tools for your Webflow site.
Automatic cookie blocking
Supported analytics and marketing scripts only run once the visitor has opted in — including scripts that Webflow would otherwise load on page load. Some third-party scripts need to be tagged manually.
Cookie scanner
Detect cookies set by external integrations such as HubSpot, Google Analytics and Meta Pixel, including new cookies introduced by embeds.
Customizable consent banner
Adjust the banner’s layout, colors, positioning and behavior so the consent experience fits your Webflow design.
Multilingual banners
Show the banner in the visitor’s preferred language when translations are enabled — useful for multilingual Webflow sites.
Consent logging
Keep a record of visitor consent choices in CookieHub’s consent log, where consent records are enabled on your plan.
Dynamic cookie declaration
A cookie declaration ready to embed in any static page or CMS collection page. Cookie scan results help you review it and keep it in line with the cookies your site uses.
Add CookieHub to Webflow in a few steps.
Everything happens in Webflow’s Site settings: no Webflow App, no site redesign and no code refactoring.
- 01
Get your implementation code
In the CookieHub dashboard, add your domain, choose a template and copy the CookieHub implementation code.
- 02
Open your Webflow project
Log in to Webflow and open the site you want to add CookieHub to.
- 03
Open Site settings
Open Site settings for the site from your Webflow dashboard.
Site settings - 04
Open Custom code
In Site settings, open the Custom code tab.
Custom code - 05
Add the code to Head code
Paste the CookieHub implementation code near the top of the Head code field, before tracking scripts, so it loads early on every page.
Head code - 06
Save and publish
Click Save changes, then publish your site. Custom code only goes live once the site is published.
Save changes
Consent control wherever Webflow loads a script.
CookieHub’s automatic cookie blocker handles the most commonly used services. For other services, change the script tag to type="text/plain" and add a data-consent category, so the script only runs once the visitor consents to that category.
How to tag scripts for consentSite-wide custom code
Scripts in the Head code and Footer code fields in Site settings › Custom code, which load on every page.
Page-level custom code
Scripts added in a page’s Page settings, inside the <head> tag or before the </body> tag.
Code Embed elements
HTML and scripts placed on the canvas with Webflow’s Code Embed element, such as third-party widgets.
Webflow Interactions
Interactions, animations and other functional behavior are not affected — only non-essential tracking scripts are controlled.
Already using Google Tag Manager?
If your Webflow site manages tags through Google Tag Manager, install CookieHub through GTM rather than adding a second implementation in your Head code.
View Google Tag Manager setupAdd a cookie declaration page
CookieHub generates a dynamic cookie declaration you can embed in any static Webflow page or CMS-driven legal center, so visitors can see which cookies your site uses.
Learn about the cookie declaration
Webflow questions, answered.
Yes. CookieHub can manage scripts added at any level — Head code, Footer code, Page settings or Code Embed elements. Commonly used services are blocked automatically; for other services, change the script tag to type="text/plain" and add a data-consent category so CookieHub can hold the script until consent.
No. CookieHub is installed through Webflow’s Custom code settings and does not require a Webflow App or any other third-party app.
Open Site settings for your site, go to the Custom code tab and paste the CookieHub implementation code into the Head code field. Click Save changes, then publish your site — custom code only goes live once the site is published.
No. Webflow suggests async or defer for external scripts in Head code, but CookieHub’s automatic cookie blocker needs to load before the tracking scripts it controls. Paste the implementation code as provided, near the top of the Head code field, before tracking scripts.
No. Only non-essential tracking scripts are controlled. Webflow Interactions, layout scripts and other functional behavior are unaffected.
Yes. CookieHub includes extensive styling options for colors, themes, placement and interaction flow.
Yes. CookieHub displays the banner in the visitor’s preferred language when translations are enabled.
Yes. CookieHub generates a dynamic cookie declaration you can embed into any static page or CMS-driven legal center. Cookie scan results help you review and maintain it as the cookies your site uses change.
Webflow Custom Code must be available for the site or Workspace. Webflow links access to custom code to your Site plan or Workspace plan, so check Webflow’s help center for the current requirements.
CookieHub provides tools that help Webflow site owners meet consent requirements under privacy laws such as GDPR and CCPA: holding back supported non-essential scripts until consent, recording consent decisions where consent records are enabled, and helping you keep a cookie declaration up to date.
Bring cookie consent management to your Webflow site.
CookieHub gives Webflow creators and developers the consent control they need — without sacrificing design flexibility or resorting to complex workarounds.