ampproject / ampproject/amphtml
amp-ad still serves cookie _ga and AMP-Token after rejecting cookie consent
Open
Type: Bug
WG: components
WG: monetization
- Dominant language
- JavaScript
- Stars
- 14.9k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
So the amp-ad data-block-on-consent does not seem to work properly as the amp-analytics connected with the amp-ad (adsense + double-click) is loaded after rejecting the cookie consent so a _ga and a AMP-Token is added as a cookie on the site.
Is this normal behavior and according to GDPR, CCPA? I do not think so.
Contributor guide
Assessment
This issue has not been assessed yet.