If you use the older synchronous ad tag (show_ads.js), then set the variable google_tag_for_under_age_of_consent=1 in every ad tag. For example: The following response from the publisher’s ConsentHref (https://publisher.com/api/check-consent) would enable restricted data processing for the AdSense ad request: { "promptIfUnknown": false, "sharedData": { "adsense-tfua": 1, "adsense-tfcd": 0 } } TFUA and TFCD can also be set statically on tags using the targeting JSON object as follows, for example: Finally, to help you comply with these requirements, note that data-block-on-consent can also be set for other AMP components that make requests to third parties, such as amp-analytics and amp-pixel.
Posts
Java script
If you use the older synchronous ad tag (show_ads.js), then set the variable google_tag_for_under_age_of_consent=1 in every ad tag. For example: tags supports marking requests for restricted data processing via the amp-consent component. That component allows the publisher to specify checkConsentHref, an endpoint that is queried before requests are sent from any component on the page that specifies the attribute data-block-on-consent. Read more about amp-consent and the format of ConsentHref responses If the publisher’s ConsentHref endpoint returns the keys "tfua" or "tfcd", subsequent AdSense requests will be marked for restricted data processing. For example, consider an AMP page with a consent component and an ad: The following response from the publisher’s ConsentHref (https://publisher.com/api/check-consent) would enable restricted data processing for the AdSense ad request: { "promptIfUnknown": false, "sharedData": { ...
