Log in Get early access
Free scan Install guides Developers Compare CMPs About Support Contact
Get Velo

Already have an account? Log in

Webflow install guide

Add Velo to Webflow.

Install the Velo cookie banner and Google Consent Mode v2 on Webflow in minutes. One line in the Head code field does it. If you already run Google Tag Manager, that route is on this page too.

Get started All install guides
WhereCustom code → Head code
PlanAny paid Webflow site plan
Goes liveOn publish
TimeAbout three minutes

Paste one line
into Head code.

One line in Webflow, and the banner is on every page with the Consent Mode default set before any other tag can fire. Same banner, same wiring and the same audit log as the Tag Manager route.

Already running Google Tag Manager? Take that route instead ↓

Three steps · about three minutes

  1. 01

    Copy the line

    One script tag, the same on every page of the site. Everything below is about getting it into the right place, and that place is always the head, ahead of the tags it governs.

    <!-- Before your other tags. That order is the point. --> <script src="https://veloconsent.com/v1/velo.js" data-velo-site="your-site-id" defer></script>
  2. 02

    Open Site settings → Custom code

    In the Designer, open the site menu top left → Site settings → the Custom code tab. Paste the snippet into the Head code field, which fits well inside Webflow’s 10,000 character limit, and hit Save. Custom code needs a paid Webflow site plan and applies to every page; a single page can carry its own head code in its page settings instead.

    webflow.com · Site settings
    The Webflow admin with the Velo snippet pasted into the site head
  3. 03

    Publish the site

    Custom code only reaches the site on publish: click Publish top right, select your domains, and reload the published site. The Designer preview never runs custom code, so always check the live URL (the webflow.io staging domain works too). The banner renders and the Consent Mode default is in place before any other tag can fire.

    your-site.com
    An ordinary web page with the Velo consent banner in the bottom left corner
One thing to watch

The Designer preview never runs custom code, so always check the published URL — the webflow.io staging domain works for that too. The snippet fits well inside Webflow's 10,000 character limit.

Recommended if you run a container

Or import the tag
in Tag Manager.

One tag, no code on the page, and your whole measurement stack stays in one place. No Tag Manager on the project yet? Paste the GTM container into the same Head code box in Site settings, publish, then start here.

  1. 01Import the Velo CMP templateTemplates→Tag Templates→New→Import
  2. 02Create the tagTags→New→Velo CMP template
  3. 03Tick the two recovery optionsAdvanced→url_passthrough→ads_data_redaction
  4. 04Fire it on Consent Initialization – All PagesTriggering→Consent Initialization – All Pages
  5. 05Turn on consent overview under AdminAdmin→Container Settings→Enable consent overview
  6. 06Preview, then publishPreview→Submit→Publish
tagmanager.google.com
A new tag in Google Tag Manager using the Velo Consent Banner template, site ID filled in
The Tag Manager guide, screen by screen Six screens, about ten minutes, the same on every platform.

Webflow questions,
answered.

What teams installing on Webflow ask first.

Does this work on the free plan?

Custom code, including any consent tool and Google Tag Manager itself, needs a paid Webflow site plan. Once the site has one, either method on this page takes a couple of minutes.

Can I test on the webflow.io staging domain?

Yes. The Head code publishes to your staging domain too, so you can watch the banner and the consent defaults there before connecting the production domain.

I already have a CMP embed in my project.

Remove the old embed before publishing Velo. Two banners confuse visitors, and two tools writing Consent Mode defaults send Google conflicting signals. Velo takes over the whole job in one tag.

Will it slow the site down?

No. The script loads deferred, never blocks rendering, and the visitor's region is resolved at the nearest edge before the page finishes painting. The banner itself is a few kilobytes of static code.

Can an AI assistant do this for me?

Yes. Copy the prompt in Install with agents, just below, into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries the steps on this page, the order the tags have to load in, and the checks the agent has to run before it tells you the job is done.

Or hand it
to an agent.

Copy the prompt into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries everything on this page: both routes, the order the tags have to load in, and the checks that prove it worked.

The prompt

Paste it in as your first message, then swap your-site-id for the ID on your Velo dashboard. Everything else the agent needs is already written into it, including what to check before publishing.

Install prompt · Webflow
# Install Velo on Webflow: cookie banner + Google Consent Mode v2 You are installing Velo, a consent management platform, on my Webflow site. Velo shows the cookie banner, sets the Google Consent Mode v2 defaults before any other tag can fire, and records every decision. Ask me for these before you touch anything: - My Velo site id. It is in the Velo dashboard. No account yet? Send me to https://veloconsent.com/get-started and wait for the id. - Whether the site already runs Google Tag Manager, and which container. - Which cookie banner or consent tool is live on the site today. ## Path A: through Google Tag Manager (preferred when GTM is live) 1. Templates → Tag Templates → New, then ⋮ → Import. Import the template.tpl from github.com/ampliodata/velo-cmp ("Velo CMP"). 2. Create a tag from that template. Set my Velo site id and pick the light or dark theme. 3. Fire it on the "Consent Initialization – All Pages" trigger. Not Initialization, not All Pages. Both run too late to set consent defaults. 4. Preview, check the Consent tab in Tag Assistant, then Submit and Publish. No container yet? On Webflow, open Site settings → Custom code (a paid Site plan is required) and paste the GTM head and body snippets into Head Code and Footer Code, then publish. ## Path B: the snippet, straight into the site Put this line in the <head>, above every analytics and advertising tag: <script src="https://veloconsent.com/v1/velo.js" data-velo-site="MY_SITE_ID" defer></script> On Webflow: Site settings → Custom code → the Head code field → Save, then publish the site. Custom code needs a paid Site plan and applies to every page; a single page can carry its own head code in its page settings instead. ## Rules - One path, never both. Two installs means two banners. - Velo loads first. Everything that measures or advertises comes after. - Only one tool may set Consent Mode defaults. If a CMP embed is already in the project, remove it before publishing Velo. Leave no hard coded gtag('consent', 'default', ...) anywhere else either. - Change nothing beyond what this install needs. Tell me first if a theme file, plugin or existing tag has to be touched. ## Verify, then report back - The banner renders on a fresh load in a private window. - Before I choose, every consent signal except security_storage is denied from an EEA, UK or Swiss location. - Accepting and rejecting each flip the matching signals, and a velo_consent_update event lands in the data layer. - Google tags stay in their cookieless mode until consent is granted, and any tag gated by hand fires only after it. - window.Velo is defined, and Velo.open() reopens the preferences panel. - On a Tag Manager install, Tag Assistant shows the Velo tag firing on Consent Initialization ahead of every other tag. Tell me what you changed, where you changed it, and what each check showed. If a check fails, fix it and run the checks again. Full guide: https://veloconsent.com/webflow More context for agents: https://veloconsent.com/llms.txt

Working with an agent that reads the web? Point it at veloconsent.com/llms.txt and /install.md for the same context in plain text.

From the journal.

What consent modelling is, and when Google actually switches it on Consent modelling estimates what declined visitors did. 11 August 2026
GDPR cookie banner requirements in 2026, and the check that proves each one The things a GDPR cookie banner must do in 2026, each paired with the browser check that proves your own banner actually does it. 29 July 2026
How to check your cookie banner is sending the Consent Mode v2 signal Two reads settle it: the four consent signals inside the browser, and the state that actually reached Google on the request. 26 July 2026
All posts

Your banner, your consent,
your data — all in one place.

Scan your site →
Pages Free scan Product Agencies Pricing Developers Install guides Compare CMPs
Company About Velo Blog Help Contact
Account Sign up Log in Get early access
GDPR CCPA
All rights reserved
© 2026 by Amplio Data
Privacy Cookies Terms Refunds GDPR TCF Legal notice
EN ES FR PT