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:
Would it be possible to implement this in AMP? The only two ways I can think of are
- implementing N amp-consents, which wouldn't be practical, as the UI would be messy
- 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,
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:
Would it be possible to implement this in AMP? The only two ways I can think of are
sharedDatain 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,