How to comply with Google Consent Mode v2 before June 2026

Starting June 2026, Google requires every site using Ads or Analytics in the European Economic Area to send valid consent signals through Consent Mode v2. If your site doesn't send them, Google stops receiving conversions and remarketing shuts down.

What exactly changes

Consent Mode v2 adds two new parameters on top of the existing ones:

• ad_storage and analytics_storage — the classics.
• ad_user_data — whether user data can be sent to Google.
• ad_personalization — whether personalization and remarketing are allowed.

That's 7 signals in total, and they must be set before any Google tag runs.

Order matters

The default state must be declared in GTM's Consent Initialization, at the highest priority. If it arrives late, Google already fired its tags without consent.

Conma solves this by injecting the snippet synchronously as the first tag, and updating the state in under 500 ms once the user decides.

Quick checklist

1. Detect every tracker currently on your site.
2. Declare the 7 parameters as default before loading Google.
3. Update them to granted/denied based on the user's choice.
4. Store a signed certificate of each consent.

With Conma, all four steps are covered in a five-minute setup.