Cookie consent for Webflow: install Cookifi in under 10 minutes

Webflow gives you wf.allowUserTracking and nothing else — no banner, no categories, no Consent Mode, no consent log. Cookifi is one paste into site-wide Head code and a publish.

What you need

A paid Site plan (any tier) or a paid Workspace. Free Starter sites on .webflow.io cannot add site-wide custom code at all.

Install Cookifi on Webflow

  1. 1

    Open the site's custom code

    Site settings (the gear icon) → Custom code. Page settings have their own custom-code fields, but those apply to one page only.

  2. 2

    Paste into Head code

    Paste the Cookifi integration script into the 'Head code' box. The field takes up to 50,000 characters, so there is no need to shorten anything.

  3. 3

    Save and publish

    Save changes, then publish. Custom code is not live until the site is published, and staging (.webflow.io) and your custom domain publish separately.

Get your Cookifi script

  1. 1.

    In the Cookifi admin click Add, enter a name and your domain — a sitemap URL is optional — and click Create.

  2. 2.

    Open the property and copy the script under General → Integration script.

  3. 3.

    Click the Google icon in the script toolbar to include the Consent Mode default command. The defaults themselves are set under Regions, together with URL Passthrough and Ads Data Redaction.

  4. 4.

    Paste it as high in the <head> as the platform allows, on every page. Save, reload, and confirm the banner appears.

  5. 5.

    If the platform strips data- attributes and the banner does not load, switch to Query string mode in the Installation script section and copy the script again.

  6. 6.

    Cannot touch the head at all? Use the GTM Installation script in a Custom HTML tag with the Consent Initialization – All Pages trigger. Direct installation is still the recommendation, because ad blockers can suppress GTM.

Consent Mode v2 and GTM on Webflow

Webflow's GA4 and GTM integrations under Site settings → Integrations load their tags unconditionally, so Cookifi in Head code has to set the Consent Mode defaults before them — or remove the native GA integration and load GA through GTM under Cookifi. If you use Analyze or Optimize, set their tracking default to opt-out and have Cookifi call wf.allowUserTracking() when the visitor consents.

What the native Webflow banner cannot do

Webflow ships no cookie banner of its own, so until you add a CMP nothing asks for consent and nothing holds a tag back.

Gotchas worth knowing

  • Page settings → Custom code applies to a single page. Site-wide code belongs in Site settings, or the banner is missing everywhere else.
  • Head code runs before Webflow loads jQuery, so anything that needs $ has to go in Footer code. The Cookifi script needs neither.
  • Publishing to .webflow.io does not publish your custom domain — check the domain you actually tested.

What you get with Cookifi

Live in under 10 minutes

One script in the head, a scan that suggests the categories for you, and a 14-day trial that needs no card.

A flat base, not a tier ladder

One monthly base from €10 plus usage on read events — the first 10,000 each month are free. Subdomains and team members are unlimited, so a second site is not a second plan.

Support that answers

Live chat and email on every plan, with a human response within one business day on Enterprise. We are a small team, which is why the things customers ask for tend to ship quickly.

Built for the modern stack

Google and Microsoft Consent Mode v2 are first-class, GA4 and GTM are the default path, and Cookifi is a Google-certified CMP partner.

Frequently asked questions

Does Webflow not have its own cookie banner?

No. It exposes a consent API (wf.allowUserTracking / denyUserTracking) that gates its own Analyze and Optimize tracking. There is no banner, no category model, no Consent Mode signalling and no consent log.

Can I install it on a free Webflow site?

No. Site-wide custom code requires a paid Site plan or a paid Workspace, which is a Webflow restriction rather than a Cookifi one.

Should I keep the native GA4 integration?

Only if Cookifi's defaults load first, which they do when the script sits in Head code. The cleaner setup is to remove the native integration and load GA through GTM, so one system controls the firing order.

Sources

Every fact on this page comes from the pages linked below. Spotted something out of date? Tell us and we will correct it.

Last reviewed November 2, 2026

All platform guides

Try it on your own site

14 days, no credit card. If the install takes you longer than ten minutes, tell us — on our side that counts as a bug.