# Webflow cookie consent: the tag that beats your banner

Webflow has no cookie banner of its own, and its Google Analytics setting loads above any banner you add. What we found on 121 Webflow sites, and the fix.

_Shaun Brown · October 19, 2026 · https://tagsentry.ai/blog/webflow-cookie-consent_

> **The short answer:** Webflow has no cookie banner of its own, so you add one from an app or with custom code, and its script has to run before any Google or Meta tag. Webflow's Google Analytics setting breaks that order: Webflow writes its tag into the page above everything in Head code. On all 25 Webflow sites where we could check, that tag set its cookie before anyone clicked. Move Google Analytics into Tag Manager, put your banner first, and test with Reject.

> **Not legal advice** This guide describes how Webflow loads code and what we measured on live sites. What your site needs depends on where your visitors are. Ask a lawyer if you need a definite answer.

## Webflow has no banner of its own

Webflow doesn't include a cookie banner. You pick one from Webflow's app marketplace (Consent Pro, DataGrail and others) or paste in a consent tool such as Cookiebot or CookieYes.

Webflow does have a tracking setting for its own analytics, Analyze and Optimize. Under **Insights › Settings › Tracking** you choose "Always track visitors", "Let visitors opt out" or "Don't track by default".

The last one keeps tracking "off for visitors, unless they explicitly opt in", Webflow says. With either of the last two "you'll need a consent management solution", or Analyze and Optimize "won't function properly".

That setting covers Analyze and Optimize and nothing else. Webflow's developer docs say its consent functions "apply only to Webflow Analyze and Optimize features". Google Analytics, Tag Manager, Meta and the rest need your banner.

## Where your banner's code goes

Your consent tool goes in **Site settings › Custom code › Head code**, as the first thing in the box, above Tag Manager and any pixel. Then publish. Head code needs a paid Site plan or a paid Workspace.

Order matters because a tag that runs before the banner has no idea a banner exists. Google says so about its own consent signals: "The order of the code here is vital. If your consent code is called out of order, consent defaults won't work."

The default has to come "before any commands that send measurement data (such as `config` or `event`)". If those signals are new to you, [Google Consent Mode v2, explained](/blog/google-consent-mode-v2-explained) covers each one.

## The Google Analytics setting loads first

Webflow can add Google Analytics for you. You paste a "G-" ID into **Site settings › Integrations › Google Analytics**, or connect it with the Google site tools app, and Webflow serves the tag through Google Tag Gateway, from your own domain.

Webflow writes that tag into the page itself, near the top of `<head>`. On every site we checked, it sat above everything the owner had pasted in Head code. The snippet ends with `gtag('config', 'G-...')`, the command that starts measuring, so it runs before any banner placed below it.

## What we found on 121 Webflow sites

On 19 October 2026 we took 12,500 random sites from the Tranco list of popular domains and kept the 121 built on Webflow. We read the order of tags in each page as served, then loaded it in a fresh browser.

If a banner showed, we pressed Reject, cleared tracking cookies and reloaded. It's the same script we used for our [GDPR banner test](/blog/gdpr-cookie-banner).

| What we saw | Sites |
|---|---|
| Webflow sites | 121 |
| A consent tool in the page | 55 |
| Using Webflow's Google Analytics setting | 28 |
| ...and a consent tool too | 10, with Webflow's tag above it on all 10 |
| ...with a Consent Mode default written into the page's HTML | 0 |
| Its own cookie (`_ga_` plus the ID) set before any click | 25 of the 25 we could read |
| ...on sites showing a banner | 8 of 8 |
| ...back again after Reject and a reload | 4 of 4 |

On the 39 banner sites without Webflow's setting, 19 tracked before a click (a request to a tracker, or a tracking cookie). That's about half, where the sites using Webflow's setting went eight for eight.

On those eight, Webflow's tag ran before the consent tool loaded, so the tool never had the chance to hold it. We visited from the US, where some tools wait for an opt-out by design, which is why the Reject results are the cleaner test.

## The fix: move Google Analytics into Tag Manager

1. In **Site settings › Integrations › Google Analytics**, delete your Measurement ID and save. If you connected through the Google site tools app, open it from the Apps panel, choose the cog, and disconnect Google Analytics there too. If you connected Tag Manager through the same app, disconnect it as well: on 3 of the sites we tested, a Tag Manager container loaded through the code Webflow writes at the top of `<head>`. Then paste Tag Manager's own snippet into Head code, below your consent tool.
2. Add Google Analytics in Tag Manager (a Google tag with the same "G-" ID), so it fires under your banner's rules. No Tag Manager? Paste Google's own gtag snippet into Head code, below your consent tool.
3. Check Head code: your consent tool first, then Tag Manager, then anything else.
4. Publish.

Your data stays in the same Google Analytics property, because the ID doesn't change. Google Tag Gateway goes with the Webflow setting, unless you set it up again yourself.

## Finsweet Cookie Consent is now Consent Pro

Search for Finsweet's cookie consent and you'll land on Consent Pro, whose site says "Finsweet Cookie Consent has been migrated to Consent Pro." It's a paid app built for Webflow, free on the staging domain, and it connects to Analyze and Optimize.

Seven of the sites we tested still ran the older version. Either one has to load above your tags, and Webflow's Google Analytics setting still loads above both.

## Check your own site

1. Open your published site in a private window, from a place where your banner shows.
2. Press **Reject** (or "Deny", "Necessary only").
3. Open developer tools (F12) › **Application** › **Cookies**, delete the `_ga` and `_ga_` cookies (leave the rest, so your Reject is kept), then reload.
4. If a cookie named `_ga`, or `_ga_` followed by your ID without the "G-", comes back after the reload, a Google tag ran without your visitor's yes.

[How to check Consent Mode v2 is working](/blog/check-consent-mode-v2-working) goes further, with the `gcs` and `gcd` values Google receives.

## Where TagSentry fits

TagSentry is one line, pasted first in Head code, above Tag Manager. Before any tag runs it sets every Consent Mode signal to denied. Where visitors can opt out, it switches tracking on moments after the page loads, unless they opted out.

Our Install screen reads your homepage and names any Google tag that loads before our line, such as Google Analytics. That includes the `gtag('config', 'G-...')` line Webflow's setting writes.

Running Cookiebot, CookieYes or OneTrust already? Keep it. Our line stands aside and watches your events for visitors who accept analytics there (CookieYes needs its Consent Mode option on). If you use Consent Pro or Finsweet's banner, turn it off before you add the line, so visitors see one banner.

Webflow steps are in the [install guide](/docs/install-by-platform), and [how consent works](/consent) covers the rules by country. Consent is free up to 10,000 page views a month.

## Sources

- [Webflow Help: Analyze & Optimize tracking settings](https://help.webflow.com/hc/en-us/articles/33620965657107)
- [Webflow Help: Manage site tracking consent](https://help.webflow.com/hc/en-us/articles/34272466616083)
- [Webflow Help: How do I connect my Webflow site to Google Analytics?](https://help.webflow.com/hc/en-us/articles/33961293143059)
- [Webflow Help: Connect Google site tools to your Webflow site](https://help.webflow.com/hc/en-us/articles/33961193954835)
- [Webflow Help: Custom code in head and body tags](https://help.webflow.com/hc/en-us/articles/33961357265299)
- [Webflow Developers: Site tracking and consent management](https://developers.webflow.com/browser/reference/consent-management)
- [Google for Developers: Set up consent mode on websites](https://developers.google.com/tag-platform/security/guides/consent)
- [Consent Pro (formerly Finsweet Cookie Consent)](https://consentpro.com/)
