The cookie banner
WordPress doesn't need
a plugin for.
Every WordPress plugin is one more thing to update, one more thing that can break the site. Velo installs like your analytics does: one line in the header, or one tag in Google Tag Manager. Compliant banner, Consent Mode v2, and no new row on your plugins screen.
Live in minutes — one tag through Google Tag Manager, or one line in your site header.
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 WordPress
Paste one line into your header — through your theme, or through the tag manager plugin you already run. It works on any theme and any builder, because it never touches PHP: it is the same script tag your other measurement uses.
Three steps
on WordPress.
Add the tag
In Google Tag Manager, add the Velo template from the community gallery. No GTM on the site? One line in your header does the same job.
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 WordPress teams ask before switching consent on.
Do I need to install a WordPress plugin?
No. Velo is one script tag. Add it through Google Tag Manager, your theme's header, or the header field of the SEO or tag plugin you already run. Nothing new to keep updated, nothing that can conflict with the rest of your stack.
Does it work with WooCommerce and page builders?
The banner is plain JavaScript in your site's head, so it renders on every page your theme serves — shop pages included. It does not depend on any particular builder, theme or checkout.
Is this enough for GDPR?
Velo blocks non essential tags until the visitor chooses, records the choice in an audit log, and applies the right rule set by region across the EU, UK and US. Equal Accept and Reject, no dark patterns.
Why does Consent Mode v2 matter for my site?
If you run Google Ads or GA4 in the EEA, Google requires it — and it is what lets Google model the conversions declined visitors would otherwise take with them. Across Amplio Data client implementations that recovers 20–40% of consent hidden conversions. Measured ranges, not a guarantee.
Works wherever you build
Consent handled.
Signal kept.
A compliant banner on WordPress in minutes,
and the conversions consent hides, modelled back.