A couple of users reported that their AdSense auto ads stopped working on their AMP pages since 11/12/2019.
The issue was reproduced here. The response from AdSense auto ads server print this error:
[amp-auto-ads] No ad placements found for publisher ID 'ca-pub-*'. Check that the provided publisher ID is correct.
The issue has been reported to Google AdSense team and got confirmed by them. They're working on a fix.
Will post here for any updates we got from them.
I'm having this issue here too at https://www.saibatudomt.com.br/
log.js:244 [amp-auto-ads] No ad placements found for publisher ID 'ca-pub-8168441694441175'. Check that the provided publisher ID is correct.
I'm having this issue here too at https://tobruxo.com.br/
Same here, any info?
Although the root cause is at AdSense server side, we cherrypicked a client side work around to mitigate the issue last Friday. I was told that with this change, sites with higher traffic will likely get recovered sooner. A full fix at server side will come in January.
I am having the same problem. Any idea when a fix will be provided?
@levyblue could you also provide a link to reproduce the issue?
Sure, the issue is happening on my personal finance blog
I'm having the same issue, my website is https://www.yourzodiacsign.com.
amp-auto-ads worked on this website before, but now it can't work.
I'm having the same issue too.
https://megane-blog.com/
Hello team, does anyone have an update on this issue?
Hello team, does anyone have an update on this issue?
Having similar issues on my website - https://www.flixwatch.co/
Some of the sample pages are-
https://www.flixwatch.co/movies/hush/
https://www.flixwatch.co/country/usa/
https://www.flixwatch.co/lists/100-best-movies-on-netflix/
Following this. having the same issue.
[amp-auto-ads] No ad placements found for publisher ID 'ca-pub-
Although the root cause is at AdSense server side, we cherrypicked a client side work around to mitigate the issue last Friday. I was told that with this change, sites with higher traffic will likely get recovered sooner. A full fix at server side will come in January.
January is almost over. any progress on this? please advise
Try this?
Have you tried it? It's from 2018 and no recent comments on the post.
Hi @lannka, please let us know if there is any new information on this issue :)
@eduardogoncalves just pinged AdSense team again. I will update here once heard back from them.
I still see this issue even with configuration. https://www.w3docs.com/ad-network-config.js
I want to show ads as a sibling of main div.code-snippet
for example on page https://www.w3docs.com/learn-git/git-clone.html.
Also, it is not clear should we use
{
"placements": [
{
"anchor": {
"selector": "MAIN",
"sub": {
"selector": "DIV.code-snippet",
}
},
"pos": 4,
"type": 1,
"style": {
"top_m": 5,
"bot_m": 10
}
}
]
}
or
export default {
"placements": [
{
"anchor": {
"selector": "MAIN",
"sub": {
"selector": "DIV.code-snippet",
}
},
"pos": 4,
"type": 1,
"style": {
"top_m": 5,
"bot_m": 10
}
}
]
}
We need attention with this issue, maybe this isn't important do AdSense team, but for AMP we can lose publishers using AMP Canonical/AMP First, because who uses AMP Canonical/AMP First are losing tons of AdSense money and soon will stop using and investing in AMP.
/ping @lannka @tlong2
same issue here.
Opened a ticket with Google Adsense yesterday, waiting their reply.
/ping @lannka @rsimha
Unfortunately, I don't work on ads, and don't have any context for the cause of this issue. Will leave it to someone from @ampproject/wg-ads to post an update.
@rsimha 馃槼 Sorry, my mistake. I Saw a picture of you in some commit related to amp-auto-ads, but now I saw that was unrelated.
@eduardogoncalves sorry for the delay on this; it's taking longer to fix than we hoped. It is important to us and we're working on it.
There's some complexity in ensuring that our backend system pickups the correct URLs to analyze for the case of canonical AMP. For various reasons that has not been as simple to solve as we had hoped.
Thanks for your patience, and sorry again for the time this is taking.
/ping @ampproject/wg-ads
@eduardogoncalves
Google ads team (@tlong2 ) would provide updates on the server-side fix. Thanks!
Hello, I have the same problem on this site: https://buenavibra.es/
Anyone has a solution for this ?
[amp-auto-ads] No ad placements found for publisher ID 'ca-pub-2XXXXXXXX. Check that the provided publisher ID is correct.
Thanks my blog was fixed.
Auto Ad is displayed.
I didn't change my code.
Probably I think someone fixed this issue from google.
https://megane-blog.com/
The issue should have been fixed at AdSense side. Close now.
same issue on my website http://nielitexams.com/
Experiencing this issue in July 2020 on this new site: infoAnew.com.
[amp-auto-ads] No ad placements found for publisher ID 'ca-pub-9705598290828550'. Check that the provided publisher ID is correct.
I noticed that the ca-
prefix is not displayed when I look at the publisher ID in Google Analytics. So I'll try dropping the prefix and see if that helps.
Experiencing this issue in July 2020 on this new site: infoAnew.com.
[amp-auto-ads] No ad placements found for publisher ID 'ca-pub-9705598290828550'. Check that the provided publisher ID is correct.
I noticed that theca-
prefix is not displayed when I look at the publisher ID in Google Analytics. So I'll try dropping the prefix and see if that helps.
Dropping the ca-
prefix did not help. AdSense instructs you to use it. Under the error above I see additional info:
[amp-auto-ads] No placements in config
and, [amp-auto-ads] unable to fulfill ad strategy
. I'm guessing the config has to be present and will try create it.
We have exactly the same issue here: https://www.bizzlibrary.com/Template/NH281/acceptable-encryption-policy/
@rolero How did you fix this issue? can see ads on you linked webpage.
Most helpful comment
The issue should have been fixed at AdSense side. Close now.