Log in Get for free
Free scan 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 with the Velo Consent app (usable now at apps.veloconsent.com, coming soon to the Webflow Apps Marketplace). Most installs take a few minutes when you already have publish access to the site. Prefer not to use the app? You can paste one line in Head code or use Google Tag Manager instead.

Instructions and image sources reviewed 23 September 2026.

Open Velo Consent for Webflow Get started
WhereVelo Consent app · or Site settings → Custom code
PlanSite plan or eligible Workspace
Goes liveOn publish
Typical timeAbout two minutes

Install with the
Velo Consent app.

The Velo Consent app is usable now at apps.veloconsent.com and is coming soon to the Webflow Apps Marketplace. It adds one script to your site head through Webflow’s custom code API (no theme edits) and passes visitor choices to Webflow Analyze and Optimize. Prefer not to use the app? Paste one line in Head code or use Google Tag Manager instead.

Already using Google Tag Manager? Skip the app and do it there ↓

Four steps · about two minutes

  1. 01

    Authorise with Webflow

    Open apps.veloconsent.com (coming soon to the Webflow Apps Marketplace), click Authorise with Webflow, and select the Webflow site or workspace you want to connect.

    Open apps.veloconsent.com
  2. 02

    Connect to Velo

    Click Connect to Velo and sign in or create a free Velo account. Your Webflow site is linked automatically, with no site IDs to copy.

  3. 03

    Install banner script

    Click Install banner script. The app adds one script to your site head through Webflow’s custom code API, with no theme edits, and passes each visitor’s choice to Webflow Analyze and Optimize alongside Google Consent Mode v2.

  4. 04

    Publish the site and check the live banner

    Publish your site in Webflow to push the script live on your staging or production domain. Open the published URL in a private window to test accepting and rejecting, and confirm the site appears as installed in your Velo dashboard.

    Velo · live consent banner
    Live interface capture · 23 September 2026

    The real banner on veloconsent.com, captured on 23 September 2026. Your banner’s copy, layout and region settings may differ.

    Velo live site ↗View full size ↗
One thing to watch

Save changes and publish to the correct domains. Webflow can include custom code in preview, but the published URL is the final check. Test your webflow.io staging domain before production.

Still comparing options? Read why teams use Velo on Webflow, or see every supported platform.

Prefer not to use the app?
Paste one line into Head code.

Add your site’s snippet to the site-wide head in Site settings → Custom code, then publish and test the result.

Alternative · Head code

  1. 01

    Copy the line

    Copy the complete installation snippet for this site from your Velo dashboard. The example below shows the format; replace your-site-id before using it. Keep the API endpoint supplied by your dashboard.

    <script src="https://cdn.veloconsent.com/v1/velo.js" data-api="https://app.veloconsent.com" data-velo-site="your-site-id" async></script>
  2. 02

    Open Site settings → Custom code

    Paste your complete Velo snippet into Head code and save changes. Custom code requires an active Site plan or an eligible paid Workspace plan. Publish to the domains you want to update.

    Webflow · site-wide custom code

    Open
    Site settings → Custom code
    Paste
    Head code
    Save
    Save changes
    Go live
    Publish the site
    Verified configuration reference · 23 September 2026

    Configuration reference checked against the platform documentation. This is not an admin screenshot.

    Platform documentation ↗
  3. 03

    Publish and check the live site

    Save and publish the change using the platform steps above, then clear any site or CDN cache. Open the published URL in a fresh browser session. Check the banner where your region rules require it, test accepting and rejecting, and verify consent defaults and updates before your measurement tags run. Confirm the site appears as installed in your Velo dashboard.

Easiest if you use Tag Manager

Use Tag Manager?
Skip the code.

If Google Tag Manager is already on your site, this is the easiest way to add Velo. There’s no code to touch, it takes four short steps, and all your tags stay in one place.

  1. 01

    Add Velo to Tag Manager

    Open the Velo template, click Add to workspace, then pick your container.

    Open the Velo template ↗
  2. 02

    Paste your site ID

    In Tag Manager, open Tags and click New. Click Tag Configuration, choose Velo CMP and paste your site ID. You’ll find it in your Velo dashboard. Leave everything else as it is.

  3. 03

    Make it load first

    Click Triggering, choose Consent Initialization – All Pages, then click Save. This lets Velo start before your other tags.

  4. 04

    Publish and check it

    Click Submit, then Publish. Preview alone doesn’t put Velo live. Then open your site in a private window, try the banner, and check that it shows as installed in your Velo dashboard.

The complete Tag Manager guide Covers testing in Preview and the optional settings. No Tag Manager on this site yet? Use the steps above.

Webflow questions,
answered.

What teams installing on Webflow ask first.

Do I need the Webflow app, or can I use Custom code?

Either works. The Velo Consent app (usable now at apps.veloconsent.com and coming soon to the Webflow Apps Marketplace) is the fastest option: it adds one script to your site head through Webflow’s custom code API with no theme edits, and passes choices to Webflow Analyze and Optimize. If you prefer not to use the app, paste the snippet into Site settings → Custom code → Head code or install through Google Tag Manager.

Does this work on the free plan?

Adding scripts to the site head, whether through the Velo Consent app or the Custom code tab, requires an active Site plan or a Core, Growth, Agency or Freelancer Workspace plan. You can test on your webflow.io staging domain before connecting your 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?

The dashboard snippet loads asynchronously. As with any script, measure its effect on your site and check your tag order; asynchronous loading alone does not guarantee consent defaults run before other tags.

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 this prompt into your assistant, then provide your site ID and the complete installation snippet or GTM settings from your Velo dashboard.

Install prompt · Webflow
Install Velo on Webflow. Current guide: https://veloconsent.com/webflow Before editing, get my site ID and complete installation snippet or GTM settings from the Velo dashboard. Confirm which consent tool and measurement tags already run on the site. Choose one installation route: A. If the site already uses Google Tag Manager, add the Velo CMP template (published by ampliodata) from the Community Template Gallery. Set my site ID, theme and API endpoint from the dashboard. Review the advanced options; both default to off. Use Consent Initialization – All Pages, then Preview and verify consent before publishing. Full steps: https://veloconsent.com/google-tag-manager B. For direct installation: Paste your complete Velo snippet into Head code and save changes. Custom code requires an active Site plan or an eligible paid Workspace plan. Publish to the domains you want to update. Preserve unrelated code. Avoid duplicate Velo installs or competing consent defaults. Do not assume a head placement or async loading alone guarantees tag order. Check the published site in a fresh session. Verify the banner under the configured region rules, initial consent defaults, accept/reject updates and the velo_consent_update event. Check that non-Google tags follow their assigned categories. Test a second page and any separate checkout surface. Confirm signals reach the Velo dashboard. Report what changed, where it changed and the result of each check. Describe any missing access or checks you could not complete.

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.

Google Consent Mode v2 in Velo: what is new Consent Mode v2 is on from the first install, the banner meets Google’s requirements, scans check every page and email you about gaps, and support comes first. 2 November 2026
How to add a cookie banner to a Webflow site Paste the banner in Site settings Custom code above your container, then clear Webflow's native Analytics and Pixel fields, which load outside your tag manager. 4 September 2026
How to set up Google Consent Mode v2 on Shopify Set denied defaults above your container, then write the visitor's choice to both Google Consent Mode and Shopify's Customer Privacy API on the same click. 2 September 2026
All posts

Website privacy, in one place.

Scan your site → Available on Shopify App Store
Pages Free scan Product Platforms Agencies Pricing Free cookie banner Chrome extension
Company About Velo Blog Help Contact
Account Sign up Log in Get Velo
Regulations GDPR UK GDPR CCPA / CPRA US state laws LGPD Ley 1581 (Colombia) Ley 25.326 (Argentina) Ley 29733 (Peru)
All rights reserved
© 2026 by Amplio Data
Privacy Cookies Terms Refunds GDPR TCF Legal notice