Set up your first website.

You need access to your website’s code or publishing settings. If you use Google Tag Manager, you also need permission to edit and publish its web container. Have your website URL and privacy policy ready.

Already using another consent platform? Keep a copy of its configuration and note which tags it controls. Plan a single switchover so two banners do not compete for the visitor’s choice.

1. Create a Velo account or log in. Complete any account verification shown.
2. Open Websites and add the website you want to manage. Use the published domain, then select that site in the workspace.
3. Open Settings → Configuration. Find the site’s installation details and copy its exact site ID and snippet. Each website needs its own matching configuration.

If your tags live in GTM, use the Velo GTM template guide. Otherwise, follow the guide for your website platform and add the snippet to the site-wide head.

The GTM template loads Velo itself. Installing the direct snippet as well can produce duplicate banners and conflicting consent updates. A direct installation also needs consent defaults in place before dependent measurement commands; an async script’s position alone does not guarantee execution order.

Use the installation guide to check placement, publishing and tag behaviour.

1. Open Banner with the correct site selected. Review its appearance, wording, languages and preferences. Add or check the policy link where your configuration provides it.
2. Keep a visible way for visitors to reopen their privacy choices. Test that control on a phone as well as a desktop.
3. Review Regional defaults for the site. Use Check a country to inspect the expected opt-in or opt-out mode.
4. Review the tags and cookies you actually use. A category label in the banner does not automatically connect every third-party script to that category.

Continue with banner styling and regional settings for the exact controls.

Test the published website, including a normal landing page and another page reached through navigation. Use a fresh browser session for each new-visitor test.

• One banner appears and its text and policy links are readable.
• Accept, reject and a partial preference choice each produce the expected consent state.
• Optional tags respect those choices. Check requests and cookies, not just the banner’s appearance.
• The privacy button reopens preferences, and a changed choice takes effect.
• A reload and a second page preserve the choice as expected.
• The correct website shows installation activity in the workspace.

For Google tags, follow the Tag Assistant test. Keep the results with your implementation notes. A scan can help identify issues, but it is not a substitute for testing each consent action.