Matomo Tag Manager & Google Consent Mode v2 – How to properly handle consent signals from a CMP?

General questions
1

Hi,

We are currently working on implementing Google Consent Mode v2 using Matomo Tag Manager (self-hosted) combined with Cookiebot as our CMP. The Cookiebot configuration has been validated by their support team — the consent signal is correctly emitted from the start.

The issue we are facing is not on the CMP side, but rather on how Matomo Tag Manager interprets and acts on these consent signals to control Google tags (Google Ads, GA4, etc.).

Unlike Google Tag Manager, which natively supports consent checks through “Additional Consent Checks” and built-in consent type variables, Matomo Tag Manager does not seem to offer an equivalent native mechanism to map CMP consent states to Google tag firing rules.

To summarize the situation:

  • Cookiebot correctly exposes the consent state (accepted/declined per category)

  • The challenge is how Matomo Tag Manager should technically consume this signal to ensure compliant firing of Google tags in Advanced Consent Mode v2

We would like to avoid relying solely on custom JavaScript workarounds without knowing if there is an official or recommended approach from the Matomo team.

Our questions:

  1. Does Matomo Tag Manager natively support Google Consent Mode v2, and if so, how?

  2. What is the recommended way to bridge a CMP’s consent signal (e.g. Cookiebot) with Google tag firing in Matomo Tag Manager?

  3. Is there an official template, trigger type, or documentation covering this use case?

Any guidance or pointer to existing documentation would be greatly appreciated.

Thanks in advance.

1 Like