Tracking conversions without cookies: Enhanced Conversions, Consent Mode v2 and server-side tagging

(updated ) 8 min read google-adstrackingmeasurement
Can you track conversions without cookies? Partly. Here's how Enhanced Conversions, Consent Mode v2 and server-side tagging work together in Google Ads.

Without cookies, you track conversions with first-party data: Enhanced Conversions links hashed customer data to the click, Consent Mode v2 lets Google model missing conversions and server-side tagging makes your tracking less dependent on the browser. Third-party cookies have stayed in Chrome since Google’s decision in April 2025. Safari and Firefox block them by default, Safari also limits the lifetime of cookies on your own site, ad blockers stop tags and some of your visitors decline the cookie banner.

The result: you record fewer conversions than actually happen. And if your conversion data is shaky, Google’s bidding algorithm steers on an incomplete picture. Three layers win back a large part of it. I set them up as part of Google Analytics and tracking, alongside the campaigns themselves.

Where your conversions leak away

Google Ads optimizes on the conversions that come in. If some are missing, Smart Bidding learns from a skewed picture. The three biggest leaks:

  1. Visitors without consent. If someone declines the cookie banner, the Google tags don’t place advertising cookies and the click can’t be linked to the conversion.
  2. Browsers and ad blockers. Even with consent, Safari limits the lifetime of cookies and ad blockers stop tags, so the link between click and conversion drops out.
  3. Sales outside your site. A quote that closes over the phone is only visible to Google Ads if you report that sale back yourself.

Enhanced Conversions, Consent Mode v2 and server-side tagging each tackle a different part. On their own, they leave gaps.

Enhanced Conversions: linking hashed customer data to the click

Enhanced Conversions (called “verbeterde conversies” in the Dutch Google Ads interface) sends first-party customer data along with a conversion: the email address, phone number, name or address the customer entered themselves. The data is hashed with SHA-256, a one-way hash, before it goes to Google. So Google never receives the plain email address.

Google compares that hash with Google accounts that customers were signed in to when they interacted with your ad. If there’s a match, the conversion still counts for the right click, even if the cookie was missing.

There are two versions:

  • Enhanced Conversions for web: for conversions on your website, such as a purchase or an inquiry. The data is sent at the moment of conversion.
  • Enhanced Conversions for leads: for sales that close outside your website, from a lead that came in through your site. You import the closed sale, and Google links it back to the campaign through the hashed data.

Google announced that from April 2026, Google Ads accepts customer data from website tags, Data Manager and API connections at the same time, and that from June 2026 both versions become one feature with a single on/off toggle. From June 15, 2026, API uploads of offline conversions and Enhanced Conversions for leads run through the Data Manager API instead of the Google Ads API. Google describes this on its help page as an announcement, so check which setting you see in your own account.

One condition is often forgotten: without the ad_user_data signal from Consent Mode, the tag doesn’t send hashed customer data. So Enhanced Conversions only works for visitors who agreed to it.

Consent Mode v2 passes the choice from your cookie banner to the Google tags. It does this with four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. If you use Google tags for measurement or remarketing, you have to pass that choice to Google for visitors from the EEA.

You can set it up in two ways:

  • Basic: the Google tags only load once someone has clicked on the cookie banner. If the visitor declines, nothing goes to Google. For modeling, Google then uses a general model.
  • Advanced: the tags load immediately, with the default status set to denied. As long as there’s no consent, they send cookieless pings. Google then models with a model specific to your account.

According to Google, conversion modeling through Consent Mode recovers on average more than half of the ad-click-to-conversion journeys lost to declined cookies, and with the advanced setup about twice as many on average. Google mentions a threshold for modeling of 700 ad clicks in 7 days per country and domain combination.

The change of June 15, 2026

Until June 15, 2026, two settings determined whether Google Analytics shared advertising cookies and IDs with Google Ads: Google signals in GA4 and your Consent Mode settings. Since that date, Consent Mode within Google Ads is the only control. Google signals now only handles the link with signed-in users for reports in GA4. In Consent Mode, ad_storage is the signal that determines whether the Analytics tag may use advertising cookies and IDs for Google Ads.

If ad_storage isn’t set correctly, you’ll see it first in your conversion import from GA4 and in your audiences. At one webshop, exactly that happened after a new cookie banner: the GA4 import was the primary conversion there and dropped away almost completely, while GA4 itself looked healthy. A dedicated Google Ads conversion tag, with Consent Mode, as the primary conversion solved it.

Server-side tagging as the third layer

With server-side tracking, your website first sends measurements to a server under your own domain, usually a Google Tag Manager server container. That server passes the data on to Google Ads, GA4 and Meta. Because the measurement runs through your own domain, fewer measurements are lost to ad blockers and browser restrictions. You also decide per platform which data goes through.

Server-side tagging doesn’t bypass the cookie banner. Your visitor’s choice also applies on the server, and Google describes how to pass Consent Mode on in a server container. Set up properly, you measure more completely what you’re allowed to measure.

It is the heaviest of the three layers, though: you add a server that you have to host and maintain. Sometimes a lighter step is enough. With Google Tag Gateway, you load the Google tags through your own domain, for example via Cloudflare, without a full server-side setup.

How to set it up

A workable order:

  1. Choose a cookie banner that supports Consent Mode v2. The consent management platform (CMP) converts your visitor’s choice into the four signals.
  2. Set the default status to denied for visitors from the EEA, and switch it to granted as soon as someone agrees. The default status has to be in place before a single tag measures anything.
  3. Turn on Enhanced Conversions in the Google Ads conversion settings, and make sure the customer data comes in through the Google tag, Google Tag Manager, Data Manager or the API.
  4. Supply the customer data. The automatic option lets Google scan your conversion page for form fields. That works on a standard checkout, but on custom pages it often misses fields. In that case, put the data in the data layer yourself and map it in Google Tag Manager. The Google tag hashes it before it’s sent.
  5. Test both accepting and declining. Check in Tag Assistant whether the default status and the choice come through correctly. Then check in Google Ads, on the Diagnostics tab of your conversion, whether Consent Mode and Enhanced Conversions are working. That status can take 48 hours to 2 weeks to appear.

Decision rules: what I turn on and when

  • I turn on Enhanced Conversions for web as soon as customers enter their own email address or phone number on your site, for an order or an inquiry. That’s the case in almost every webshop and on every lead form.
  • I choose Enhanced Conversions for leads when the sale only closes later, over the phone or after a quote, and you can pull the closed deals with email addresses from your CRM.
  • I set Consent Mode to advanced, unless your privacy policy doesn’t allow a single request to Google without consent. Then it’s basic.
  • With fewer than 700 ad clicks in 7 days per country and domain, I don’t count on modeling. The gain is then in a cookie banner that gets more visitors to make a choice.
  • I only recommend server-side tracking once the regular tracking is correct and there are enough conversions to make a difference. With a handful of conversions a month, I don’t start on it.
  • After every new cookie banner or CMP, I compare the conversions in Google Ads, GA4 and your own orders or inquiries side by side for a few weeks.
  • Plain customer data never leaves unhashed. Hashing has to happen before sending, or you send plain personal data to Google.

You pay for every click, so you want to know which clicks deliver something. With first-party data, you keep that visibility, even when cookies are missing, and the bidding algorithm keeps usable data to steer on.

Need help with the setup?

Suspect that your conversions are underreported, or not sure whether Consent Mode and Enhanced Conversions are set up correctly? Request a Free Performance Quick Scan. I check your tracking with read-only access and show you where conversions leak away.

Sources

Frequently asked questions

Can you track conversions without cookies?

Partly, yes. Enhanced Conversions links hashed customer data, such as an email address, to the ad click, even when the cookie is missing. Consent Mode v2 lets Google model the conversions of visitors who didn't give consent. Server-side tagging means fewer measurements get lost along the way. Consent is still required: visitors who decline only count through the modeling.

What is the difference between Enhanced Conversions and Consent Mode v2?

Enhanced Conversions restores the link between click and conversion using hashed customer data from visitors who consented to it. Consent Mode v2 passes the choice from your cookie banner to Google and lets Google model the conversions of visitors who declined. Each covers a different gap in your tracking, which is why I turn both on.

Want to win back return?

Start with a Quick Scan and find your 3 biggest opportunities.