In June 2026, Google changed how consent choices govern the data that reaches Google Ads. If you run Consent Mode for visitors in the European Economic Area, the United Kingdom or Switzerland, your default consent settings now matter more than they did before.
This guide explains what changed according to the documentation vendors have summarized, shows a default configuration by region, and lists how to test it.
What changed
Vendor write-ups that quote Google's documentation say that from June 15, 2026, the consent choices managed through the Ads consent mode settings control how Google collects and uses data. They also say the Google signals setting no longer controls that behavior. One consent platform describes ad_storage as the main gate on what reaches Google Ads and recommends setting it to denied by default for EEA, UK and Swiss traffic.
These are secondary sources. Before you change anything, read Google's own June 2026 announcement and the current Consent Mode documentation. This article is not legal advice, and your consent defaults should match advice from your privacy counsel.
The four signals
Consent Mode v2 uses four signals:
ad_storage: whether advertising cookies and identifiers can be storedanalytics_storage: whether analytics cookies can be storedad_user_data: whether user data can be sent to Google for advertisingad_personalization: whether data can be used for personalized advertising
Our earlier guide on checking that Consent Mode v2 is enabled shows how to confirm all four are present.
Set defaults by region
A default consent state must load before any Google tag runs. For regulated regions, the usual starting point is denied for all four signals until the visitor chooses. Use the region parameter to apply different defaults to different places.
gtag('consent', 'default', {
ad_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied',
analytics_storage: 'denied',
region: ['AT','BE','BG','HR','CY','CZ','DK','EE','FI','FR','DE','GR','HU','IE','IT','LV','LT','LU','MT','NL','PL','PT','RO','SK','SI','ES','SE','IS','LI','NO','GB','CH'],
wait_for_update: 500
});
gtag('consent', 'default', {
ad_storage: 'granted',
ad_user_data: 'granted',
ad_personalization: 'granted',
analytics_storage: 'granted'
});
The first block covers EEA member states plus Iceland, Liechtenstein and Norway, and also the United Kingdom and Switzerland. The second block sets the default for everyone else. Whether you grant by default outside those regions depends on the laws that apply to your visitors, such as state privacy laws in the United States. Decide that with your counsel.
wait_for_update gives your consent platform a short window, in milliseconds, to send the visitor's saved choice before tags fire.
Wire it into GTM
If you use Google Tag Manager:
- Load your consent platform's GTM template, or the Consent Mode settings built into your platform, so the default state is set in the Consent Initialization trigger.
- Make sure the default tag fires on Consent Initialization, before All Pages tags.
- Configure the platform to send an update when a visitor accepts, rejects or changes a choice.
- Check that your Google tags have the right built-in consent checks. Google Ads and GA4 tags support consent checks by default, and other tags may need extra settings.
Test the setup
Test with three visitors, in a private window each time:
- A visitor in a regulated region who rejects everything. Advertising cookies should not be set, and Google tags should send only the limited pings Consent Mode allows.
- A visitor in a regulated region who accepts. Tags should send full data after the update.
- A visitor outside those regions. Check that the default you chose applies.
Use GTM Preview or Tag Assistant to see the consent state on each page load, and check the network requests for the consent parameters that Google tags append. Our Consent Mode service includes this kind of test pass.
What to expect in reporting
Denied consent reduces the data Google can use. Modeled conversions may fill part of the gap when your setup and traffic volumes meet Google's requirements, but modeling needs enough consenting traffic to work. Review your Google Ads and GA4 reports for the weeks after you change defaults, and tell your team to expect a step in reported conversions.
If your acceptance rate is low, the banner is a good place to look. Our case study on behavioral modeling and consent rates shows how a clearer banner changed what Google could model.
Checklist
- Read Google's June 2026 announcement and current documentation.
- Confirm all four signals have defaults, set before any Google tag fires.
- Use
regionto separate regulated regions from the rest. - Check that your consent platform sends updates.
- Test accept, reject and out-of-region visits.
- Record the date of the change, so you can explain shifts in reporting.
Need expert tracking setup?
Our Google Tag Manager experts have delivered 500+ tracking setups with a 98% success rate.
Get a Free Consultation →