Consent Mode v2,
wired the way Google expects.

When a visitor declines, your tags fall silent and the conversion disappears from your reports. Velo passes the right consent signals so Google can model what you lost, and your campaigns optimise on the full picture again.

tagassistant.google.com
analytics_storagegranted
✓ signal sent
ad_storagedenied
modelled
ad_user_datadenied
modelled
ad_personalizationdenied
modelled

The signal layer behind 100+ marketing teams

Google Consent Mode v2GA4 & Google AdsModelled conversionsLive in 72h

Why Consent Mode v2 matters

Set it up properly and a declined visitor is no longer a lost one. Velo handles the three things that make the difference.

Four signals, set right

Velo reads each visitor's choice and sets all four consent flags correctly, in real time, with no manual tag edits.

Declines still modelled

A cookieless ping still fires on a reject, so Google can estimate the conversion consent would otherwise erase.

Live in a day

One Google Tag Manager template, set at the edge before your tags load. Full setup runs inside 72 hours.

How the gap gets filled

A decline is not a dead end

We value your privacy

We use cookies to measure traffic and improve your experience.

RejectAccept all
Step 1

The visitor declines

They tap reject, and your advertising tags are blocked, exactly as the law requires. With most consent tools, that visitor and any purchase they make now vanishes from GA4 and Google Ads.

analytics_storagegranted
ad_storagedenied
ad_user_datadenied
ad_personalizationdenied
Step 2

Velo passes the signals

Even on a decline, Velo sends Google the precise consent state for each of the four signals. Nothing personal moves, but Google now knows the choice was made and a cookieless ping still fires.

+37%
average ROAS lift
observed 412modelled +138
Step 3

Google models the conversion

From those signals and your consented traffic, Google estimates the conversions that consent hid and adds them back to your reports. The campaign optimises on what really happened.

Count the conversions consent hides

On a typical site, 34% of sessions sit behind the banner. Without modelling, every sale from a declined visitor is simply missing, so your campaigns bid on a fraction of the truth. Velo restores the signal and most sites recover 20 to 40% of the conversions they were quietly losing.

See the banner that asks
analytics.google.com
Observed conversionsconsented sessions
412
Hidden by consentdeclined, not counted
−138
Modelled backrecovered by Velo
+138
Total countedafter Velo
550
+37%

average ROAS lift once the signal comes back.

When declined visitors are modelled and counted, Google Ads bids on the full conversion picture instead of the slice that happened to consent. The same spend works harder.

Figures are measured ranges across Amplio Data client implementations, not a guarantee. Recovery depends on your traffic mix, regions and how your tags are configured. Modelled conversions are estimated by Google, not invented by Velo.

Four signals, set right on every visit

Consent Mode v2 turns on four flags. Velo reads each visitor's choice and sets all four correctly, in real time, with no manual tag edits and no guesswork. That is the whole reason Google can model what a decline would otherwise erase.

Read the developer docs
velo.app/consent
analytics_storagemeasures traffic in GA4
granted
ad_storagestores advertising cookies
denied
ad_user_datasends user data to Google Ads
denied
ad_personalizationallows remarketing audiences
denied

What Velo wires for you

The plumbing that recovers your signal, handled once and kept correct on every page, in every region, for every visitor.

Default state

Denied by default

Before a single choice is made, all four signals start denied. Tags stay blocked, you stay compliant, and Google still receives the cookieless ping it needs.

On choice

Updated the instant they decide

Accept, reject or pick categories, and Velo updates the consent state immediately. The signals always match what the visitor actually agreed to.

Per region

The right rule for each visitor

Opt in across the EEA and the UK, opt out for US state laws, light touch elsewhere. The consent state follows the regime that applies where the visitor is.

No tag surgery

Works with your Google Tag Manager

Drop in the Velo template and your existing tags read consent automatically. No rewriting triggers, no per tag consent checks to maintain by hand.

At the edge

Fast enough to fire first

Velo runs on Cloudflare's edge, so the consent state is set before your tags load. No race, no flicker, no conversions dropped to a slow banner.

On the record

Every choice logged

Each consent state is written to an anonymised, time stamped log. When a regulator or a client asks how the signal was captured, the answer is ready to export.

What still reaches Google on a reject

A decline blocks the cookies, not the signal. These are the cookieless pings Velo keeps flowing so the model has something to work from.

Consent stategranted or denied, per flag
Coarse regioncountry level, no precise location
Conversion eventthat one happened, not who
Timing pingcookieless, no identifier
One template, every tag covered

Consent Mode v2, set once and kept correct.

Add the Velo template to your Google Tag Manager and the four signals stay right on every page, in every region, with nothing to maintain by hand.

Recovery that stays inside the rules

Modelling only works when consent is captured properly first. Velo keeps you on the right side of the laws your visitors are protected by, and runs to a recognised information security standard.

GDPR
CCPA
ISO 27001

Consent Mode v2, answered

What is Consent Mode v2?

It is Google's framework for passing a visitor's consent choice to GA4 and Google Ads through four signals: analytics_storage, ad_storage, ad_user_data and ad_personalization. When a visitor declines, advanced mode lets Google model the conversion from a cookieless ping instead of dropping it. Velo wires it the way Google expects.

What happens when a visitor rejects?

Your advertising tags stay blocked, as the law requires. Velo still sends Google the precise consent state and a cookieless ping, so Google can model the conversion from your consented traffic. Most sites recover 20 to 40% of the conversions consent was hiding.

Are modelled conversions real conversions?

They are Google's estimate of the conversions that happened behind a decline, calculated by Google from your consented traffic and the consent signals Velo sends. Velo does not invent numbers. Treat them as a measured estimate, not a guarantee.

Do I have to edit my tags?

No. You add the Velo template to your Google Tag Manager once, and your existing tags read consent automatically. There are no per tag consent checks to write or maintain by hand. See the developer docs for the full setup.

Does this work outside the EU?

Yes. Velo applies opt in across the EEA and the UK, opt out for US state laws and a light touch notice elsewhere, set at the edge from the visitor's region. The four signals are set correctly wherever the visitor is.

How long does it take to go live?

Full setup runs inside 72 hours. The template itself drops into Google Tag Manager in minutes, and everything else is configured in the dashboard without touching the snippet again.

Stop losing the conversions you already earned.

Add Velo once and get Consent Mode v2 wired correctly, the four signals set on every visit, and the declined conversions modelled back, live in 72 hours.

Consent saved