Adsense Mediation

web4business

I tried setting up Google Adsense so I could set up AdSense Mediation and added the required code into the <head> section of my website, but when I do I see the following message:

PHP is NOT allowed in your code (disabled by your theme or a plugin)

Then I installed SiteKit to connect everything, but unfortunately I get the following message.

Looks like Site Kit is unable to place or detect tags on your site. This can be caused by using certain caching or maintenance mode plugins or your site’s frontend is configured on a different host or infrastructure than your administration dashboard.

I have disabled my caching plugin and that hasn't made any difference. So I am not sure where else to look or what could be the problem.

And I am wondering if it could have anything to do with the caching through ezoic.

Thank you for your help

Monica

web4business You don't need this code to use Adsense mediation with Ezoic, is Adsense asking for this before they can review your site?

web4business

Monica Yes it is asking me for the code in order to review the website. Looking at Mediation, it says: We are still pending verification of your AdSense account in our Certified Partner Program. So I am not sure what to do. Although looking at "Manage your sites", under Ads.txt it says it is authorised. I am soooo confused.

cjsmith

web4business no problem, sounds like you're on the right lines!

Ads.txt is different from AdSense so it makes sense that ads.txt would be authorised but not your AdSense.

Regarding AdSense, we just need to help you add those tags so AdSense can approve your site. I don't believe Ezoic's caching would impact Site Kit's ability to detect the tags on your site but you're welcome to clear Ezoic's cache or temporarily disable it altogether (both of which can be done under 'Leap' > 'Caching') to see whether that makes any difference.

More likely it's to do with the 'PHP is NOT allowed in your code (disabled by your theme or a plugin)' messaging you've received - are you aware of your theme or a plugin disallowing this? It might be worth contacting your theme's developers for assistance.