Add Velo to Duda.
Install the Velo cookie banner and Google Consent Mode v2 on Duda in minutes. One line in Head HTML does it. If you already run Google Tag Manager, that route is on this page too.
One line, and every
page inherits it.
One line in Duda, and the banner is on every page with the Consent Mode default set before any other tag can fire. Same banner, same wiring and the same audit log as the Tag Manager route.
Already running Google Tag Manager? Take that route instead ↓
Three steps · about two minutes
-
01
Copy the line
One script tag, the same on every page of the site. Everything below is about getting it into the right place, and that place is always the head, ahead of the tags it governs.
<!-- Before your other tags. That order is the point. --> <script src="https://veloconsent.com/v1/velo.js" data-velo-site="your-site-id" defer></script> -
02
Paste into the site’s Head HTML
In the Duda editor, open Settings → Head HTML, paste the snippet, and save. Every page of the site inherits it.
my.duda.co · Head HTML
-
03
Republish
Duda applies head code on republish, so republish and reload the live site. The banner renders with the Consent Mode default set before any other tag can fire.
your-site.com
Duda serves the published version, so a head code change only goes live on the next republish. Banner copy and region rules changed in the Velo dashboard, by contrast, apply without touching Duda at all — which is what makes this workable across a book of client sites.
Or import the tag
in Tag Manager.
One tag, no code on the page, and your whole measurement stack stays in one place. No Tag Manager yet? Paste the GTM container into the same Head HTML panel, republish, then start here.
- 01Import the Velo CMP templateTemplates→Tag Templates→New→Import
- 02Create the tagTags→New→Velo CMP template
- 03Tick the two recovery optionsAdvanced→url_passthrough→ads_data_redaction
- 04Fire it on Consent Initialization – All PagesTriggering→Consent Initialization – All Pages
- 05Turn on consent overview under AdminAdmin→Container Settings→Enable consent overview
- 06Preview, then publishPreview→Submit→Publish
Duda questions,
answered.
What teams installing on Duda ask first.
I run many client sites on Duda.
That is the setup Velo is built for: every client site gets its own site ID and banner, and you watch them all from one Velo dashboard: consent rates, recovered conversions and audit logs per client. See Velo for agencies.
Duda has a cookie notification widget.
Switch it off so Velo is the only layer your visitors see. Two banners confuse people, and only Velo wires the decision into Consent Mode, the audit log and your tags.
Do changes need a republish?
Yes. Duda serves the published version, so any head code change goes live on the next republish. Banner copy and region changes made in the Velo dashboard, by contrast, apply without touching Duda at all.
Will it slow the site down?
No. The script loads deferred, never blocks rendering, and the visitor's region is resolved at the nearest edge before the page finishes painting. The banner itself is a few kilobytes of static code.
Can an AI assistant do this for me?
Yes. Copy the prompt in Install with agents, just below, into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries the steps on this page, the order the tags have to load in, and the checks the agent has to run before it tells you the job is done.
Or hand it
to an agent.
Copy the prompt into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries everything on this page: both routes, the order the tags have to load in, and the checks that prove it worked.
Paste it in as your first message, then swap your-site-id for the ID on your Velo dashboard. Everything else the agent needs is already written into it, including what to check before publishing.
Working with an agent that reads the web? Point it at veloconsent.com/llms.txt and /install.md for the same context in plain text.
From the journal.
Your banner, your consent,
your data — all in one place.
