Product

Your website privacy workspace

Manage your banner, cookies and consent records in one workspace, review what the scans find, and check how each visitor’s choice reaches your tags.

Built by the data team at Amplio Data.

Works with the platforms you build on

WordPressShopifyWebflowWixHubSpotPrestaShopDrupalBigCommerceShopwareNext.jsAstroSquare

Install it once and change the rest from your workspace

Add the Velo snippet or use Google Tag Manager, and check how consent behaves before you publish. After that, banner changes happen in your workspace.

From snippet to reports

  • Paste one snippet.
  • The banner goes live.
  • Signals reach your reports.

How it installs

  • One snippet. Paste it once and you’re done. After that you change the copy, colours, categories and regions from the dashboard, and the snippet itself stays the same.
  • Or through GTM. If you already run Tag Manager, the GTM guide adds the banner and makes your tags follow the consent state Velo publishes.
  • Guides for your platform. Step-by-step install guides for Shopify, WordPress, Webflow, Wix and nine more, each ending with a prompt you can give an AI assistant.
  • Light on your pages. The script is smaller than a single product photo and loads deferred, so it doesn’t hold up the page and your speed scores stay where they are.
CMConsent Mode v2GPCGlobal Privacy ControlEUGDPRUSUS state laws

All your privacy work in one console

The banner, cookies, visitor choices and privacy requests for every site on your plan sit in one place, and the overview shows what changed and what needs your attention.

Screens from the Velo console, shown with an example site and illustrative data.


The Velo console overview: the share of visitors who accept the banner, visitor choices by day and the cookie review.

The overview

See the share of visitors who accept the banner, choices by day, cookies waiting for a category, newly detected scripts and a preview of your live banner.

The Velo set up screen: four steps (your website, install Velo, check connection, first scan), the first scan form and a preview of the default consent banner.

Go live in four steps

Add your website, install Velo with one snippet or through Google Tag Manager, check the connection and run your first scan. Your progress is saved, so you can stop and pick up where you left off. A default banner shows as soon as Velo is installed, and the connection check confirms Velo is reporting from your site. Consent Mode v2 signals go to supported Google tags. Google may model the gaps in eligible accounts; Velo’s part is sending the signals.

The Velo overview further down: new scripts with their category and a held until consent status, and the consent banner that is live.

New scripts and your live banner

See the scripts the latest scan found, each with its category and whether it waits for consent, next to the banner that’s live on your site.

Velo notifications: a finished scan with one cookie to categorise, a change in the consent rate and the share of this month’s sessions used.

Notifications in one place

Finished scans, privacy requests, usage and changes other people made are kept here for 90 days, and you choose what you’re notified about.

4 stepsFrom adding your website to your first scan
30 daysThe reply by date on every privacy request
MonthlyAutomatic rescans on Pro keep the cookie list current
From the first install to the last privacy request, here is what you do in Velo and where you do it.
V
The Velo consoleBuilt by the data team at Amplio Data, in Barcelona and London
See pricing

Start with a scan

See what your homepage already loads before you install anything. This is the kind of result the free scanner hands back.

Sample result with illustrative data. The scanner reads your homepage HTML and public Tag Manager container, and within a daily limit also loads the page in a browser.


Worth a closer look. There’s a consent layer, and the next step is checking that it holds. A consent platform loads alongside 3 tracking tags from the Tag Manager container. What a static scan can’t tell you is whether those tags wait for the visitor’s choice.

Tags we found. 3 tracking tags in the page and Tag Manager, each listed with its category.


Checks passed: 2/4Static checks on the first response.
Tracking tags: 3In the page and Tag Manager.
Cookies on first response: 1Any kind, set by the server.
What we checkedHomepage HTML and public Tag Manager container.
Tracking technology3 tracking tags found inside Google Tag Manager. In the EEA and the UK these need consent. Result: check in a browser.
Consent platformDetected in the Tag Manager container and present when the page loads. A banner alone isn’t enough, because it also has to hold tags back until the visitor chooses. Result: pass.
Google Consent Mode v2Google tags are present. Only a check in a real browser can show whether the Consent Mode default fires before them. Result: check in a browser.
Cookies before consentNo tracking cookies were set by the server on the first response. Result: pass.
Tags we foundGoogle Tag Manager (tag management) in the page HTML. Google Analytics 4 (analytics), Google Ads and Meta Pixel (advertising) inside Tag Manager.

How it works, screen by screen

Screens from the Velo console, shown with an example site and illustrative data.

Get Velo

Know every cookie on your site

The scanner visits your site as a real visitor would, before and after accepting cookies, and lists every cookie and script it finds. Unknown cookies can come with a suggested category, and nothing changes until you accept it.

The Velo scanner: counts of cookies found, categorised, needing review and scripts detected, and a review table with a suggested category.
Cookies, scripts and localStorage keys are listed with the pages they were found on. Unknown cookies get a suggested category, applied only when you accept it, and findings flag what needs your attention. On Pro, an automatic rescan every month keeps the list current.
The Velo scanner’s cookie list: each cookie with its provider, category, the page it was seen on and whether it ran before consent.
Every cookie with its provider, its category, the page it was seen on and whether it ran before consent.

The right defaults in every region

Velo reads each visitor’s country and applies the matching consent defaults. Where the law requires opt in, it stays locked on, and where the law leaves it open, the choice is yours.

The Velo regional defaults screen: opt in required by law for the EEA, UK and Switzerland and for Brazil, Peru, Colombia and Argentina, and opt in or opt out choices for the United States and the rest of the world.
Opt in across the EEA, the UK and Switzerland, and in Brazil, Peru, Colombia and Argentina. Opt out in the US, where Global Privacy Control signals are honoured automatically, with an optional “Do not sell or share my personal information” label for California. You can override the defaults by country wherever the law leaves the choice to you.

See how visitors answer

Follow how many visitors accept, reject or customise their choice, how that moves over time and where they are. Every figure is compared with the previous period.

Velo analytics: the share of visitors who accepted all cookies, customised, rejected all or sent a GPC refusal, and a chart of choices over time.
See accept, reject, customised and GPC refusal rates, choices over time and by country, and a breakdown by consent category. You can export the numbers as CSV.
Velo analytics further down: the breakdown by choice, the share of choices by country and the opt in rate for each category.
The breakdown by choice, by country and by category.

Proof of every choice

Every decision is logged with a receipt ID, the time, the region, the categories allowed and the banner version the visitor saw. Look up a single receipt when someone asks.

Velo consent records: a receipt search and a table of decisions with time, choice, site, region, categories and banner version.
Search any decision by its receipt ID. Every record shows the choice, region, categories and GPC status, and you can export records as CSV.

Answer privacy requests on time

Access, deletion and consent withdrawal requests sit in one queue, each with a reply by date 30 days after it arrived. Velo warns you a week before a request is due and flags anything overdue.

Velo privacy requests: a queue of access, deletion and consent withdrawal requests with received and due dates, days left and status.
Switch between open, due soon, overdue and closed, filter by request type and site, and track each request from open to resolved.

How different teams use Velo

One shared workspace for the people who look after a website and its visitors.

By use case and industry

For ecommerce

Connect your storefront’s consent choices to its analytics and advertising tags. Test checkout separately so you know which events your setup can send.

Cookie consent for online shops

For SaaS

Manage consent across your marketing site and review how signup and trial events reach your analytics tools.

First-party data, collected with consent

For publishers

Velo is not yet a registered IAB TCF CMP. If your advertising partners require a registered CMP, check our TCF status page before choosing Velo.

Cookie consent for media and publishing

For agencies

Manage the client accounts you have access to from the partner portal. Each client keeps their own subscription and workspace.

Works with your platform

Velo works on any site where you can add one line to the page head or one tag in Google Tag Manager. Pick your platform to see how Velo fits it and how to install it.

Switching from another consent platform?

From the journal

Notes on cookie banners, Consent Mode and the data that goes missing between them. All posts.


Is your cookie banner sending the Consent Mode v2 signal?
V
The Velo journal26 July 2026

Can you recover conversions lost to cookie consent?

9 July 2026Read the post

Google Consent Mode v2 in Velo: what is new

2 November 2026Read the post

Common questions

Do I need a developer to install Velo?

You need access to your site’s code or Google Tag Manager. A straightforward setup may only need a snippet, but complex tag configurations may need developer help. Always test before publishing.

What is Google Consent Mode v2?

Consent Mode v2 tells Google tags which types of storage and data use a visitor has allowed. It controls how supported tags behave; it does not replace your banner or configure every other tag on your site.

Can Consent Mode help with measurement gaps?

Google may use modelling to estimate gaps in eligible accounts. The requirements differ between Google Ads and GA4 and depend on traffic and configuration. Velo provides consent signals; it does not guarantee a recovery percentage.

Which regions does Velo cover?

Velo uses opt in defaults across the EEA, the UK, Switzerland, Brazil, Peru, Colombia and Argentina, and opt out everywhere else. The rules are picked at the edge, from each visitor’s country.

Can I migrate from another CMP?

Plan the switch, check your categories and test your tags before removing the previous banner. Existing consent records and returning visitor choices need a separate compatibility check.

Will the banner slow my site down?

Velo adds a script to your page. How much that affects loading depends on your site and tag setup, so check loading performance as part of installation rather than assuming there’s no impact.

Free for one site

Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.