Shihua Zheng

@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.

This contribution is undergoing review.

Proposed example of permissible picture tag ``` ``` Background In the earlier versions, AMP mandated use of an [amp-img element](https://amp.dev/documentation/components/amp-img) to display images. The element incorporates essential features necessary for...

I think you would also need to modify ads/_config.js and add a new vendor js in ads/vendors/selectmedia.js

Your approach should work. However, that would require all consent platforms on AMP to make changes to their API to accommodate, and the timeline will be long. Alternatively, if it...

Given that this approach requires platform support, cc'ing all the existing platforms here for inputs: @dav-m85 @janwinkler @carsten1980 @MaximePlancke @yotam-g @Vasile-Peste @nielsbaarsma @oliverfernandez @PierigOgury @gramesan @heikostaab @marco-prontera @nicobatalla @RemiSirdata @molz...

If any one of you have more contacts within these CMPs, feel free to escalate the issue through them as well (since github users might not be the responsible person...

@bretg Can you substantiate your use case of gppSid meta? My undetstanding is that one GPP string could have multiple sections and each would have its own SID.

@bretg https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/blob/main/Core/Consent%20String%20Specification.md Okay, you meant the GPP_SID at the bottom of the page. It makes sense but I did not see that macro.

@bretg We are going to proceed with this proposal. There are several downstreams (receivers of consent strings in AMP) that we are prioritizing to add support for GPP, and then...