Webflow has no cookie banner of its own, so you add one. Embedra's banner goes into Webflow's Footer code once, sends Google Consent Mode v2 and keeps the Meta Pixel off until a visitor says yes, on a free plan.
Webflow does not ship a cookie banner; its own consent tools cover only its Analyze and Optimize products. Embedra's Cookie Banner adds one with a single line in Site settings, Custom code, Footer code. It starts every Google Consent Mode v2 signal at denied, and loads Google Analytics, Google Ads, Tag Manager and the Meta Pixel only after a visitor accepts. The Free plan covers one banner and 500 views a month with a small Embedra badge. Webflow needs a paid Site or Workspace plan for any custom code, whichever banner you use.
The banner, in detail →No. Webflow's own documentation says its consent tools apply only to Webflow Analyze and Optimize, its built-in analytics and testing. For a banner, it points you to a Marketplace app, a consent platform you already pay for, or one you build yourself with custom code.
Webflow's consent docs →Webflow's Meta Pixel setting has a "Delay for cookie consent" switch, but Webflow says you then need a cookie consent banner of your own, and its tutorial for building one covers only the Pixel. It does nothing for Google Analytics, Google Ads, TikTok or LinkedIn.
Try the controls below. Adjust the padding, match your brand colors, and pick the perfect placement. What you design here is exactly what drops into your site.
Six steps, once. You need a Webflow site with an active Site plan, or a Core, Growth, Agency or Freelancer Workspace: Webflow's rule for any custom code.
Add your widget to Webflow →At app.embedra.io, and add a Cookie Banner.
New banners start as Informational, a notice with one button. Strict gives visitors Accept and Decline, and is what holds your tracking tools.
Under Tracking tools, turn on Google, the Meta Pixel and anything else your site runs, and paste each ID.
If you added Google Analytics under Site settings, Integrations, or the Pixel under Apps & Integrations, delete the ID there, and delete any old tags from Head code and Footer code. Embedra now loads them. "Check my site" in the banner's Integration guide lists what it still finds.

In Webflow: the Webflow logo, Site settings, Custom code, Footer code, then Save changes. Footer code runs on every page.
Webflow runs no custom code in the Designer, so open your live site or your .webflow.io address to see the banner.

Prefer the Designer? "Copy for Webflow" in Embedra copies the banner as a Code Embed: paste it inside a component that is on every page, like your footer. The same plan rule applies to Code Embed.
Yes, for the Pixel you connect. Paste your Pixel ID into the banner and remove the old Pixel code, and the banner loads the Pixel only once a visitor allows Marketing. Before that, nothing reaches Meta. A visitor who allows only Analytics never gets the Pixel.
Meta ads and the cookie notice →If an app adds the Pixel and you would rather keep it, choose "Already on my site" and paste the banner's head code at the very top of Head code, above the Pixel. The Pixel then waits for the visitor's answer.
Meta's Business Tools Terms ask for a clear and prominent notice on every page where the Pixel runs. The banner shows on every page with a link to your privacy policy.
Yes. All four signals (analytics_storage, ad_storage, ad_user_data and ad_personalization) start at denied and follow the visitor's choice. You pick how, per tool.
How Consent Mode v2 works with it →Paste your G-, AW- or GTM- ID and remove the old tag. Google's tag loads only after a yes, with Consent Mode already set.
Keep your Google tag and paste the head code above it, at the top of Webflow's Head code. Google's tags load with every signal denied and update on the choice.
Webflow's own Google Analytics field has no consent setting, so for basic mode, move the G- ID from there into the banner.
Yes. Set any Webflow link's URL to #embedra-cookie-settings (a "Cookie settings" link in your footer is the usual place) and it reopens the banner with the visitor's current choice. Or switch on the banner's own Cookie settings button. Turning something off reloads the page once so the tools stop.
Hold Google Analytics, Google Ads, Tag Manager, Microsoft Clarity, the Meta Pixel, the TikTok Pixel, the LinkedIn Insight Tag and the ChatGPT Ads pixel until a yes.
Send Google Consent Mode v2, basic or advanced.
Keep Analytics and Marketing apart, so an Analytics-only yes never runs your ads.
Let visitors reopen it from a Cookie settings link or button.
Set no cookies of its own, and send nothing to Embedra.
Scan your Webflow site or block scripts you did not connect. Anything else can wait for a yes if you wrap it in the banner's browser event.
Pass the choice to Webflow Analyze or Optimize. If you use those, Webflow's consent settings for them still apply.
Keep a central record of each choice. The answer stays in the visitor's browser.
Work on a free Webflow Starter site, which cannot run custom code.
Make your site compliant with POPIA, GDPR or any other law on its own.
Free covers 500 views a month: a view each time the banner loads, with a visitor counted once every 30 minutes. Past 500 the banner keeps working, until it reaches twice that or 7 days have passed, and then it pauses. A paused banner shows nothing and loads nothing: tools Embedra loads stay off, and tools held by the head code stay held. It never switches tracking on without asking. The one exception is a Clarity app with no head code, which records again. You get an email when it reaches 500, and Starter, at $7 a month, gives 15,000 views with no badge.
Most popular
75,000 monthly views
Any 10 widgets
Unlimited domains
Custom CSS / JS
5 projects
No badge
We would rather you pick the right tool. Each of these is the better choice in some cases.
A Webflow app; Webflow's help names it. Free on .webflow.io staging; a paid plan for your own domain: $12 a month, or $199 once, per site. The better pick when you want it built in the Webflow canvas, an automatic site scan, automatic script blocking, consent records, or Webflow Analyze and Optimize handled.
Consent Pro pricing →A consent platform you paste into Webflow's Head code. Free: 5,000 pageviews a month, with CookieYes branding; Basic $10 a month or $100 a year, per domain. The better pick when you need more free traffic, a cookie scan, automatic blocking or a consent log.
CookieYes pricing →A consent platform Webflow's help names. Free plan: not checked. The better pick when you already use DataGrail.
Webflow's consent help →Webflow's tutorial: a designed banner, interactions and a footer script. Free, on a plan with custom code. The better pick when you only run the Meta Pixel and want full control.
Webflow's tutorial →Checked on 5 November 2026 on each company's own site. Prices change; tell us if one has: support@embedra.io
No. Webflow's consent tools cover only its own Analyze and Optimize products. For a banner it points to Marketplace apps, an existing consent platform or custom code.
For any banner added with code, yes: Webflow allows custom code and Code Embed only with an active Site plan or a Core, Growth, Agency or Freelancer Workspace.
Yes, on the Free plan: one banner and 500 views a month, every tracking tool and Consent Mode v2 included, with a small Embedra badge. Paid plans start at $7 a month and remove the badge.
The Pixel you connect, yes: it loads only after a visitor allows Marketing. It does not scan for other copies, so remove the Pixel from Webflow's Apps & Integrations and your custom code.
Site settings, Custom code, Footer code, then publish. Or use "Copy for Webflow" and paste the Code Embed into your footer component.
Add a link with the URL #embedra-cookie-settings, or switch on the banner's Cookie settings button. Either reopens the banner.