Auto adsense not workingAuthor: Craig K.
Visited 207, Followers 1, Shared 0
Are there any specific settings to allow the automated version of adsense to work on Wx5 pro? Even though approved, and everything else seems fine from Adsense account side, still will not show. Even manually placed ad unit.
Posted on the
To work, the AdSense service first needs the domain to be verified and then to scan the contents. These aspects take time, for example several days. If you have correctly configured the domain and entered the code in Step 1 > Code it should work by itself.
Basically this is not a WebSite X5 problem. For example, if you visit this site WSX5 https://www.gebher.com/ (accepting cookies) banners should appear while browsing. Obviously a lot depends on the AdSense channel and other factors of your device and browsing data.
Hi Craig, are you talking about the AddSense object or the internal AddSense function in the blog settings?
I am asking, because the object isn't working anymore, at least on my templates, why the AdSense switch in the blog pages worked fine. Instead of the object, I use now an HTML object and paste the script from the AddSense account directly into it. With this approach you get more configuration and style options too.
I inserted Google's code as they requested in the header, by going to settings > statistics and code
Not sure what objects you are referring to.
Hi Craig, sorry I missed the AddSense in regards to AdThis. Those who can read have a clear advantage
Regarding AddSense, make sure that the marketing cookies are enabled per browser session, otherwise nothing will pop up. In case you use something like Cookiebot.
Thanks will try that.
I do not see banners on your website? Which page has banners?
I tested manually placing ad code on a page using code object. However get the following error, visible in browser (inspect -> console):
A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.
To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.
Note that for performance reasons, only the first access to one of the properties is shown.