How to Implement Google Consent Mode v2 on EU and UK Websites

Google Consent Mode v2 allows supported Google services to adjust their behaviour according to a visitor’s consent choices. For websites using GA4, Google Ads, remarketing or conversion tracking, a reliable implementation must coordinate the consent banner, tag configuration and consent signals.

This guide explains the practical implementation process for EU and UK websites. It is not legal advice. Neither Consent Mode v2 nor a consent management platform (CMP) guarantees compliance on its own. Your legal basis, privacy information, vendor list and technical configuration may require professional review.

How Google Consent Mode v2 works with a CMP

A CMP presents consent choices and records visitors’ selections. Consent Mode v2 communicates the resulting consent states to supported Google services.

Your CMP and tag setup should map visitors’ choices to the relevant signals:

• ad_storage
• analytics_storage
• ad_user_data
• ad_personalization

Area	Question to check	Implementation consideration
Banner wording	Are the choices clear and accurate?	Use understandable labels and categories that reflect the website’s behaviour
Default state	Are signals set before Google tags initialise?	Configure the intended defaults early in the page-loading sequence
Consent update	Are signals updated after a choice?	Map each CMP category to the relevant signals
Script control	Do optional tags follow the choice?	Review blocking rules, triggers and category mappings
Documentation	Can the team reproduce the setup?	Keep configuration details and test results

Consent Mode v2 is a signal framework, not consent itself. It does not replace an appropriate visitor choice mechanism, accurate privacy information, script controls or legal review.

Recommended implementation order

1. Inventory GA4, Google Ads, GTM, conversion linker and remarketing tags, embedded media, ecommerce plugins and custom scripts.
2. Classify each service using clear categories such as necessary, analytics, marketing or preferences.
3. Set the intended default Consent Mode states before affected Google tags initialise.
4. Map CMP categories to ad_storage, analytics_storage, ad_user_data and ad_personalization.
5. Configure optional scripts and tags to follow the corresponding choices.
6. Update consent states when visitors accept, reject or revise their preferences.
7. Test every available choice in a clean browser session and retain the results.

For a detailed GTM walkthrough, see the guide to setting up Google Consent Mode v2 in Google Tag Manager.

Google Tag Manager checklist

When using GTM, review:

• Consent Overview and each tag’s consent settings.
• Consent initialization and trigger order.
• Default states before the visitor chooses.
• Updates after acceptance, rejection and preference changes.
• The behaviour of GA4, Google Ads, remarketing and conversion linker tags.
• Embedded media and custom HTML tags that may load additional resources.

Enabling Consent Mode in an administration interface is not enough to verify the implementation. Check what actually happens in the browser before and after each available choice.

How to test Consent Mode v2

Use a clean browser profile or private session for each test. Inspect cookies, browser storage and network requests while testing:

1. A first visit before any choice.
2. Rejection of optional categories.
3. Acceptance of all categories.
4. Acceptance of analytics without marketing, and vice versa if offered.
5. A later change to saved preferences.

Repeat these checks after deployment and after material changes to campaigns, plugins, embedded media or tags. Browser evidence is more informative than a banner screenshot because it shows whether technical behaviour matches the selected preference.

Records and ownership

Keep records of the banner wording, category mappings, vendor list, implementation date, configuration and test results. This information can help identify whether a later issue comes from CMP settings, GTM sequencing, consent text or a newly introduced script.

If an agency or several internal teams manage the website, document who owns the CMP, GTM container, privacy content and quality assurance process.

Common implementation mistakes

• Initializing tags before default consent states are established.
• Treating Consent Mode as the visitor’s consent rather than a way to communicate consent states.
• Omitting ad_user_data or ad_personalization from the mapping.
• Using vague categories that do not reflect actual website behaviour.
• Testing acceptance but not rejection, partial choices or preference changes.
• Failing to retest after adding a plugin, campaign or tag.

EU and UK considerations

Consent Mode v2 should be configured alongside the privacy and cookie requirements that apply to your organization and visitors. Useful reference points include the European Data Protection Board, the UK Information Commissioner’s Office, the European Commission’s data protection guidance and Google’s Consent Mode documentation.

Use clear labels such as “Accept,” “Reject,” “Analytics” and “Marketing” only where they accurately describe the available choices and resulting website behaviour. The appropriate wording and consent mechanism depend on the technologies used and the requirements applicable to the website.

Evaluating a CMP for Consent Mode v2

When evaluating a CMP, check whether its available configuration fits your tag structure, vendors and consent categories. CookiePilot presents features for managing consent choices and integrating them with website scripts and Consent Mode v2; these functions should be validated against your specific implementation requirements.

Review the CookiePilot feature overview and documentation to assess the available setup options.

FAQ

Does Google Consent Mode v2 make a website compliant?

No. It allows supported Google services to respond to consent signals. Compliance depends on the applicable requirements and the website’s wider legal and technical implementation.

Does Consent Mode v2 replace a cookie banner?

No. Consent Mode v2 does not provide the visitor-facing choice mechanism. Whether and how consent must be requested depends on the technologies used and the rules applicable to the website and its visitors.

Can Consent Mode v2 be implemented through GTM?

Yes. The sequencing matters: set default consent states before affected tags initialize, then send updates after the visitor makes or changes a choice.

What should teams test first?

Start by checking which tags and network requests occur before the visitor makes a choice. Then test rejection, acceptance, partial selections and later preference changes.

Next step

Before deploying Consent Mode v2, document your intended defaults and category mappings, then test each visitor choice in the browser. If you are assessing CookiePilot for this setup, compare the documented features with your website’s tags, vendors and implementation needs.