Google Consent Mode Setup for Irish Websites

A cookie banner is easy to spot. A consent failure often sits behind it, hidden in tag settings, asynchronous scripts, and reports that seem more complete than they are.

For Irish businesses using GA4, Google Analytics or Google Ads, the consent state must reach Google’s tags before measurement begins. Google Consent Mode can help pass those choices to Google’s tags, but it doesn’t make an unclear banner lawful or permit non-essential tracking without consent.

The banner is only one part of a wider process. A consent management platform can record choices and support the visitor journey, while GDPR, ePrivacy rules and guidance from the Data Protection Commission still shape what Irish websites should do. This isn’t legal advice.

Start with a sound consent journey, then connect it properly to your tags.

Key Takeaways

• Google Consent Mode v2 passes four consent signals to Google tags: analytics_storage, ad_storage, ad_user_data, and ad_personalization.
• Set all four signals to denied before Google tags run, then update them immediately when a visitor accepts, rejects, or changes their choices.
• Consent Mode communicates consent but does not make consent lawful. Your banner, privacy notice, tag inventory, and withdrawal process must still meet Irish GDPR, ePrivacy, and relevant Google requirements.
• Basic mode blocks Google tags until consent, while advanced mode can send limited cookieless pings and support conversion modelling when storage is denied.
• Map and test every tag, including non-Google tools, and review the setup regularly as campaigns, platforms, and website functionality change.

Google Consent Mode for Irish websites: what it does

Google Consent Mode is a technical layer between your consent management platform (CMP), cookie banner, and Google tags. It tells Google Analytics, Google Ads, Floodlight, and related tags whether they may read or write cookies, use data for ads, or personalise advertising.

The system must receive a default consent state before Google tags run. It must then receive an update to the consent state when someone accepts, rejects, or changes their choices. Google’s Consent Mode implementation guide covers Google Tag Manager installations.

For an Irish site, Irish ePrivacy rules and GDPR form the core data privacy regulations for consent collection. Google’s EU User Consent Policy adds separate requirements for its advertising and measurement services. The website must meet both frameworks, but Consent Mode itself doesn’t provide lawful consent.

The four consent mode v2 signals

The system uses four core signals. Your CMP must map genuine visitor choices to these four consent signals.

The two newer signals, ad_user_data and ad_personalization, matter for advertisers with European Economic Area traffic. Google’s Tag Manager consent reference explains that ad_user_data affects measurement features such as Enhanced Conversions and tag-based conversion tracking.

Consent Mode is not a legal consent mechanism

Consent Mode records and communicates a choice. Your banner, privacy notice, tag inventory, and internal processes determine whether that choice was validly obtained.

A default setting of “denied” is only useful when it runs before tags send data and when the banner gives people a genuine, granular choice.

Keep analytics, advertising, functional tools, embedded media, and other purposes separate where they need separate consent types. Visitors should find rejecting non-essential cookies as straightforward as accepting them. They should also be able to withdraw consent later without hunting through a privacy policy.

Choose basic or advanced Consent Mode

Google Consent Mode offers two approaches, and both respect a denied consent state. However, they produce different measurement outcomes and require different implementation work.

Basic consent mode blocks tags first

Basic mode prevents Google tags from firing until a visitor grants consent. If someone rejects analytics or advertising cookies, relevant tags don’t send requests, and ad storage remains unavailable.

This is easier to explain and test. It also means Google Analytics and Google Ads receive less information from visitors who don’t consent. Reporting gaps can become large for sites with high rejection rates, particularly when paid media drives much of the traffic.

Basic mode suits organisations that want a block-first approach and can accept leaner reporting. It’s often the simpler choice when a website has limited tagging or a newly installed consent tool.

Advanced consent mode sends consent-aware pings

This approach loads Google tags with denied defaults. Rather than setting cookies after refusal, tags can send limited cookieless pings. This changes tag behavior without a full identifier-based hit, while eligible data may support conversion modeling.

That distinction matters because a limited request isn’t a full GA4 hit with persistent identifiers and advertising cookies. Denied settings may also restrict advertising-related fields through ads data redaction. This provides less data and doesn’t recreate every lost conversion. Where configured, URL passthrough can retain some paid-search click information when storage is denied.

Advanced mode can improve reporting continuity, but the default consent state must load before Google tag configuration. After a choice, the consent tool must update signals immediately. URL passthrough is an implementation setting, not proof of consent, and doesn’t guarantee complete attribution. For a useful technical comparison of the GA4 side, see this Consent Mode v2 setup checklist.

Map consent choices before touching Google Tag Manager

A working container cannot repair a vague privacy setup, and neither a cookie banner nor a consent management platform can replace an inventory. Begin with an audit of every technology that loads on the site, including apps, widgets, pixels, chat tools, video embeds, testing platforms, and tag templates.

Match purposes to the data you collect

List each tag, its supplier, purpose, consent types, and the category that controls it. A Shopify store may combine Google Analytics and Google Ads with Meta Pixel, Klaviyo, and review tools.

Google Consent Mode controls Google tags only, so map them separately from other vendors. Don’t assume one platform’s update controls Meta or TikTok; their tag behavior needs separate consent-aware rules.

Document what happens in each state:

• Before a choice, the consent state should keep non-essential tags blocked or limited to their denied configuration.
• After analytics-only consent, analytics tags may run with analytics storage granted, while advertising storage and personalisation remain denied.
• After full consent, approved analytics and advertising tags may use the permissions selected.
• After withdrawal, the consent state must ensure future tag activity reflects the changed preferences.

Apply regional rules with care

Ireland is in the EEA, so an Irish website should account for Google’s European consent requirements and relevant data privacy regulations. If your business also serves visitors outside Europe, regional defaults can support region specific behavior for different countries.

For a site aimed only at Ireland, a denied default across all four core Google consent categories is the clearest starting point. A site with wider traffic may set an Ireland-specific default with the IE region code and use a separate approach elsewhere.

IP-based location isn’t perfect. People travel, use VPNs, and cross borders. Build the consent experience around the visitor’s selected settings, because regional defaults can’t replace that choice.

Configure Google Tag Manager or gtag.js correctly

Google Tag Manager is usually the practical option for Irish marketing teams because it makes Google Consent Mode easier to inspect and maintain. It supports Consent Mode v2 for Google Analytics and other Google tags. Direct gtag js implementations can work well on smaller sites where developers control every script in the page head.

Set denied defaults before any tag can run

In Google Tag Manager, use a Consent Initialization trigger for the tag or template that sets the default consent state. This trigger runs before normal page triggers, including most Google tags.

Set analytics storage (analytics_storage), ad storage (ad_storage), ad user data (ad_user_data), and ad personalization (ad_personalization) to denied until the visitor chooses. These defaults also govern Google Ads advertising tags, so review each tag’s built-in controls and additional requirements. Tag behavior should match the consent types mapped to analytics, advertising, and other purposes.

For direct gtag js installs, place the consent default ahead of every config command. For advertising implementations, enable url passthrough only where your approved setup permits it. A typical Ireland-only default uses this pattern:

gtag('consent', 'default', {ad_storage: 'denied', analytics_storage: 'denied', ad_user_data: 'denied', ad_personalization: 'denied', region: ['IE']});

The exact code belongs in your developer implementation, not in an afterthought added below the tag. It sets technical defaults, but doesn’t establish lawful consent. However, url passthrough can preserve permitted click information; it can’t override a denied setting.

Update signals when the visitor chooses

Your consent management platform (CMP) must trigger a consent update after every meaningful choice. It uses the consent API to send relevant consent signals to Google. Each update must reflect the visitor’s current consent state.

For example, accepting analytics only should grant analytics_storage but keep both advertising-related signals denied. An all-purpose “accept” button can update all four signals, including the settings used by Google Ads, only if the visitor has been clearly told what each category covers.

A “reject all” action should send denied values. The preference centre must also send updates when people later change their choices.

Use a Google-certified CMP where possible, but still inspect its configuration. The CookieHub overview of 2026 Google changes is a useful reminder that a CMP update alone doesn’t prove each category, script, and tag is correctly mapped.

Test the visitor journey, not only the banner

A green consent dashboard doesn’t prove that Google Consent Mode flows correctly into Google Analytics, Google Ads, or a server-side container. Test like a visitor, then inspect network activity like a developer.

Run a full consent testing checklist

Run these consent checks in Google Tag Manager Preview and Tag Assistant on a staging site before every major release. Repeat them in an incognito browser to avoid old cookies affecting the result.

• Load the page with no stored choice and confirm the initial consent state has all four signals set to denied.
• Reject non-essential cookies and check that advertising and analytics cookies are absent or blocked as intended.
• Grant analytics only and compare tag behavior across GA4, advertising, and non-Google tags.
• Accept all categories and confirm approved tags receive the expected permissions.
• Withdraw consent through the preference centre, then refresh and confirm the updated consent state is retained and applied again.
• Check Tag Assistant’s Consent tab for the expected consent signals, then use the consent API to validate the update event and data passed to tags.
• Inspect browser storage and network requests in developer tools, looking for cookieless pings and unexpected data. For paid-search landing URLs, test url passthrough alongside the visitor’s recorded decision and attribution behaviour.
• Test checkout, cross-domain payment flows, booking engines, and single-page application route changes. For cross-domain checkout or booking flows, test url passthrough alongside the visitor’s recorded decision and attribution behaviour, not as permission to collect data.

GA4 DebugView can help validate event activity, while advertising diagnostics can highlight missing updates. Reports may include conversion modeling, so separate modelled results from observed consented conversions; keep screenshots or test records for complex launches and client handovers.

Fix common implementation failures

A frequent problem is a race condition. The consent tool loads slowly, while analytics or advertising tags fire immediately. Put the denied default in Consent Initialization or directly in the page head, then delay the tag configuration until that command has run.

Another problem appears on single-page applications. The first page may behave correctly, but later route changes fire events without retaining the visitor’s current choice. Developers need to persist that choice and reapply it when the app changes route.

Server-side tagging also needs attention. Moving processing server-side can reduce browser-side clutter, but it doesn’t remove consent obligations. Pass only the visitor’s permitted choice to the server container and stop it sending data that the visitor hasn’t authorised.

Keep Consent Mode accurate after launch

Consent setup is an operating task, not a one-off project. New campaigns, apps, checkout tools, and marketing pixels can change how Google Consent Mode works with Google Ads, Google Tag Manager, and Google Analytics.

Give the process clear ownership

Keep a simple register with the tag name, supplier, purpose, consent types, owner, implementation date, latest test date, and current consent state. Record separate owners where analytics, advertising, and functional purposes differ, plus url passthrough settings where used. Assign marketing ownership for campaign tags and developer ownership for templates, data layers, and container changes.

Review the register when adding a Shopify app, rebuilding a WordPress site, migrating domains, or launching a new paid channel. Recheck configured url passthrough and retest the consent state after campaign, domain, or landing-page changes. New custom HTML tags, Shopify apps, or WordPress plugins can change tag behavior and bypass controls that look fine in your dashboard.

Watch for reporting and policy changes

Compare consented traffic, conversions, and campaign performance over time, but don’t treat modelled conversions as the same as observed consented conversions. Record which reports include conversion modeling and explain the difference to stakeholders.

Google’s product rules, the DPC’s guidance, and wider data privacy regulations can change, as can the EU User Consent Policy. Platform or advertising requirements connected with the Digital Markets Act are separate from Irish GDPR and ePrivacy obligations, and aren’t the source of Irish consent law. Review your setup at least every six months, after meaningful platform updates, or whenever the consent interface changes. Reconfirm that choices remain clear, granular, and easy to withdraw through regular consent checks.

Frequently Asked Questions

What is Google Consent Mode?

Google Consent Mode is a technical layer that communicates a visitor’s consent choices to Google tags such as Google Analytics and Google Ads. It controls how those tags use storage, advertising data, and personalisation signals.

Does Google Consent Mode make an Irish website compliant?

No. Consent Mode records and communicates a choice, but it does not create lawful consent or replace a clear cookie banner and privacy notice. Irish websites must still consider GDPR, ePrivacy rules, Data Protection Commission guidance, and Google’s relevant policies.

What is the difference between basic and advanced Consent Mode?

Basic mode blocks Google tags until the visitor grants consent, which can lead to larger reporting gaps. Advanced mode loads tags with denied defaults and may send limited cookieless pings, allowing eligible data to support conversion modelling without creating the same data as consented tracking.

Which consent signals should an Irish website use?

Consent Mode v2 uses analytics_storage, ad_storage, ad_user_data, and ad_personalization. An Ireland-focused website will generally start each signal as denied and grant only the permissions covered by the visitor’s selected choices.

How should Google Consent Mode be tested?

Test the full visitor journey in Tag Assistant and Google Tag Manager Preview, including no choice, rejection, analytics-only consent, full consent, and later withdrawal. Inspect consent signals, browser storage, network requests, route changes, checkout flows, and non-Google tags rather than relying only on a green dashboard.

A consent setup that visitors and teams can trust

Google consent mode helps Irish websites respect visitor choices while retaining useful measurement. It works best with a clear journey, accurate tag mapping and tested tag behavior, including url passthrough where permission allows.

An accurate consent state starts denied and updates immediately when choices change. Regular consent checks build trust, while conversion modeling supports reporting continuity without making modelled results identical to observed consented conversions.