ampproject / ampproject/amphtml

[amp-consent] Fine grain, client-side consent

Open
#26,735 30 comments 2 reactions 1 assignee Claimed by @micajuine-ho View on GitHub
Component: amp-consent Stale Type: Feature Request WG: analytics
Dominant language
JavaScript
Stars
14.9k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

Some publishers may want to implement fine grain consent on cookies, discriminating between analytics, marketing, etc. An example of this is what The Guardian is dong today:

![image](https://user-images.githubusercontent.com/868584/74238589-050e0400-4cce-11ea-8e2d-cdb3f0c382af.png)

Would it be possible to implement this in AMP? The only two ways I can think of are
1. implementing N amp-consents, which wouldn't be practical, as the UI would be messy
2. Using `sharedData` in amp-aconsent, but this would require defining an endpoint to manage the satate of the consent, which is a high bar for something that was not requirirng an endpoint untill now.

Is there any other way of implementing this fine grain consents? in AMP, client-side only? If there it isn't, could this be considered an FR?

Thanks,

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.