Velo on
your platform.
Each platform has two pages. The platform page covers what Velo does on that site builder or store. The install guide walks through every step, from pasting the snippet to checking that it works.
Pick your
platform.
Velo needs one line in the page head, or one tag in Google Tag Manager, instead of a plugin inside your CMS. What changes between platforms is where that line goes.
WordPress
Install the Velo Consent plugin under Settings → Velo Consent, or paste one line in your site header. Works on any WordPress install.
Shopify
One line in theme.liquid, under Themes → Edit code. Any Shopify plan, no app needed.
Webflow
Install the Velo Consent app at apps.veloconsent.com (coming soon to the Webflow Apps Marketplace), or paste one line in Site settings → Custom code.
Wix
Velo Consent: Cookie Banner is on the Wix App Market. Or install with one line in Settings → Custom code → Head, or through Google Tag Manager.
Squarespace
One line in the Header field, under Website Tools → Code Injection. Core plan or above.
Framer
One line in the Start of head slot, under Site settings → General → Custom Code. Paid plans, Mini and up.
HubSpot
One line in Site header HTML, under Settings → Website → Pages. Any plan with a connected domain.
Drupal
One line in html.html.twig, or through the Asset Injector module. Drupal 9, 10 and 11.
Square Online
One line in Settings → Tracking Tools → Head. Any paid Square Online plan.
BigCommerce
One script in Storefront → Script Manager, in the Essential category. Any BigCommerce plan.
Duda
One line in Settings → Head HTML, and every page inherits it. Works on any Duda site.
Shopware
One line in the base_head block of storefront/base.html.twig. Shopware 6.
PrestaShop
One line in your child theme's templates/_partials/head.tpl. PrestaShop 1.7, 8 and 9.
Astro
One line in the layout every page shares. Static or server rendered, with or without ClientRouter.
Next.js
One line in your root layout, or in pages/_document.tsx. App Router and Pages Router.
Google Tag Manager
Import the Velo CMP template from the Community Template Gallery and fire it on the Consent Initialization trigger. No code on the page, on any site that already runs a Tag Manager container.
Which route
fits your site?
Snippet or Tag Manager, and what to do when your platform is missing.
Should I use the snippet or Google Tag Manager?
If your site already runs Google Tag Manager, use the Velo template on the Consent Initialization trigger, so the consent defaults are set before your other tags fire. If it does not, paste the snippet into the page head, above your analytics and advertising tags. Both routes load the same banner.
Can I install Velo both ways?
No. Pick one route. Two installs mean two banners, and two sources of Consent Mode defaults send Google conflicting signals. If you move to Tag Manager later, remove the snippet when you publish the tag.
My platform is not listed. Can I still use Velo?
Yes, if you can add a script to the head of every page, or your site runs Google Tag Manager. Follow the general setup in Get started, then test accept, reject and preference changes on the live site.
