Install once. Check it works.

Choose Google Tag Manager or a direct website installation, then verify loading, consent order and visitor choices.

3 min readReviewed 23 September 2026

Choose your installation method

Use one method per website
Your setup	Use this route
Tags managed through Google Tag Manager	Install the Velo CMP template and trigger it on Consent Initialization – All Pages.
Website builder, theme or custom code	Add the site’s direct snippet to the global head, following the platform guide below.

The GTM template already loads the banner SDK. Do not add a second copy through your website’s theme, a plugin or a Custom HTML tag.

Install the direct snippet

In the Velo workspace, select your website and open Settings → Configuration → Install.
Copy the complete snippet for that website. Keep its site ID and API endpoint intact.
Paste it in the site-wide <head> using your platform’s custom-code field or theme template.
Publish the website, then clear any relevant site or CDN cache.

Example only · use your own site ID

<script src="https://cdn.veloconsent.com/v1/velo.js"
  data-api="https://app.veloconsent.com"
  data-velo-site="YOUR-SITE-ID"
  async></script>

Script placement is only part of consent setup.

An async script can execute after code that appears below it. Establish the consent defaults before Google measurement commands run, and configure checks for other tags. Follow the consent-order guidance before publishing measurement changes.

Follow your platform’s guide

Use the instructions for the place where your website is published. The guides explain the correct custom-code field, publishing step and platform limitations.

Google Tag Manager WordPress Shopify Webflow Framer Wix Squarespace Drupal HubSpot Square Duda Shopware BigCommerce

For a custom application, place the script in the shared document head so it is available across routes. Test client-side navigation as well as a full page load, and avoid mounting a new copy after every route change.

Verify the published installation

Open the live website in a fresh browser session. Do not rely on the builder’s preview.
Check the browser’s Network panel for velo.js and the site configuration request. Resolve blocked or failed requests.
Check that the loaded snippet has the site ID you copied from Configuration.
Confirm that one banner appears and the privacy control can reopen it.
Test accept, reject and preferences, then navigate to a second page.
Check the Google consent state and any non-Google tags independently.

Fix a banner that is not showing

Rule out an existing choice. Open a fresh private session or use the existing privacy button. Returning visitors may already have a saved decision.
Confirm publication. Save and publish the website or GTM container. A draft or preview does not update the public site.
Check for blocked loading. Look for a content security policy error, failed CDN request, browser extension or script optimiser that delays Velo.
Check the configuration. Compare the site ID and API endpoint with Configuration. Confirm that automatic banner display has not been disabled in your custom install.
Check for another install. Search your theme, plugins and GTM for an older CMP or another copy of Velo.

If the banner appears twice, remove the extra installation from its source, publish again and retest in a fresh session.