The cookie banner
built for BigCommerce.
Your BigCommerce store runs on paid traffic, and consent quietly taxes it: every declined visitor is a purchase your ads can no longer claim. Velo keeps the store compliant across the EU, UK and US and wires Google Consent Mode v2 so those purchases are modelled instead of gone.
Live in minutes — one tag through Google Tag Manager, or one line in Script Manager.
Compliant. Fast.
Nothing Lost.
Compliant by default
Region rules apply the right law by location — GDPR consent in the EU and UK, opt out where US states require it. Equal Accept and Reject, per category choices, and every consent recorded in an exportable audit log.
Consent Mode v2, wired right
The denied default lands before any tag fires — the step most installs get wrong. Declined visitors send cookieless pings, and Google models the conversions consent hides instead of dropping them.
Made for 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.
Three steps
on BigCommerce.
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.
Denied by default, banner up
Velo sets the Consent Mode v2 denied default before any other tag runs, then shows the banner. Nothing non essential fires until the visitor chooses, and every choice lands in the audit log.
Verify and forget it
Check the consent signals flip in Tag Assistant or your browser, publish, and you are done. Region rules, records and Google's modelling run on their own from here.
Real Results.
Not Promises.
+37%
Average ROAS lift
Reported across paid channels once consent signal is restored and modelled the compliant way.
20–40%
Conversions recovered
Won back through Consent Mode v2 and server side tagging, so reporting reflects revenue that was already happening.
34%
Sessions brought back
Otherwise hidden by consent, brought back into view, so the data you pay for actually shows up.
Measured ranges across Amplio Data client implementations, not a guarantee.
Questions,
answered.
What BigCommerce teams ask before switching consent on.
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 — that 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?
With Consent Mode v2 in place, declined visitors send cookieless pings and Google models the conversions you cannot observe. Across Amplio Data client implementations that recovers 20–40% of consent hidden conversions — measured ranges, not a guarantee.
Do I need a developer for the install?
No. 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.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on BigCommerce in minutes,
and the conversions consent hides, modelled back.