This is the second post I've seen here today with this problem, so it may be just another Gglitch? See it at [webmasterworld.com...]

Ya, I got that msg too for a couple of sites that have been running the Google CMP for time. Revisited the settings, set all to on, and will just wait to see if the msg goes away.

I'm thinking false positive?

"I'm thinking false positive? "

I think so too...

Greetings
Milanex

Wish there was a Review option somewhere just to help clear the clutter sooner.

I contacted support with the question of what is happening here and how is it possible to get a 'Certified CMP not adopted' policy violations warning for CMP from Google Adsense itself?

Me too!

"One or more of your sites has been in violation of AdSense policies."

I've had the Google CMP running absolutely fine since May... then a few days ago the CMP suddenly stopped appearing on my sites, despite the CMP status still declared 'published' in the Adsense console.

So... I created a new Google CMP message and published it but it's still not showing on my sites.

I assume it's a bug.

Definitely a bug. When I click to to see the list of sites affected, AdSense interface shows a few sites starting with www. and also subdomain. ; but when I am shown the list of all my sites, the sites which are supposedly "affected" appear in the list of compliant sites without the subdomain part.

I just received a reply, which shows that everything about this is an unknown, a confusion and that it is still waiting for clarification.

"Thanks for reaching out!

We are currently checking with our specialist team and will get back to you with a response once we have an update to share.

Thanks for your patience and understanding. "

@dolcevita, funny, that's just about the same response I get from everyone about anything when I ask for help with some sort of problem I'm having. Translated: we don't know, don't really care that much and will stall using meaningless words as long as we can. And have a nice day.

I think this is all related to TC string error 3.3, where Google CPM detects that the consent in the TC string is older than 13 months, but does not offer the possibility, nor does it automatically delete the same and then ask for re-consent.
Issue with IAB TCF 3.3 (part 1):
[webmasterworld.com...]

There is the main problem in my opinion for the constant TC string 3.3 error with certain EU visits, as well as this policy violations from yesterday.

Now I wonder why Google CPM doesn't automatically delete consent older than 13 months and ask for a new one from the visitor?

Issue with IAB TCF 3.3 (part 2):
[webmasterworld.com...]

On several websites, only one has the warning.
What is different? Old ad unit code in very old content i forgot to change?
Could this be the cause of the warning?

Warning have Ad serving at risk 0% 6.5K ad requests
Regular ad serving 100% 1.39M ad requests

Seems only some ads at risk,

Or, maybe, 6k5 are EEA UK ads

I think dolcevita is right: this has alot to do with the TCF string (which I think is out of our control?).

Of all my sites, just two are affected by this in the downloadable reports and those two are the only sites flagged by the Adsense Policy Center. They also see quite a bit of European traffic - like 20%.

Seems like the kids at Google flipped a switch and weren't prepared for what was coming. I assume that's why they delayed enforcement into February.

@CommandDork

I am currently testing a script, which receives the TC string from the Funding Choices cookie and if it is older than 12 months, automatically deletes it, which will then enable re-consent and thus send a 3.3 error, as well as a policy violation "Consent requirement: Certified CMP not adopted" (which is most likely related to this) into oblivion.

Adserving at rix dropped since 13 Dec from 11% to 6%, last detected 3.3 error was om 12/12/23 but i'm still not sure of script works or not.

It will take another 5-7 days for me to be able to confirm whether it works or not.

Dolcevita i have a script to avoid 3.3 error and is not the issue.

@ruip

Two questions:

1) Since when do you use script? Do you still have TCF string 3 3 error reported by adsense for certain domain?

2) Do you have policy violaton "Consent requirement: Certified CMP not adopted"?

I've been using the script since September or August, I don't remember exactly. No 3.3 errors since working, not all my sites have this script, and, 3.3 not affect normal revenue, seems this a glicth from one or other advertiser corrected couple of days later with a few ads display.
Error is "Consent requirement: Certified CMP not adopted".
There is a change since yesterday. Yesterday it had 6.5K and 1.39M
Today have 5.6K (ad requests affected) 1.29M (Regular serving)
This is for the last 7 days report, maybe we need a week or so for changes take effect.
The only change I made was in ads with the old code and resubmitted the gdpr messages again
Let's wait and see.

This is script i use
<script>
// Delete the Funding Choices cookie if consent is more than 12 months old
try {
const nm = "FCCDCF"; // Match name of Funding Choices cookie
const dm = "xxxxxxxxx.com"; // Match domain of Funding Choices cookie
const pa = "/"; // Match path of Funding Choices cookie
let tc = ('; ' + document.cookie).split('; ' + nm + '=');
if (tc.length === 2) {
tc = decodeURIComponent(tc.pop().split(';').shift());
tc = JSON.parse(tc)[3][0].substring(1,9);
tc = Uint8Array.from(window.atob(tc), (v) => v.charCodeAt(0));
let dt = (tc[0] * 2**28) + (tc[1] * 2**20) + (tc[2] * 2**12) +
(tc[3] * 2**4) + (tc[4] >> 4);
if (Date.now() / 1000 - dt / 10 > 86400 * 365)
document.cookie = nm + "=;path=" + pa + ";domain=" + dm +
";expires=" + new Date(0).toUTCString();
}
} finally {}
</script>

Yep. Same script.

It is important to know that in the field where the domain should be entered, that the exactly matched domain can be found via the developer console under Application -> Cookies

All credits go to Terry Burton for sharing script with us.
[stackoverflow.com...]

Like others here, the Google CMP consent pop-up has recently stopped displaying on my sites, even though it is actually marked as 'published' in the Adsense console.

I have just enabled the Adsense 'Ad blocking recovery' script, for desktop visitors only.

Since adding this script to my sites (the script calls fundingchoicesmessages.google.com, btw) the Google CMP consent pop-up now displays again (for desktop only, not mobile, as only desktop visitors invoke the script on my sites).

Message: "Consent requirement: Certified CMP not adopted" disappear.
Normal operation mode.

Adserving at rix dropped since 13 Dec from 11% to 3% today and last detected 3.3 error was om 12/12/23.

Weird, those two sites that were flagged for me for a week aren't showing in the policy center anymore as of right now. I didn't change anything TCF-wise.

A few hours later, the policy violation disappeared from my account as well.

The same for me. I had the "Certified CMP not adopted" message on the last 11 days, concerning 2% of the ads. It disappeared today. I have just republished the Google CMP just in case few days ago.

I got this policy violation the other day two. I only use AdSense so I only use their CMP and have had message published for MANY months now. This is getting frustrating because I'm doing everything right and get warnings every day in my login area that I'm not compliant. Just fix your bugs already, Google.

I'm currently suffering of this issue since some days.
No violation, CMP Validator extension confirms API is not loaded.
Suddenly stopped working...

Did anyone solved and how ?

Have you tried re-publishing the Google CMP? That seems to have fixed it for some.

Yes I did republished it, I've even created a brand new message. Nothing happens.

The implementation of this has been sketchy from Googlees side of things. I had several sites that I needed to use a CMP for. I used the default option of using Google's own CMP. Carried out the required steps, saved and published. Still, I occasionally get the nag notification in my Control panel that I need to use a CMP (even though they are live and functioning).

Mack.