Use case

Switch consent platform without a gap

Move from Cookiebot, CookieYes, OneTrust, Usercentrics or another consent platform in one planned change. You scan what you load and set your categories, then install Velo and remove the old banner in the same release.

Examples on this page use sample data. This is not legal advice.

Switch over in five steps and one release

Follow this order and the page always has a consent state. The old banner comes out in the same release that puts Velo in, so visitors never see two banners, or none.


  1. Before

    Export the old records

    Download the consent records from the platform you are leaving. Velo cannot import them, and you may need them as proof later.

  2. Before

    Scan and review categories

    Run the Velo scan and check the category of each cookie it lists.

  3. In a workspace

    Add the Velo CMP tag

    Set it up in a Tag Manager workspace, on Consent Initialization, and preview it.

  4. Same release

    Remove the old banner

    Take out the old platform’s tag or plugin and publish both changes together.

  5. After

    Check in debug mode

    Open the site with ?velo_debug=1 in the address and confirm the default lands before your Google tags.

What carries over, and what does not

Most of a switch is knowing which parts start again from scratch.

Does not carry over

  • Choices saved by the old platform, so visitors choose once more.
  • The old platform’s consent records, so export them before you leave.
  • Its cookie list and categories, which the Velo scan rebuilds.
  • Triggers that listened for its events.

Stays as it is

  • Your Google tags, which read Consent Mode from whichever platform sets it.
  • Your Tag Manager container and its other tags.
  • Your pages, since Velo is one snippet or one tag.

A WordPress site leaves its old plugin

A company blog on WordPress has run another consent plugin for three years. Its tags are in Google Tag Manager.

Illustrative example with sample data, not a customer story.


Find what listened to the old platform

Google tags read Consent Mode, so they follow Velo as soon as it sets the default. Tags that fired on the old platform’s own event need a new trigger: Velo pushes velo_consent_update to the data layer with the categories allowed.

The cookie list in the Velo scanner: each cookie with its provider, category, the page it was seen on, whether it was set before consent and its review status.

The scan rebuilds the cookie list

Known cookies arrive with a category. Unknown ones can come with a suggested category, and nothing applies until you accept it.

Works with the platforms you build on

WordPressShopifyWebflowWixHubSpotPrestaShopDrupalBigCommerceShopwareNext.jsAstroSquare

Where it lives in Velo

It starts with the free scan, then two screens in the console.

Scan your site

Scan first

The free scan reads your homepage and public Tag Manager container and names the consent platform it finds. Once Velo is installed, the console scanner visits up to three pages before and after accepting, and lists cookies, marked scripts and local storage keys.

The Velo scanner: counts of cookies found, categorised, needing review and scripts detected, and a review table with a suggested category for an unknown cookie.

Install, then verify

Follow the guide for your platform. The set up screen walks through four steps and shows whether Velo is reporting from your site.

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

What Velo covers, and what it does not

The limits, stated plainly, so you can decide before you install anything.


No import toolVelo does not import categories, cookie lists or consent records from another platform. The scan rebuilds the cookie list from your live site.
Returning visitorsChoices saved by your old platform do not carry over. Visitors see the Velo banner once and choose again.
One install onlyUse the snippet or the Tag Manager template, never both. Two installs mean two banners.
Platform guidesStep by step guides cover WordPress, Shopify, Webflow, Wix and twelve more platforms.
PlansFree covers one site. Pro covers unlimited sites from €7 a month, plus VAT.
Not legal adviceVelo gives you the banner, the signals and the records. Whether your setup meets the law in your sector is for you and your advisers to decide.

Questions and answers

Can I import my old consent records?

No. Keep an export from your previous platform. Velo’s records begin with the first decision made on the Velo banner.

Will visitors be asked again?

Yes, once. A choice stored by another platform is not read by Velo, so the first visit after the switch shows the Velo banner.

How long does a switch take?

It depends on how many tags listen to the old platform. A site whose tags are all Google tags in Tag Manager needs little more than the new template and a publish. Each tag wired to the old platform’s events adds a trigger to change and test.

Free for one site

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