Cookie consent for Duda

One cookie banner
for your whole
Duda roster.

If you build client sites on Duda, consent is a rollout problem, not a one off. Velo installs with one paste in Head HTML per site and runs every client from one dashboard — themed to each brand, governed by each region, reported per client.

Live in minutes — one tag through Google Tag Manager, or one line in the site's Head HTML.

Compliant. Fast.
Nothing Lost.

Compliant by default

Region rules apply the right law by location — GDPR consent in the EU and UK, opt out where US states require it. Equal Accept and Reject, per category choices, and every consent recorded in an exportable audit log.

Consent Mode v2, wired right

The denied default lands before any tag fires — the step most installs get wrong. Declined visitors send cookieless pings, and Google models the conversions consent hides instead of dropping them.

Made for Duda

Paste the snippet into the site's Head HTML and republish — repeat per client site, or template it into the sites you clone from. Each client gets their own themed banner and their own audit trail under your single Velo account.

How it goes live

Three steps
on Duda.

01

Paste the snippet

In Duda, open the site's Head HTML, paste the Velo snippet and republish. Or add the Velo template in Google Tag Manager per site.

02

Denied by default, banner up

Velo sets the Consent Mode v2 denied default before any other tag runs, then shows the banner. Nothing non essential fires until the visitor chooses, and every choice lands in the audit log.

03

Verify and forget it

Check the consent signals flip in Tag Assistant or your browser, publish, and you are done. Region rules, records and Google's modelling run on their own from here.

Real Results.
Not Promises.

+37%

Average ROAS lift

Reported across paid channels once consent signal is restored and modelled the compliant way.

20–40%

Conversions recovered

Won back through Consent Mode v2 and server side tagging, so reporting reflects revenue that was already happening.

34%

Sessions brought back

Otherwise hidden by consent, brought back into view, so the data you pay for actually shows up.

Measured ranges across Amplio Data client implementations, not a guarantee.

Questions,
answered.

What Duda teams ask before switching consent on.

Can I manage many client sites from one account?

Yes — that is the agency setup Velo is built around. Every Duda client site runs under your one dashboard with its own domain, theme, region rules and exportable audit trail. Push a change once and it lands roster wide.

Can the banner carry each client's brand?

Yes. Theme the banner per site — colours, logo, copy — and white label the layer entirely so your agency's name is the one clients see.

How long does a rollout across sites take?

The per site work is one paste in Head HTML and a republish. Add it to the template sites you clone from and new builds ship with consent already handled.

What do I report back to clients?

Per client consent rates and recovered signal. With Consent Mode v2 wired, Google models the conversions declined visitors hide — across Amplio Data client implementations that recovers 20–40% of them. Measured ranges, not a guarantee.

Consent handled.
Signal kept.

A compliant banner on Duda in minutes,
and the conversions consent hides, modelled back.