The cookie banner
built for BigCommerce.
Manage consent on BigCommerce with Velo. Bring your banner, consent records, scan findings and AI cookie categorisation into one workspace.
Free for one site and 1,500 monthly sessions. Pro from €7 a month, plus VAT, for unlimited sites.
What Velo does
on BigCommerce.
Create one script in Script Manager on the Essential category so it loads before consent is given. That placement is what lets Velo set the denied default ahead of your other scripts. Or install through Google Tag Manager and keep everything in the container.
BigCommerce · Script Manager
- Open
- Storefront → Script Manager → Create a Script
- Location
- Head
- Pages
- All pages
- Type
- Script
- Consent category
- Essential
Configuration reference checked against the platform documentation. This is not an admin screenshot.
Platform documentation ↗How it goes live
on BigCommerce.
Three steps. Most installs take a few minutes when you can already publish changes to the site.
-
01
Create the script
In BigCommerce, open Script Manager and add the Velo snippet as an Essential script in the head. Or add the Velo template in Google Tag Manager.
BigCommerce · Script Manager
- Open
- Storefront → Script Manager → Create a Script
- Location
- Head
- Pages
- All pages
- Type
- Script
- Consent category
- Essential
Verified configuration reference · 23 September 2026 Configuration reference checked against the platform documentation. This is not an admin screenshot.
Platform documentation ↗ -
02
Denied by default, banner up
Velo sets the Google Consent Mode v2 defaults before your other tags run, denied where your region settings ask for opt in, then shows the banner. Google tags adjust to the choice and tags you gate on Velo's consent event wait for it. Every choice is saved to your consent records.
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 ↗ -
03
Verify, then publish
Check that the consent signals change in Tag Assistant when you accept and when you reject, then publish. Run the same check again whenever you change your tags or banner settings.
Using a different platform? See every supported platform.
BigCommerce questions,
answered.
What teams putting a banner on BigCommerce ask first.
Why does the script category matter in BigCommerce?
Script Manager sorts scripts into categories, and only Essential scripts load before the visitor consents. Velo must run first to set the denied default and show the banner, which is why the guide has you file it under Essential. It manages the consent for everything else.
Does this replace BigCommerce's own cookie consent tracking?
BigCommerce's built in consent banner covers basic notice. Velo replaces it with category level choices, region rules, an audit log and Consent Mode v2, the parts your ad platforms actually read.
How does it affect my Google Ads reporting?
You see fewer observed conversions from visitors who decline, because Google Ads tags adjust to each choice through Consent Mode v2. In advanced mode those visitors can still send cookieless pings, and Google may model some of the missing conversions when its eligibility and traffic conditions are met. That is not guaranteed.
Do I need a developer for the install?
Usually not. Both paths are settings work: one script in Script Manager, or one tag in Google Tag Manager. The install guide covers each step with screenshots.
From the journal.
Website privacy, in one place.
Scan your site →