How to Add Cookie Consent to Webflow (Without Code)
Webflow handles design and hosting, but GDPR compliance is your responsibility. If your Webflow site uses Google Analytics, Meta Pixel, or any other tracking tool, you need a cookie consent banner before those scripts fire. This guide shows you how to add one in under five minutes, without writing any custom code.
Does a Webflow Site Need a Cookie Banner?
Yes, if it collects any data from EU visitors. Tracking scripts like Google Analytics, Meta Pixel, and embedded third-party widgets all qualify as non-essential cookies under GDPR and the ePrivacy Directive. Webflow doesn't manage this for you. The compliance requirement is on the site owner.
To check what's currently running on your site before you configure anything, use the Consentify domain scanner. It identifies active cookies and flags which ones require consent.
What You Need
- A free Consentify account (the free plan works)
- Access to your Webflow project settings
Step 1 — Create Your Domain in Consentify
Sign up at consentify.app and log in to your dashboard. Click "Add domain" and enter your Webflow site's URL. This creates a configuration for your banner and generates the script tag you'll paste into Webflow.
Step 2 — Configure Your Banner and Integrations
Open the visual editor to design your banner. Set the position (bottom bar, centered modal, or corner widget), adjust colors to match your Webflow site's design, and edit the text your visitors will see. You don't need to write any CSS.
Then go to the integrations tab. Add the tracking tools your Webflow site uses. The most common ones are Google Analytics 4 and Meta Pixel. Consentify will block these from loading until the visitor consents to the relevant category.
Step 3 — Copy Your Script Tag
In your domain settings, copy the script tag. It looks like this:
<script src="https://www.consentify.app/api/gateway/script/YOUR_TOKEN"></script>
Step 4 — Paste It Into Webflow
In Webflow, go to Project Settings → Custom Code → Footer Code. Paste your script tag and click Save. Publish your site. Your banner is now live on every page.
The script loads asynchronously, so it won't slow down your page render. Your Webflow Interactions, animations, and transitions will continue to work as normal.
Step 5 — Add a Revoke Button (Required)
GDPR requires that users can change their consent at any time, not just on their first visit. Add a link or button somewhere on your site with the element ID set to revoke-consent-btn. Your footer or privacy policy page are the standard choices.
To set the ID in Webflow, click the element, open the element settings panel (the gear icon), and type revoke-consent-btn in the ID field. Publish again. Consentify attaches the consent panel to it automatically.
Does It Work With Webflow Interactions?
Yes. Consentify uses a Shadow DOM to keep the banner isolated from your Webflow stylesheets. Your site's CSS doesn't affect the banner, and the banner's styles don't bleed into your layout. There's no conflict with Webflow Interactions, custom animations, or third-party scripts embedded through Webflow.
What Happens to My Tracking Scripts?
Tracking scripts you've configured in Consentify won't fire until the visitor consents to that category. Before consent, they're blocked at the script level. After consent, they load and run as normal. Consent is stored for 12 months by default, so returning visitors don't see the banner again unless your policy changes, for example when you add a new integration.
Can I Use This for Client Sites?
Yes. The free plan covers one domain with no watermark and no page view limit. For managing multiple Webflow client sites from one dashboard, paid plans start at 39 NOK per month. The Consentify for Webflow page has a full breakdown of what's included at each plan level.
If you're a Webflow agency handling compliance as part of your service, you might also find the comparison with Cookiebot useful if you're evaluating options for multiple clients.