The AMP Project Roadmap
- Add an analytics trigger for when the user education overlay is shown (#15420)
- Add an analytics trigger for when the video spinner is shown
At the moment, consent within amp-consent is binary. Either the user can accept consent for all vendors on the page or reject consent for all vendors on the page. This feature provides the ability for a user to accept or reject consent on a per vendor basis. Further, this could also be enhanced to support consent on a per vendor and per purpose basis. for e.g. a user should be able to give consent at a granular level to Vendor A for the purpose of analytics but reject consent to Vendor A for the purpose of ads. Master issue is #15651
This is a master issue to track the second phase of amp-consent which focuses on more advanced use cases of amp-consent. All active features in discussion from the initial amp-consent [implementation] (#13716 ) have been moved to this issue.
This feature will enable a publisher to incorporate amp-consent related status information via AMP's substitution variable framework (originally proposed here).
We intend to implement a link decoration based solution for AMP pages to sync IDs across domains.
Bring the feature described in #13716 into amp-story.
<amp-consent>component that enables publisher to get consents from readers and manage their consents.