On June 15, 2026, Google Ads changes how it reads Consent Mode: ad_storage becomes the sole signal, and Google Signals in GA4 no longer feeds data independently into Google Ads. For businesses operating in Ukraine or Eastern Europe, this change requires context: Ukraine is not in the EEA, but its EU candidate status and tight business integration with EU markets means many Ukrainian advertisers are already affected.
This guide explains who in the Ukraine/Eastern Europe context needs to act before June 15 - and who does not.
Ukraine's Position Relative to Consent Mode Requirements
Ukraine is not currently a member of the EU or EEA. Ukrainian internet users are therefore not covered by GDPR or the EU ePrivacy Directive in the same way as EU residents. Domestic Ukrainian traffic - users browsing from Ukrainian IP addresses - does not trigger mandatory Consent Mode obligations.
However, the situation is more complex for most Ukrainian businesses:
Ukrainian companies with EU operations. Since 2022, a large share of Ukrainian businesses have registered entities in Poland, Germany, or other EU member states. If your EU-registered entity runs Google Ads and those ads target EU users, GDPR-based Consent Mode requirements apply to that portion of your advertising.
Ukrainian companies selling into EU markets. Even without an EU legal entity, if you run Google Ads campaigns geotargeting EU countries, GDPR arguably applies to your processing of EU user data. Consent Mode is the mechanism Google provides for handling this.
International advertisers with Ukrainian operations. Companies with offices or clients in Ukraine, running campaigns that target Eastern European audiences including Ukraine, need to understand which portion of their traffic requires Consent Mode and which does not.
What Changes on June 15
The change applies to all Google Ads accounts globally - but its practical impact is concentrated in markets where users actively manage consent choices (EU/EEA).
Before June 15: Google Ads drew data from ad_storage, ad_personalization, and Google Signals in GA4.
From June 15: Google Ads reads only ad_storage.
For advertisers targeting a mix of EU and Ukrainian audiences:
- Ukrainian domestic users without consent banners:
ad_storagedefaults togranted- no change - EU users subject to consent banners:
ad_storagebecomes the only data point Google Ads uses - If your EU portion has misconfigured
ad_storage, EU conversion data degrades from June 15
Who This Affects in Eastern Europe
Ukrainian businesses with EU campaigns: Check your Consent Mode setup if any Google Ads campaign geotargets Poland, Germany, Czech Republic, Slovakia, or other EEA countries.
Businesses targeting Poland and Ukraine simultaneously: A common scenario for Ukrainian diaspora businesses. Polish users require Consent Mode (Poland is in EEA); Ukrainian users do not - but a single site with both audiences needs correct implementation for the Polish portion.
IT and SaaS companies with global user bases: Ukrainian tech companies often have international SaaS products with users across EU countries. Consent Mode applies to the EU user portion.
Digital agencies in Ukraine managing EU clients: If you manage Google Ads accounts for Polish, German, or other EU-based clients, the June 15 change directly affects those accounts.
Three Steps to Verify Before June 15
Step 1 - Check the Tag in Google Tag Manager
Open GTM and find your Google Ads Conversion Tracking tag. Under Consent Settings, verify the tag requires ad_storage. Check whether your CMP integration exists and is active for EU users.
If you show a consent banner only to EU users (geo-targeted banner), verify the CMP correctly initialises and sends the GTM update for EU IPs. Some geo-targeted banner implementations have initialisation delays that cause conversion tags to fire before the consent signal is received.
Step 2 - Test Signals in Google Tag Assistant
Visit tagassistant.google.com, enter your site URL, and enter debug mode. Test with your consent banner:
- Accept all →
ad_storage: granted - Decline →
ad_storage: denied
If your banner only shows for EU users, you may need to temporarily enable it for all visitors, or test from an EU IP, to verify the signals.
Step 3 - Review Tag Diagnostics in Google Ads
Tools → Measurement → Conversions → Tag Details tab. Check "Consent Mode signal coverage." If you run mixed EU/non-EU campaigns, segment by geography in the Conversions report to assess EU-specific signal quality.
For Businesses New to Consent Mode
If you have been running Google Ads campaigns targeting EU markets without a consent banner or without Consent Mode implementation, June 15 is a natural moment to set this up - both for compliance with GDPR and for data quality in Google Ads.
The minimum required to comply with Consent Mode v2:
- A Consent Management Platform (CMP) with Google-certified Consent Mode v2 support
- GTM integration sending
ad_storageupdates based on user consent choices - Google Ads conversion tags configured to require
ad_storage
For businesses on WordPress: Cookiebot or Complianz are widely used options. For Joomla-based sites: GTM-based integration with a compatible CMP is the recommended path.
Consent Mode Modelling and Eastern European Markets
For Ukrainian and Eastern European audiences that do use consent banners (typically businesses with EU legal presence), Consent Mode Modelling provides statistical recovery of non-consenting conversion data.
Modelling requires:
- 700+ consented conversions weekly
- Correctly configured
deniedsignal (not absent)
For smaller advertisers or those with mixed audiences, the modelling may be less relevant - but correct signal configuration remains important regardless.
Related reading
For a broader view of how Google's algorithm changes are affecting Eastern European search results, see our analysis of Google's May 2026 Core Update and its impact on the Ukrainian market.
FAQ
Q: My website is Ukrainian, my users are in Ukraine. Do I need Consent Mode? A: Not for GDPR compliance for Ukrainian domestic users. However, if you run Google Ads campaigns with geotargeting that includes any EU/EEA country, those campaigns require Consent Mode for the EU portion of your audience.
Q: We have a Ukrainian company but are registered in Poland. Which rules apply? A: Your EU-registered entity (Polish company) is subject to GDPR and Polish UODO oversight. Google Ads campaigns run by that entity targeting EU users must comply with Consent Mode requirements. The June 15 change applies to your Polish entity's advertising operations.
Q: We target both Ukraine and Poland in the same campaign. How does Consent Mode handle this? A: Consent Mode is implemented at the site level, not the campaign level. The same ad_storage signal applies to all users. Polish users with consent banners will generate granted or denied signals. Ukrainian users without banners default to granted. Both are handled correctly by a single well-configured implementation.
Q: Does Ukraine's EU candidate status affect Consent Mode requirements? A: Not currently. Consent Mode requirements are based on current EU law, not candidate status. As Ukraine progresses toward EU membership, GDPR alignment will eventually become mandatory - but there is no current obligation for domestic Ukrainian traffic.
Q: We are a Ukrainian IT company with SaaS users across Europe. What is the minimum we need to do? A: Set up a CMP that shows a consent banner to users from EEA countries, configure it to send ad_storage signals to GTM, and ensure your Google Ads conversion tags require ad_storage consent. The June 15 change means this setup now determines whether your EU conversion data reaches Google Ads at all.
