ampproject
Google Consent Mode V2
Description
Hopefully I haven't missed something obvious in either the documentation, functionality or issue tracker but do you know if amp consent will support Google Consent Mode V2 and the two new consent purposes they have added?
ad_user_data & ad_personalization
https://support.google.com/tagmanager/answer/13695607?hl=en
Alternatives Considered
Not aware of any alternatives, we have updated our CMP template on GTM to cover non-amp pages
Additional Context
At the moment we use amp-consent for Statistics and Marketing but couldn't see any updated documentation around the new consent purposes.
@powerivq could you take a look at this? would this be new implementation needed or does our current implementation cover this scenario?
Although I am not working on Google Ads, I think this document says that you should set up all purposes from your CMP, and granular consents will be passed through as a consent string and be processed by the Google Ads.
Thanks for the feedback on this one, we already updated our CMP template on Google Tag Manager as we work with Cookiebot for consent mgmt, so we should be fully compliant on non-amp pages. I've just sort of guessed that for our AMP consent we just added these other two consent purposes...any thoughts on whether this is right or totally wrong would be great.
"purposeConsentRequired": ["purpose-analytics", "purpose-marketing", "purpose-user_data", "purpose-personalization"]
So we have another couple of checkboxes on our consent form -
<label class="consentLabel" for="consent-purpose-user_data" style="color: grey;"> <input id="consent-purpose-user_data" type="checkbox" on="change:siteConsent.setPurpose(purpose-user_data=event.checked)" /> User Data </label> <label class="consentLabel" for="consent-purpose-personalization" style="color: grey;"> <input id="consent-purpose-personalization" type="checkbox" on="change:siteConsent.setPurpose(purpose-personalization=event.checked)" /> Personalization </label>
@StuartPaterson purposeConsentRequired seems right. As to the consent screen HTML, I have no knowledge as to your specific CMP and the CMP is probably your best resource.
@powerivq purposeConsentRequired is the part we already know to be correct as this is specified on the amp-dev documentation.
This post is more about the 'consent purposes' within the purposeConsentRequired array, in regard to the new consent types introduced by Google Consent Mode V2, as mentioned in my original query.