# Velo

> Velo is a consent management platform built by the data engineers at Amplio Data. It keeps websites compliant with GDPR, CCPA and Google Consent Mode v2 while recovering the analytics and advertising signal that cookie banners normally cost. One snippet, any stack, one dashboard across every client site.

Stay compliant. Recover the signal. Velo pairs a fast, fair consent banner (≤30KB, Shadow DOM, GTM native) with Consent Mode v2 and server side tagging wired the way Google expects, so the 20–40% of conversions consent typically hides can be modelled and counted again. Figures are measured ranges across Amplio Data client implementations, not a guarantee. You can create an account now at https://app.veloconsent.com/signup; general availability is 2026-08-20.

Velo is a product and brand of AmplioData OÜ. It is not affiliated with Velo by Wix, or with any other product of the same name.

## What Velo does

A visitor lands on a site running Velo. Before any tag fires, the banner asks what they allow, in the language and under the rules of the region they are in. Their answer is written to Google Consent Mode v2 as the four signals Google expects, so tags that may not run simply do not run, and the conversions consent hides get modelled back into Google Ads and GA4 instead of disappearing. Every choice is recorded in an exportable audit log.

Three things separate it from a banner that only paints a box:

- Consent Mode v2 advanced is wired on every plan, not sold as an upgrade. Basic mode drops the declined conversion; advanced models it.
- The consent signal is carried through to server side tagging, so a first party container honours the same choice the browser made.
- A cookie and tracker scan runs at onboarding and, on paid plans, monthly, so the vendor list on the banner matches what the site actually loads.

## Who Velo is for

- Advertisers running Google Ads and GA4 in the EEA and UK, who can see conversions falling away after a banner goes live.
- Agencies rolling consent out across a client roster, who need white label branding, per client domains and one dashboard over the portfolio.
- Developers and analytics engineers who want one script tag or one Google Tag Manager template rather than a platform migration.

## Pricing

Billed per workspace, VAT excluded, switch or cancel at any time. Prices on the pricing page are illustrative for this preview.

- Free — €0/month. A single site getting compliant. Up to 1,500 monthly sessions, 1 domain, one user, Consent Mode v2 advanced, one cookie and tracker scan at onboarding.
- Pro — from €7/month, scaling with monthly sessions (€7 at 3K, €39 at 50K, €199 at 250K, €459 above 1M). Up to 3 domains. Everything in Free, plus banner design and branding, automated monthly scans plus manual scans on demand, a consent dashboard with the full consent log and CSV export, and email support.
- Server — custom, on request. Server side work scoped and delivered by our data team rather than sold self serve. Everything in Pro, plus unlimited sessions and domains, team seats for the whole workspace, server side tagging scoped as a project, and priority support.

You pick the monthly sessions you need and change tier whenever you want; we tell you as you approach your allowance rather than moving you between tiers automatically.

## Capabilities

- Cookie consent banner: ≤30KB, Shadow DOM so it cannot inherit or break site CSS, keyboard accessible, reject in one click.
- Google Consent Mode v2: denied defaults on Consent Initialization, url_passthrough and ads_data_redaction, advanced mode on every plan.
- Region rules: EU and UK opt in, US opt out including Global Privacy Control, configured per region rather than per site.
- Conversion recovery: modelled conversions in Google Ads and GA4, and server side tagging for first party recovery beyond modelling.
- Vendor and cookie scanning: full scan at onboarding, automated monthly rescans on paid plans, manual scans on demand.
- Audit log: every consent record exportable, for a regulator or a client review.
- Agency features: white label branding, client domains, team seats, one dashboard across the portfolio, revenue share and referrals.
- Install paths: one script tag, a Google Tag Manager template, or the paste into any coding agent prompt at /install.md.
- IAB TCF: Velo is not yet a registered TCF CMP. TCF v2.3 support is in development; see /tcf for the current status.

## Key pages

- [Product](https://veloconsent.com/product): the consent layer end to end, for advertisers
- [Pricing](https://veloconsent.com/pricing): three plans, session and request based, with the questions teams ask before picking one
- [For agencies](https://veloconsent.com/agencies): white label, client domains, one dashboard per portfolio
- [For developers](https://veloconsent.com/developers): quick start, GTM template, API reference, status
- [Compare](https://veloconsent.com/compare): Velo against Usercentrics, Cookiebot, OneTrust, Didomi, CookieYes, iubenda, Axeptio and Termly, point for point
- [Free compliance scan](https://veloconsent.com/scan): check any site for trackers, a consent platform and Consent Mode v2 wiring
- [Get started](https://veloconsent.com/get-started): from empty account to live consent layer in five steps
- [Consent Mode v2](https://veloconsent.com/product#consent-mode): what Velo sends Google, and when
- [Cookie banner](https://veloconsent.com/product#cookie-banner): the banner itself, size, behaviour and design controls
- [Lost conversions](https://veloconsent.com/product#recovery): how the conversions consent hides get counted again
- [Install with Google Tag Manager](https://veloconsent.com/google-tag-manager): the GTM route, step by step
- [Agent install prompt](https://veloconsent.com/install.md): paste into any coding agent to install Velo
- [IAB TCF status](https://veloconsent.com/tcf): Velo is not yet a registered TCF CMP; TCF v2.3 support in development
- [Help centre](https://veloconsent.com/help): setup, migration and day to day answers
- [About](https://veloconsent.com/about): who built Velo and why
- [Contact](https://veloconsent.com/contact): talk to the team

## Platform pages

Cookie consent per technology. Each links to a step by step install guide.

- [Shopify](https://veloconsent.com/cookie-banner-for-shopify)
- [WordPress](https://veloconsent.com/cookie-banner-for-wordpress)
- [Wix](https://veloconsent.com/cookie-banner-for-wix): not affiliated with Velo by Wix
- [Webflow](https://veloconsent.com/cookie-banner-for-webflow)
- [Squarespace](https://veloconsent.com/cookie-banner-for-squarespace)
- [BigCommerce](https://veloconsent.com/cookie-banner-for-bigcommerce)
- [Shopware](https://veloconsent.com/cookie-banner-for-shopware)
- [Square Online](https://veloconsent.com/cookie-banner-for-square)
- [Duda](https://veloconsent.com/cookie-banner-for-duda): agency rollouts
- [Drupal](https://veloconsent.com/cookie-banner-for-drupal)
- [HubSpot](https://veloconsent.com/cookie-banner-for-hubspot)
- [Framer](https://veloconsent.com/cookie-banner-for-framer)
- [Consent Mode v2 in Google Tag Manager](https://veloconsent.com/consent-mode-for-google-tag-manager)

## Languages

The marketing site is published in English, Spanish and French. Every page listed above has a Spanish twin under /es and a French twin under /fr, linked to each other by reciprocal hreflang and listed with their alternates in sitemap.xml. Slugs are localised, so the Spanish pricing page is /es/precios and the French one is /fr/tarifs; platform names keep their slug in every language (/es/shopify). The three copies say the same thing — a claim that appears in one appears in all three, and the figures are identical.

- Spanish: https://veloconsent.com/es
- French: https://veloconsent.com/fr

Two deliberate exceptions. The blog and its posts are published in English only, so those URLs have no Spanish or French alternate — do not infer one from the pattern. And the translated copies of the legal pages (/es/terminos, /fr/conditions and the rest) are reading translations: the English version of each legal document is the operative one, and each translated page says so on its face.

The consent banner itself is separate from the site and speaks eight languages (English, Spanish, German, French, Italian, Dutch, Portuguese, Polish), resolved from the visitor's browser unless the embedding page pins one with data-velo-locale.

## Answer pages

Direct answers to the questions teams actually ask about consent and measurement, written from real client work. This section is regenerated from the published posts at every deploy (scripts/build-llms.ts).

<!-- answer-pages:start -->
- [How do you prove a visitor gave consent](https://veloconsent.com/blog/how-do-you-prove-a-visitor-gave-consent): You prove it with a consent record you can retrieve for one visitor on one date.
- [How much does a consent management platform cost in 2026](https://veloconsent.com/blog/how-much-does-a-consent-management-platform-cost): Most sites pay nothing to a few hundred a month, and monthly sessions decide where you land.
- [What is the TCF, and does your site need it](https://veloconsent.com/blog/what-is-the-tcf-and-does-your-site-need-it): The TCF is how the advertising supply chain records and passes consent.
- [GDPR cookie banner requirements in 2026, and the check that proves each one](https://veloconsent.com/blog/gdpr-cookie-banner-requirements-2026): The things a GDPR cookie banner must do in 2026, each paired with the browser check that proves your own banner actually does it.
- [Why Google Ads and GA4 report different conversion numbers](https://veloconsent.com/blog/why-google-ads-and-ga4-report-different-conversions): Google Ads and GA4 count different things, so a gap is normal.
- [How to pass the consent signal to a server side tagging container](https://veloconsent.com/blog/how-to-pass-consent-signal-server-side-tagging): Consent is decided in the web container and rides to the server on the request.
- [How to check your cookie banner is sending the Consent Mode v2 signal](https://veloconsent.com/blog/check-cookie-banner-consent-mode-v2-signal): Two reads settle it: the four consent signals inside the browser, and the state that actually reached Google on the request.
- [Can Google Analytics work without cookies](https://veloconsent.com/blog/can-google-analytics-work-without-cookies): Yes, but only in a narrower sense than the question implies.
- [Do you still need a cookie banner with server side tagging](https://veloconsent.com/blog/do-you-still-need-a-cookie-banner-with-server-side-tagging): Yes.
- [Why your GA4 traffic shows as Unassigned after adding a cookie banner](https://veloconsent.com/blog/ga4-unassigned-traffic-after-cookie-banner): Unassigned is traffic GA4 collected and could not attribute.
- [White label cookie consent for agencies: what actually matters](https://veloconsent.com/blog/white-label-cookie-consent-for-agencies): White labelling a cookie banner is the easy part.
- [What is Global Privacy Control, and do you have to honour it](https://veloconsent.com/blog/what-is-global-privacy-control): Global Privacy Control is a browser signal that says do not sell or share my data.
- [Do cookie banners slow down your website](https://veloconsent.com/blog/do-cookie-banners-slow-down-your-website): A cookie banner can slow your site, but the banner script is rarely the expensive part.
- [How to raise cookie consent accept rates without dark patterns](https://veloconsent.com/blog/raise-consent-accept-rates-without-dark-patterns): The honest levers that raise cookie consent accept rates: plain language, equal buttons, granular categories, a fast banner and a measured baseline.
- [Do you actually need a cookie banner on your website](https://veloconsent.com/blog/do-i-need-a-cookie-banner-on-my-website): When your website needs a cookie banner, when it does not, and the question the checklists skip: whether the banner quietly costs you analytics data.
- [What happens to your GA4 data when users reject cookies](https://veloconsent.com/blog/what-happens-to-ga4-data-when-users-reject-cookies): What GA4 keeps and what it loses when a visitor rejects cookies, why the answer depends on your Consent Mode, and the part of the gap modelling never fills.
- [What is a consent management platform (and when do you need one)](https://veloconsent.com/blog/what-is-a-consent-management-platform): A consent management platform captures what visitors allow, proves it, and passes that choice to your analytics and ad tags.
- [Basic vs advanced Consent Mode: which one are you running](https://veloconsent.com/blog/basic-vs-advanced-consent-mode-which-am-i-running): Deny consent in incognito and read the gcs parameter on Google's request.
- [How to install a cookie banner with Google Tag Manager](https://veloconsent.com/blog/install-cookie-banner-google-tag-manager): Install your consent banner as the first thing Tag Manager does, on the Consent Initialization trigger, defaulted to denied.
- [How to recover the conversions your cookie banner is costing you](https://veloconsent.com/blog/recover-conversions-lost-to-cookie-consent): When visitors reject cookies you lose the attribution, not the traffic, and most of it is recoverable.
- [Where 34% of your sessions actually go](https://veloconsent.com/blog/where-34-percent-of-sessions-go): A third of visitors sit behind the cookie banner and never reach your reports.
- [A plain English guide to Consent Mode v2](https://veloconsent.com/blog/consent-mode-v2-plain-english): What the four consent signals mean, why basic and advanced implementations are not the same thing, and how to tell which one your site is actually running.
- [Why your GA4 conversions dropped overnight](https://veloconsent.com/blog/ga4-conversions-dropped-overnight): A banner change, a tag that fires too early, a region rule that flipped.
- [Reject all should be one click, here is why](https://veloconsent.com/blog/reject-all-one-click): The banner design choice regulators keep flagging, what a fair banner looks like, and why a clearer first view tends to lift consent rates rather than lower them.
<!-- answer-pages:end -->

## Company

Velo is a product of AmplioData OÜ, trading as Velo and Amplio Data. Estonian Business Register code 17190588, VAT EE102836994, registered at Sepapaja tn 6, 15551 Tallinn, Estonia, operating from Barcelona, Spain. Amplio Data (https://www.ampliodata.io) is the analytics implementation company behind it, founded by Walter Masseroni Gonzalez.

## Contact

- Email: support@veloconsent.com
- Website: https://veloconsent.com
- Sign up: https://app.veloconsent.com/signup
- Parent company: https://www.ampliodata.io