Hello, We’re using Piwik PRO Consent & Tag Managers, and we are running ads with Google Ads. We’re using the built-in Google Ads conversion & remarketing tags. As Google announced the release of its new Consent Mode, it’s clear that this is will soon be mandatory for advertisers to use it (by March 2024): Google announces Consent Mode v2 - What does it mean?. I don’t think Piwik PRO is a certified Google CMP partner: https://cmppartnerprogram.withgoogle.com/. How can I implement Google Consent Mode using Piwik PRO Consent & Tag Managers? Thank you very much!

Update I used Google’s documentation: Administrar la configuración de consentimiento (Web) | Security and Privacy hub | Google for Developers. By following gtag.js method, you should be able to install Consent Mode with Piwik PRO Tag & Consent Managers. Make sure you trigger the tags in the correct order: default values first. You can verify your implementation following these instructions: Manage consent settings (web) | Security and Privacy hub | Google for Developers. I personally used the Network tab & Google Tag Assistant to check my setup. I hope this will help!

Hello @Thomas_Anode_FR Did you have a look at this : [image] Google consent mode integration | Piwik PRO help center From November 2020, Google ads are displayed only to visitors who have consented to analytics and advertising cookies. They won’t pop up if the visitor hasn’t given their consent. Google relies on two consent mechanisms: IAB TCF 2.0 and Google... Est. reading time: 4 minutes

Hello @romainproximity, I did, but I think that following Google’s guidelines is better. The main reason is that it clearly invites you to set default values to “denied” first. It is not the case in this Piwik PRO’s tutorial: it’s only update commands. Additionally, Google’s guidelines integrate the new parameters “ad_user_data” and “ad_personalization”. I think Piwik PRO documentation would benefit from a little update. :slight_smile:

[image] Thomas_Anode_FR: I think Piwik PRO documentation would benefit from a little update. Hey everyone, sorry for not responding earlier - we are working on an update :saluting_face:.

[image] Google consent mode v2 integration | Piwik PRO help center According to Google’s policy, Google ads are displayed only to visitors who have consented to analytics and advertising cookies. They won’t pop up if the visitor hasn’t given their consent. Google relies on two consent mechanisms: IAB TCF 2.2 and...

Hi @anthonybartczak , The first step to integrate Google Consent Mode v2, with all the denied default. It must be on the webpages code, or can it be a tag in Tag Manager ? Thanks for your help,

Hi @christophe.henaff, In my opinion (and Google’s documentation mentions this method) it’s best to embed the defaults directly in your website, before any tag managment or tracking tool is loaded. It’s the safest way because it skips potential issues with 3rd party tools.

I think any TMS should be capable of setting Consent defaults, even Piwik’s. And maybe I misunderstand how Piwik’s Consent Manager works, but Google consent mode v2 integration | Piwik PRO help center mentions we should update the Consent Manager defaults when the Event is stg.consentDecisionMade. But doesn’t that apply only to the rare cases when somebody first gives their consent (or even rarer, when they update consent)? => If we only use that stg.consentDecisionMade Event, there will be no Consent given for any Pageviews where there was no interaction with the Consent Manager (=99% of Pageviews)… The documentation is missing the crucial info that the update command needs to be fired on every pageview (or that the Consent “default” settings need to reflect the user’s current consent state on every page). Last question: When I try to get {{ Consents }} via a Custom HTML Tag, it always refers to window.sevenTag.getVariableValue('Consents', 3). This 3 refers to t.variables[3][“Consents”] which sometimes contains a filled Consents object, but also sometimes not… [image] E.g. here (trying to receive “Consents” with the stg.consentDecisionMade Event: Consents.current_state is just an empty object → setting Consent Mode via the googleConsentModeMapping function from the documentation fails (everything gets “denied”… [image] Why does a reference to a Variable not always get the latest version of it? (=which would contain the correct values) [image]

Looking at this again, it seems like PP TM, when 'eval’ing the Custom HTML Tag (with all comments, yikes, performance anyone?!), injects the INDEX of the data layer event that triggered the current tag into the window.sevenTag.getVariableValue('Consents', INDEX);call. So if a tag has multiple triggers (like stg.pageView OR stg.consentDecisionMade, the value counts that was in the data layer when the tag was first called… So if stg.pageView is the 3rd event (INDEX = 3) and stg.consentDecisionMade the 22nd (INDEX = 22), Piwik TM will still get the data of the Consents variable as it existed when the 3rd event happened… So when somebody updates their consent level, this will never make it to the Google Consent Mode update as it will “update” it based on data layer INDEX 3 again (when Consent still did not exist)… That is totally not how I expect a Variable reference to work. In GTM, it always takes the last value… I will have to re-visit quite some code now that I found this out… I will replace Variable reference by this manual call now which always gets the latest version of a Variable: window.sevenTag.getVariableValue('Consents', dataLayer.length); But this should not be necessary…

[image] loldenburg: I think any TMS should be capable of setting Consent defaults, even Piwik’s. It’s not about ability, it’s just recommended. See my answer here: [image] Google Consent Mode: analytics_storage denied Data collection and tags That was one of the reasons why we didn’t include the defaults in the code. We didn’t want to skip the defaults part in case there is a failure with the Piwik PRO container (e.g. outage, blocking) We wanted them (the defaults) to be on top of any potential tool that could either make use of them or modify them. As you’ve mentioned - it’s of course possible to add those in the integration tag but we can’t really advise on doing so because of the mostly asynchronous manner of Piwik PRO Tag Man… [image] loldenburg: And maybe I misunderstand how Piwik’s Consent Manager works, but Google consent mode v2 integration | Piwik PRO help center mentions we should update the Consent Manager defaults when the Event is stg.consentDecisionMade. But doesn’t that apply only to the rare cases when somebody first gives their consent (or even rarer, when they update consent)? => If we only use that stg.consentDecisionMade Event, there will be no Consent given for any Pageviews where there was no interaction with the Consent Manager (=99% of Pageviews)… And also the page view event [image]

Google Consent Mode with Piwik PRO Consent & Tag Manager

Privacy

anthonybartczak March 5, 2024, 7:28pm 11

It’s not about ability, it’s just recommended. See my answer here:

And also the page view event

Topic		Replies	Views
Add Google AdSense with PIWIK PRO tag manager Data collection and tags	22	951	June 13, 2022
Google Consent Mode with GTM Privacy	4	1023	June 21, 2023
Consent Mode & Data modelling Piwik Privacy	2	270	February 1, 2024
Piwik Consent Report Privacy	8	383	January 26, 2024
Google Consent Mode: analytics_storage denied Data collection and tags	18	2380	February 13, 2024

Google Consent Mode with Piwik PRO Consent & Tag Manager

Related topics