Add Velo
to BigCommerce.
Install the Velo cookie banner and Google Consent Mode v2 on BigCommerce with one line in a Script Manager entry. Most installs take a few minutes when you already have admin access to the site. If you run Google Tag Manager, that route is on this page too.
Instructions and image sources reviewed 23 September 2026.
One script, category
Essential.
Add your site’s snippet to the site-wide head, then publish and test the result. If your measurement tags already run through Google Tag Manager, use the route below.
Already running Google Tag Manager? Take that route instead ↓
Three steps · about three minutes
-
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> -
02
Create a Script Manager entry
Open Storefront → Script Manager → Create a Script. Name it Velo, choose Head, All pages, Essential and Script, then paste the complete snippet and save. Script Manager supports Stencil and Catalyst storefronts; it is not a Blueprint installation method.
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 ↗ -
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.
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 ↗
Use Essential so the consent tool itself can load before a decision. Other tags still need their own consent configuration. Checkout coverage depends on your checkout type and permissions; verify it separately.
Still comparing options? Read why teams use Velo on BigCommerce, or see every supported platform.
Or add the tag
in Tag Manager.
Already have a Google Tag Manager web container on this site? Add Velo from the Community Template Gallery and configure it there. If you need to install the container first, use your platform’s supported integration and check it on the published URL.
- 01Add the Velo CMP templateTemplates→Tag Templates→New→Search Gallery
- 02Create the tagTags→New→Velo CMP template
- 03Review the advanced optionsAdvanced→url_passthrough→ads_data_redaction
- 04Fire it on Consent Initialization – All PagesTriggering→Consent Initialization – All Pages
- 05Enable the consent overviewAdmin→Container Settings→Enable consent overview
- 06Preview, then publishPreview→Submit→Publish
Velo CMP · tag configuration
- Velo site ID
- Copy the exact site ID from your Velo dashboard.
- Banner theme
- Light or Dark
- Velo API endpoint (optional)
- Use the API endpoint shown in your Velo installation settings.
Field names checked against the published Velo CMP template. Use your own site ID and API endpoint.
Velo CMP template ↗BigCommerce questions,
answered.
What teams installing on BigCommerce ask first.
Does it cover the checkout?
All pages can include checkout and order confirmation on supported configurations. Availability depends on the checkout type, Script Manager support and permissions; test those pages separately.
BigCommerce has its own cookie consent banner.
Switch it off so Velo is the only banner your visitors see. Two banners confuse people, and only Velo wires the decision into Consent Mode v2, the region rules and the audit log.
I already load a CMP through Script Manager.
Delete or disable that script before saving Velo. Two consent tools writing Consent Mode defaults send Google conflicting signals. One layer, one source of truth.
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.
Paste this prompt into your assistant, then provide your site ID and the complete installation snippet or GTM settings from your Velo dashboard.
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.
Website privacy, in one place.
Scan your site →