rez0rat
Forum Replies Created
-
Hi
it’s work now for me by adding the function below in ads-functions.php :
add_action(‘ampforwp_before_head’,’amp_cmp_tcf2′);
function amp_cmp_tcf2() { ?>
<script async custom-element=”amp-consent” src=”https://cdn.ampproject.org/v0/amp-consent-0.1.js”></script><script async custom-element=”amp-auto-ads” src=”https://cdn.ampproject.org/v0/amp-auto-ads-0.1.js”></script><script async custom-element=”amp-sticky-ad” src=”https://cdn.ampproject.org/v0/amp-sticky-ad-1.0.js”></script><meta name=”amp-consent-blocking” content=”amp-auto-ads,amp-ad,amp-sticky-ad”>
<?php
}I have to wait a few days to see if the errors ( Google Errors 1.1/2.1a ) go away or not from adsense console.
Thanks you for your great ampforwp plugin,
Hi Ahmed,
Thank you first for suggestion, but this option is not approved by the IAB Europe Transparency & Consent Framework in v2 version. All users in europe will have TCF v2 & Google Errors 1.1/2.1a in adsense console.
that’s why we are using a third party script like sirdata or quantas.
to adapt your GPDR option, take a look at https://cmp.sirdata.com/#/google-tcf-errors.
So for my probleme, the custom-element=”amp-consent” exist already in header that’s why it disapears i think, and i’m looking now to change its place in header (more higher) to work perfectly.
img : https://postimg.cc/jLMRVfn8
think you.
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] 2 errors : meta name & AMP componenthi
i have same probleme, can’t put sirdata cmp code in AMPforWP.
just to be clear, i have to add 2 lines in amp header to work fine:<script async custom-element=”amp-consent” src=”https://cdn.ampproject.org/v0/amp-consent-0.1.js”></script>
<meta name=”amp-consent-blocking” content=””>the first line of code disappears because this tag :custom-element=”amp-consent”
Any solutions ?
Thx for you help !
- This reply was modified 5 years, 5 months ago by rez0rat.