If you run an Irish business and use Google Ads or Google Analytics, your digital marketing ecosystem faces its strictest compliance environment yet. While the mandate for Google Consent Mode v2 technically went into effect in March 2024, a major architecture shift by Google in June 2026 has made proper implementation a survival requirement for your ad performance.
Google Consent Mode v2 is an API mechanism that acts as a bridge between your website's cookie banner and Google's tracking tags. It does not replace your cookie banner; instead, it dynamically tells Google exactly what level of data tracking a user has explicitly permitted.
Google introduced v2 largely in response to the EU Digital Markets Act (DMA), which places new obligations on large platforms to ensure user consent is properly signalled. In practice, this means advertisers now need to pass two additional consent parameters for their tracking to function correctly:
ad_user_data: Signals whether user data can be sent to Google for advertising purposes.
ad_personalization: Signals whether user data can be utilized for targeted remarketing.
Many businesses previously relied on account dashboard settings, like 'Google Signals' inside Google Analytics 4 (GA4), to manually override or stitch together their tracking gaps. However, as of June 15, 2026, Google officially removed Google Signals as a data-sharing control for Google Ads.
In practice, Google Ads now relies heavily on the consent signals coming from your website code. If a user denies tracking or your setup is misconfigured, Google loses visibility into that session. Over time, this erodes your remarketing audiences, degrades conversion measurement, and starves Smart Bidding of the data it needs to optimise effectively.
When updating your website, you must choose between two distinct tracking setups, each offering drastically different data outcomes:
In Basic Mode, Google's tracking tags are completely blocked from loading until a user explicitly clicks 'Accept' on your banner. If they click 'Deny,' no data is transmitted whatsoever. While highly conservative from a privacy standpoint, this results in total data blackout for a large percentage of your web traffic.
In Advanced Mode, Google tags load immediately when the page opens, but with tracking permissions preset to 'denied.' If the user rejects cookies, the tags automatically adapt, stripping away personal identifiers and sending anonymous, 'cookieless pings' to Google. This baseline stream of anonymous data gives Google Ads and GA4 the necessary signals to run conversion modeling, allowing their AI to accurately estimate and recover missing sales data.
While Advanced Mode allows Google to model missing data using machine learning, it is not a magic switch. Google requires a minimum volume of observed data before it can reliably model the rest. Accounts with very low traffic or infrequent conversions may not see modelled data fill the gap immediately, so the benefit scales with your overall ad activity.
Route 1: Google-Certified CMP (Safest): The most practical approach for most Irish SMEs is to deploy a Google-certified Consent Management Platform (CMP) such as Cookiebot, Consent Manager, or CookieScript. These tools integrate natively with Google Tag Manager (GTM) and dynamically pass the correct v2 parameters out-of-the-box.
Route 2: Custom GTM Deployment: For larger or custom-built platforms, developers can deploy Consent Mode v2 manually inside Google Tag Manager. This involves adjusting default container consent states via custom code templates and triggering explicit state updates once a user interacts with the interface.
No. Your cookie banner collects consent from users. Consent Mode v2 is what communicates that consent choice to Google's tags so they behave accordingly.
With Advanced Mode, Google still receives anonymous pings that allow it to model conversions. With Basic Mode, denied users produce zero data.
Not necessarily. If you use a Google-certified CMP like Cookiebot, setup can be handled through their dashboard or a plugin. Custom GTM deployments typically do require a developer.
Consent Mode v2 is a Google-specific mechanism. Meta has its own requirements around the Conversions API and Limited Data Use settings, which are separate.