Amphtml: CMP / Funding Choices for AMP

Created on 4 Nov 2020  路  16Comments  路  Source: ampproject/amphtml

Hi, we are working on converting all our sites to AMP responsive tech, for desktop / mobile users. We are using Adsense and Ad Manager, and we have some issues with the update of the rules regarding consent for advertising. As we still have some desktop sites in standard HTML, our Google Account Manager suggested that we use the Funding Choices CMP script. This solution is great as really simple to implement.

On the other hand, we have been searching for a simple CMP solution for AMP. Right now, there are only some CMP for AMP commercial solutions (expensive). How come Google is working so hard on pushing AMP and does not provide a turnkey solution for AMP CMP based on Funding Choices. When could we expect such AMP CMP solution ? Indeed, we adopted your AMP solution really early (2017) and this situation with CMP is like a brick wall for us.

amp-consent Feature Request components

Most helpful comment

Related? #26229 - if TCFv2 support isn't even ready for AMP, I don't see how Funding Choices can be. Google is about to stop serving ads in the EEA on sites that don't support TCFv2 on Nov 15, but don't have an official solution for AMP?

Hi @archon810, while Funding Choices has not integrated into AMP yet, we do support TCFv2 with other CMPs (or through your own implementation): https://github.com/ampproject/amphtml/blob/master/extensions/amp-consent/amp-consent.md#does-amp-support-the-iab-tcf

Please let me know if you need any more clarification around this subject.

Hi, thank you for your reply. To tell you the truth, we need a plug and play CMP solution for AMP not a pain in the neck nightmare to develop (meaning countless hours to dev / test and no guaranties it'll work at the end...). AMP is supposed to be a simple solution ;) Funding Choices for AMP is a must have features for all people like us here who are deeply involved in pushing this tech on ours sites. Thank you in advance ;)

All 16 comments

@jeffjose FYI

+1. We're also adding Funding Choices and need a solution for AMP.

Related? https://github.com/ampproject/amphtml/issues/26229 - if TCFv2 support isn't even ready for AMP, I don't see how Funding Choices can be. Google is about to stop serving ads in the EEA on sites that don't support TCFv2 on Nov 15, but don't have an official solution for AMP?

Hello!
Google Choices should absolutely support AMP.
It should be "a must", as AMP is also sponsored by Google.

Hello,
also for us it is very important .
+1. We're also adding Funding Choices and need a solution for AMP.

Related? #26229 - if TCFv2 support isn't even ready for AMP, I don't see how Funding Choices can be. Google is about to stop serving ads in the EEA on sites that don't support TCFv2 on Nov 15, but don't have an official solution for AMP?

Hi @archon810, while Funding Choices has not integrated into AMP yet, we do support TCFv2 with other CMPs (or through your own implementation): https://github.com/ampproject/amphtml/blob/master/extensions/amp-consent/amp-consent.md#does-amp-support-the-iab-tcf

Please let me know if you need any more clarification around this subject.

Related? #26229 - if TCFv2 support isn't even ready for AMP, I don't see how Funding Choices can be. Google is about to stop serving ads in the EEA on sites that don't support TCFv2 on Nov 15, but don't have an official solution for AMP?

Hi @archon810, while Funding Choices has not integrated into AMP yet, we do support TCFv2 with other CMPs (or through your own implementation): https://github.com/ampproject/amphtml/blob/master/extensions/amp-consent/amp-consent.md#does-amp-support-the-iab-tcf

Please let me know if you need any more clarification around this subject.

Hi, thank you for your reply. To tell you the truth, we need a plug and play CMP solution for AMP not a pain in the neck nightmare to develop (meaning countless hours to dev / test and no guaranties it'll work at the end...). AMP is supposed to be a simple solution ;) Funding Choices for AMP is a must have features for all people like us here who are deeply involved in pushing this tech on ours sites. Thank you in advance ;)

Hi @micajuine-ho do you have any example of custom amp consent implementation that supports TCFv2?

@maciejmackowiak It's hacky, but works and is compliant https://community.cookiepro.com/s/article/UUID-94cf9b13-1998-d989-a5e0-d01a73a2e0a7

Hi @maciejmackowiak I assume by 'custom implementation' you mean that you are not working with a CMP. Is that correct?

Thanks @sankalpsans I will take a look into it.

@micajuine-ho yes and no - for AMP currently we have basic <amp-consent> implementation without CMP, and for non-AMP we are using google funding choice.

This raises two questions:

  1. Is there a way to have custom AMP implementation without CMP that will support TCFv2?
  2. Maybe the solution @sankalpsans mentiond is possible to implement with google funding choice using an <iframe> and then pass the cookies?

Is there a way to have custom AMP implementation without CMP that will support TCFv2?

If you are able to create a TC String, you can pass that along through amp-consent (via checkConsentHref) to be passed along to vendors (who will decode it and decide what to do with the request).

The amp-consent config will loosely look like this:

{
   consentRequired: 'remote',
   checkConsentHref: "your-endpoint-that-returns-a-tc-string",
   promptUi: "inline-prompt-ui-id"
}

More information on the checkHrefResponse can be found here.

Maybe the solution @sankalpsans mentiond is possible to implement with google funding choice using an