Adsense and CFAA's CMP
Last Friday's post, Adsense and the CMP (September 2023), established a plan:-
Google's permanent page on the subject [...] sets a deadline: 'Beginning January 16, 2024, publishers and developers using Google AdSense, Ad Manager, or AdMob will be required to use a Consent Management Platform (CMP) [...]'. The page contains a list of 'Google-certified CMPs' that currently has 50 names with a link for each name. Only one of the 50 names was even vaguely familiar to me, 'Google consent management solutions', so no prize for guessing which one I chose to investigate further. [...] That leads to the next stage of the adventure, which I'll cover in the next Friday post.
That 'next Friday post' is today's post. When I signed into Adsense to continue the adventure, I received a new notification on CMPs, shown below.
Since I had already started to create a GDPR consent message for the previous post, I chose the second option and CONFIRMed. Now I was nagged a second time with the message:-
Notifications: Remember to publish your GDPR message using a Google-certified CMP to continue showing AdSense ads on your site in the EEA and the UK. If you don't publish it by January 16, 2024, we'll publish one for you.
This was the first time I knew that Google would 'publish one' for me. If I had known that earlier, I probably would have gone that route. Instead, I accessed my stored message and published it. I received an error message:-
Your message is almost ready to publish. You need to add a logo to publish your message.
My domain has two main sites (linked near the top of the right sidebar), both with a different logo. The CFAA portion of the site generates the most Adsense revenue, so I used the following logo. It's based on the logo for the CFAA pages, but respecting Google's CMP requirements.
After adding the logo, my GDPR message was accepted. As I was preparing this post for publishing, the message still wasn't showing on my pages, so maybe I did something wrong. I'll come back to it for next Friday's post.
No comments:
Post a Comment