WordPress
Install the Velo Consent plugin under Settings → Velo Consent, or paste one line in your site header. Works on any WordPress install.
Platforms
Each platform has two pages: one on what Velo does on that site builder or store, and an install guide that walks through every step, from pasting the snippet to checking that it works.
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.
Install the Velo Consent plugin under Settings → Velo Consent, or paste one line in your site header. Works on any WordPress install.
Install the Velo Consent app from the Shopify App Store, with no code to edit, or paste one line in theme.liquid under Themes → Edit code.
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.
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.
One line in the Header field, under Website Tools → Code Injection. Core plan or above.
One line in the Start of head slot, under Site settings → General → Custom Code. Paid plans, Mini and up.
One line in Site header HTML, under Settings → Website → Pages. Any plan with a connected domain.
One line in html.html.twig, or through the Asset Injector module. Drupal 9, 10 and 11.
One line in Settings → Tracking Tools → Head. Any paid Square Online plan.
One script in Storefront → Script Manager, in the Essential category. Any BigCommerce plan.
One line in Settings → Head HTML, and every page inherits it. Works on any Duda site.
One line in the base_head block of storefront/base.html.twig. Shopware 6.
One line in your child theme's templates/_partials/head.tpl. PrestaShop 1.7, 8 and 9.
One line in the layout every page shares. Static or server rendered, with or without ClientRouter.
One line in your root layout, or in pages/_document.tsx. App Router and Pages Router.
Import the Velo CMP template from the Community Template Gallery and fire it on the Consent Initialization trigger. It needs no code on the page and works on any site that already runs a Tag Manager container.
No platform matches that name. See what to do when yours is not listed.
WordPress has the Velo Consent plugin under Settings → Velo Consent, Wix has Velo Consent: Cookie Banner on the Wix App Market and Webflow has the Velo Consent app at apps.veloconsent.com.
What changes is where the line goes: a settings field on some platforms, the template every page shares on others.
Use the Velo template if your site already runs Google Tag Manager, and the snippet if it does not. Both routes load the same banner.
Paste the snippet into the page head, above your analytics and advertising tags. The install guide for your platform shows where that line goes.
Import the Velo CMP template from the Community Template Gallery and fire it on the Consent Initialization trigger. It needs no code on the page and works on any site that already runs a Tag Manager container. Consent Mode for Tag Manager · Tag Manager install guide
Pick one route. If you install both, you get two banners, and two sets of Consent Mode defaults send Google conflicting signals.
You can still use Velo if you can add a script to the head of every page, or your site runs Google Tag Manager.
Get startedThe general setup is in Get started. It applies to any site where you can add a script to the head of every page.
Paste the snippet into the page head, above your analytics and advertising tags. If the site already runs Google Tag Manager, use the Velo template on the Consent Initialization trigger instead, so the consent defaults are set before your other tags fire.
Test accept, reject and preference changes on the live site.
Why Velo sits outside your CMS, what it costs and the Tag Manager route in full.
One line in the page head, or one tag in Google Tag Manager, instead of a plugin inside your CMS.
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.
No. Pick one route. If you install both, you get two banners, and two sets of Consent Mode defaults send Google conflicting signals. If you move to Tag Manager later, remove the snippet when you publish the tag.
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.
Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.