Measurement

The Conversion Data Google Ads Relies On: What Changed in 2026 and How to Check Your Tracking

Since June 15, 2026, the Consent Mode ad_storage parameter alone decides whether advertising data from Google Analytics reaches your Google Ads account. Google Signals no longer acts as a second gate, and without ad_user_data, enhanced conversions fail silently. A 20-minute audit of your consent signals keeps conversions from disappearing.

By Darius Lukosius, Google Ads strategist Published September 5, 2026 Updated September 5, 2026 12 min read

The short version

Until June 15, two things controlled the flow of advertising data to Google Ads: the Google Signals setting and the ad_storage consent parameter. Now only the second remains.
If you turned off Google Signals as a privacy safeguard, that safeguard is gone - advertising cookies are used whenever ad_storage is "granted."
Without the ad_user_data parameter, enhanced conversions do not work. Silently. Your reports look like everything is fine.
The consent signal must load before Google tags and on every page, including the order confirmation page and subdomains.
The more decisions you hand to automation, the more expensive every inaccurate conversion becomes. Bad data no longer looks like a bad report - it looks like bad results.

1. What changed on June 15

In mid-April, an announcement appeared in the Google Help Center that almost nobody commented on. The gist: starting June 15, 2026, Google Analytics moves to a single point of data control - Consent Mode on the Google Ads side.

Until then, a dual system was in place. For advertising cookies and user identifiers from the Google Analytics tag to reach a linked Google Ads account, two conditions had to line up: the Google Signals setting enabled on the Analytics side, and a positive ad_storage signal from the consent banner. If either one was "no," the data did not travel.

As of June 15, there is a single gatekeeper. ad_storage decides, on its own, whether advertising data reaches Google Ads. The Google Signals setting is left with one function: determining whether Analytics data is linked to the signed-in user's account for behavior reports inside Analytics itself.

Who this hurts most. Organizations that turned off Google Signals deliberately - as a privacy measure, or as a backup safeguard in case the consent platform failed. That safeguard is gone. Since June 15, advertising cookies are used whenever ad_storage is "granted," regardless of what is enabled in Analytics settings. If your consent banner is misconfigured or missing altogether, Google tags run in their default active state - that is, as if consent had been given.

This is not legal advice but a technical explanation: General Data Protection Regulation (GDPR) requirements have not changed one bit with this update. What changed is the mechanism through which a user's choice reaches Google's systems - and now that mechanism is the only one.

2. The four parameters and what each one controls

Consent Mode v2 has been mandatory for EU and UK traffic since March 2024. Even so, we still find implementations that send only two of the four parameters, the old ones. Such an implementation does not look broken - it simply quietly does not work.

Parameter	What it controls	What stops working if it is missing or denied
`ad_storage`	Advertising cookies and device identifiers	Conversion tracking, remarketing audiences, the entire flow of advertising data from the linked Analytics account
`ad_user_data`	Whether user data can be sent to Google for measurement	Enhanced conversions. This is the most common silent failure point in older implementations
`ad_personalization`	Whether data is used for personalized advertising	Remarketing lists stop growing, audience expansion narrows
`analytics_storage`	Analytics measurement cookies	Session and user measurement in Google Analytics 4 (GA4) reports

All four must be present in both the default and the update command. The default state for European Economic Area traffic is set to "denied," and the consent banner raises it when the visitor actually clicks the button.

3. Why this matters right now

Five years ago, inaccurate tracking meant an inaccurate report. Today it means an inaccurate algorithm decision - and the algorithm has been handed more and more control. When a campaign picks the queries, the ad copy, and the landing page on its own, the only thing it navigates by is your conversion data.

This summer, Google began to automatically switch Search campaigns to AI Max. The practical takeaway is simple: an account where conversions are counted twice, or where half of the real customers never arrive, will make mistakes faster and at greater cost after the switch than before. Fixing tracking after results have dropped is twice as expensive - because by then it is no longer clear who is to blame: the settings or the data.

4. How to check your website in 20 minutes

This checklist does not require a developer. You need a browser, Tag Assistant, and twenty minutes.

Run the "reject all" scenario Open your website in an incognito window, reject everything in the consent banner, and look at the consent states in Tag Assistant. All four parameters should be "denied," and there should be no advertising cookies. If you see only two parameters, your implementation is the first version and enhanced conversions are not working.
Run the "accept all" scenario Repeat the same steps after accepting. All four should switch to "granted," and the conversion tag should fire. If the state updates only after a page reload, some conversions are lost.
Check the order of events The default consent command must happen before any Google tag. The classic mistake: the banner loads asynchronously and a tag manages to fire first. The result is data sent before the visitor has clicked anything.
Review the confirmation page separately The order or thank-you page often loads the conversion tag through a different path than the rest of the site. This is where we most often find the missing consent signal - and with it the explanation for why the account shows fewer conversions than your sales system.
Check subdomains and separate containers If your store, blog, or booking system has its own Google Tag Manager container, each one needs its own consent integration. Fixing one domain does not rescue the others.
Review default states by region The default state can be set regionally. Make sure it is "denied" for EU traffic, and that nobody once switched on "granted" worldwide "to get more data."
Count your conversion actions Open the conversion list in your Google Ads account and check how many are marked as primary. If there are five, including page views and taps on a phone number, the algorithm is optimizing for noise.

Not sure your numbers are real?

In an audit, we check consent signals, conversion duplication, and how many real customers never reach your account. You get a report with specific fixes, not generic advice.

Check my tracking

5. Enhanced conversions: why they stopped being optional

The principle is simple. When a visitor fills out a form or makes a purchase, the website takes their email address or phone number, hashes it in the browser, and sends it to Google along with the conversion. There, the hashed value is matched against signed-in user data. If they match, the conversion is attributed to a click that nothing else would have connected.

The benefit is greatest where the path from click to purchase is long or spans several devices: service businesses, B2B, higher-priced goods. There are three conditions without which it does not work:

Consent. Without the ad_user_data parameter, the data is simply not sent, and no error message will show you.
Data on the page. If the confirmation page has no email, there is nothing to send. In that case you need to either pass it through or use an upload from your sales system.
Format consistency. Spaces, capital letters, and inconsistent phone number formats reduce the match rate. Data must be normalized before hashing.

It is worth recording the match rate once a month. If it suddenly dropped, the first place to look is not Google but changes to your website or consent banner.

6. Server-side tracking: when it is worth it and when it is not

Server-side tracking is not a way around consent. It does nothing the visitor has not allowed. What it does is move the sending of data away from the browser - where ad blockers, cookie lifetime limits, and network filters interfere - to a server you control. The result: data from the same consent reaches its destination more reliably.

Situation	Worth it?	Why
Online store, 500+ orders per month	Yes	The value of lost conversions quickly exceeds the server and setup costs
B2B with a long sales cycle	Yes, together with sending data back from your Customer Relationship Management (CRM) system	What matters is not the number of inquiries but which of them became contracts
Services with 10-30 inquiries per month	Not yet	Fix consent and enhanced conversions first - the impact will be bigger and the cost close to zero
A website with no clear conversion	No	A more accurate measurement of zero is still zero

The order is almost always the same: first a clean consent implementation, then one clear primary conversion action, then enhanced conversions, and only after that server-side tracking. Skip the steps and you get an expensive setup that accurately delivers inaccurate data.

7. Modeled conversions in reports

Some of the conversions you see in your account are not recorded but estimated. When a visitor does not give consent, Google tries to calculate the likely outcome based on the behavior of those who did. This requires a sufficient volume of consented sessions - in small accounts the model is unstable or does not activate at all.

What to do with this in practice:

Do not be surprised that the numbers in Google Ads and in your sales system will never match. What matters is not a match but a stable ratio.
Your consent rate becomes a business metric. A transparent, clearly worded banner yields more data than an aggressive or confusing one.
Before comparing periods, check whether you changed the banner, the tags, or the conversion settings during that time. Half of all "unexpected changes" are exactly that.

8. Seven mistakes we see most often

The consent banner is installed but sends no signals. Everything looks tidy visually, and nothing reaches the tags.
The two newer parameters are missing. Enhanced conversions do not work, and there is no error message.
A conversion is counted twice. The same form is measured both through a GA4 import and a direct tag; the algorithm sees double the benefit where there is none.
Micro actions marked as primary. Page views and clicks steer optimization toward cheap but worthless actions.
The confirmation page is forgotten. The most common place where both the consent signal and the conversion disappear.
Subdomains with their own containers. Each one needs separate fixing.
Changes are not recorded anywhere. Without a log, a month later you cannot answer why the numbers changed that particular week.

9. Frequently asked questions

What exactly changed on June 15, 2026?

From that day, the flow of advertising data from Google Analytics to the linked Google Ads account is controlled solely by the Consent Mode parameter ad_storage. The Google Signals setting is left with only one function: linking Analytics data to signed-in users for behavior reports inside Analytics itself.

Do I need to do anything if Consent Mode v2 is already implemented correctly?

No product changes are required. It is only worth checking the default ad_storage states - previously they could be covered by a disabled Google Signals, and that safeguard no longer exists.

Why don't enhanced conversions work even though everything is turned on?

Most often because of a missing ad_user_data parameter in older implementations. The second most common reason is that the confirmation page simply has no email or phone number that could be hashed and sent.

Does server-side tracking let me collect data without consent?

No. Consent rules apply regardless of where the tags run. Server-side tracking improves the reliability of data you are already allowed to collect; it does not expand the limits of permission.

How many conversions are actually lost to a bad implementation?

The difference ranges from a few percent to more than half, depending on traffic, browsers, and how the banner is configured. The only way to learn your number is to compare account conversions with real orders or inquiries over the same period.

Where do I start if everything is neglected?

With checking the two scenarios using Tag Assistant and reviewing the list of conversion actions. These two steps reveal most problems and cost nothing but time.

Let's fix the data before it costs you

We review your consent implementation, conversion structure, and Google Tag Manager setup, and deliver our findings as a concrete, prioritized list of fixes.

Get a free review

AI Max in Your Google Ads Account: What Changes Automatically and What to Do About It

Sources

Darius Lukosius

Google Ads strategist who has run search and shopping campaigns in the Lithuanian and Baltic markets since 2016. This article draws on changes published by Google and on tracking audits in real client accounts. The text is not legal advice - for specific compliance requirements, consult a lawyer.