Google Consent Mode v2 and Enhanced Conversions

A while back I watched a client’s Google Ads account develop a strange limp. Desktop conversions looked healthy. Mobile conversions — for a local service business whose customers overwhelmingly book from a phone — had all but vanished. The ads were running, the calls were coming in, the booking forms were being filled. Google Ads just couldn’t see any of it happening on mobile.

The culprit wasn’t the campaign. It was Safari. The booking form posted, redirected to a success page, and somewhere in that hop Apple’s tracking prevention stripped the cookie that tied the conversion back to the ad click. Every iPhone customer — most of the customer base — was converting invisibly. The fix was Enhanced Conversions: the customer’s own email, hashed in the browser at the moment of booking, gave Google something to match where the cookie had been confiscated. Mobile attribution came back the same week.

I tell that story because Consent Mode v2 and Enhanced Conversions get written about as compliance chores, and they’re not. They’re the difference between an ad account that can see what it’s doing and one that’s bidding half-blind.

The quiet hole in your numbers

Three things eat conversions before they reach your reports, and none of them announces itself.

Consent banners. A meaningful share of UK visitors decline cookies when asked. Decline rates vary wildly by sector and banner design, but a third of visitors saying no is not unusual — and every one of them who goes on to buy is a conversion your tracking never records, unless something stands in for the cookie.

Browser privacy. Safari’s Intelligent Tracking Prevention caps and strips tracking cookies; Firefox does its own version; iOS users are most of the mobile traffic for many UK businesses. This is the hole my client fell into — no consent banner involved, just the browser quietly discarding the attribution chain.

Ad blockers. A chunk of visitors never load the tags at all.

Stack those up and a store can be genuinely converting twenty or thirty per cent more than its dashboard reports. And that’s not just a vanity problem, because the numbers aren’t only for you.

What Consent Mode v2 actually does

Consent Mode v2 is Google’s answer to the consent half of the problem, and since March 2024 it’s been a requirement, not a suggestion, for anyone using Google’s advertising features in the UK and EEA — remarketing audiences and conversion modelling stop working without it.

The mechanism is simpler than the documentation makes it look. Your consent banner becomes the source of truth, and Google’s tags listen to it. Visitor consents: everything works as before. Visitor declines: the tags drop to sending cookieless “pings” — anonymous signals that say a conversion happened here without saying who. Google then models the gap: it knows what consented visitors do, it knows how many declined, and it statistically reconstructs the conversions it couldn’t observe. The modelled conversions land back in your Google Ads numbers, labelled as such.

The practical effect: a decline stops being a deletion. Without Consent Mode, a declined visitor who buys is invisible. With it, they come back as a modelled conversion — an estimate, and labelled as one, and far better for the bidding than a hole.

For Shopify stores the implementation is mostly plumbing that already exists — Shopify’s native consent banner and the Google channel app speak Consent Mode between themselves. The places it goes wrong are custom banners that never wire the consent signal to the tags (the banner shows, the visitor declines, and the tags carry on regardless — which is worse than no banner, because now it’s non-compliant and dishonest), and the v1-era setups that never added the two new parameters v2 requires. If your banner was installed before 2024 and nobody’s touched it since, that’s worth a look this week, not this quarter.

What Enhanced Conversions actually does

Enhanced Conversions attacks the other half — the cookie-blocked conversions that consent can’t bring back, because the visitor consented and the browser binned the cookie anyway.

The mechanism: at the moment of conversion, data the customer has already given you — their email, sometimes phone or address — is hashed (turned into an irreversible fingerprint, SHA-256, before it leaves the browser) and sent alongside the conversion. Google matches the hash against signed-in Google accounts. If the person who bought from you is signed into Chrome or Gmail anywhere — and most people are — the conversion gets attributed to the ad click that earned it, cookie or no cookie.

Google’s published range is a 5–20% uplift in measured conversions. In my experience the businesses at the top of that range are exactly the ones like my limping client: mobile-heavy, Safari-heavy, form- or checkout-based. The data leaving your site is nothing the customer didn’t already hand you, hashed before transmission — this is first-party data doing first-party work, not surveillance.

One caveat that matters: Enhanced Conversions recovers attribution, not consent. It runs on consented conversions that browsers broke, and it complements — never replaces — Consent Mode’s modelling of the declined ones. You want both, because they patch different holes.

The part everyone skips: checking it’s firing

Here’s where I’ll be blunt, because this is the failure I actually find in accounts. Both features fail silently. A Consent Mode setup where the banner never passes the signal still shows a working banner. An Enhanced Conversions toggle flipped on in a dashboard, with no hashed data actually arriving, still shows as “enabled”. The interface reports the configuration; it does not report the truth. Dashboards are good at that.

The check is unglamorous: fire a real test conversion and confirm, in the conversion’s diagnostics, that enhanced data was received and consent state was recorded — not that the settings page says it should have been. When I audit a tracking setup, the whole chain gets walked from the click to the recorded conversion, because every layer happily reports “OK” on the layer above’s say-so. The setups that were “done” a year ago and never verified are where the missing 20% lives.

What to actually do

If you run Google Ads in the UK, the worklist is short:

1. Confirm Consent Mode v2 is live and wired — banner present, the consent signal actually reaching Google’s tags, both v2 parameters set. Pre-2024 installations are the prime suspects.
2. Enable Enhanced Conversions on your conversion actions and verify hashed data is arriving — via the channel app on Shopify, via the Google tag elsewhere.
3. Test a conversion end to end and look at what Google recorded, not what your settings claim.
4. Then leave it alone and let the bidding re-learn against fuller data — the benefit compounds over weeks as the algorithms see more of what was always happening. (If your spend is high enough that you’re wondering about server-side tracking, that conversation comes after these steps, not instead of them.)

If you’d rather have the chain checked by someone who does it weekly — the consent wiring, the hashing, the layers in between that all say “OK” — get in touch. The most common thing I find isn’t a broken setup; it’s a half-finished one that’s been quietly costing attribution since the day it was declared done.

Related: The Dashboard Is a Decoy · One Shopify Expert Operator or Three Marketing Agencies? · Why Your Website Gets Visitors But Not Enquiries