- Edited
Tucker_P_Ezoic I understood. In the panel where do I create the reserved space?
Currently ads are automatic.
Tucker_P_Ezoic I understood. In the panel where do I create the reserved space?
Currently ads are automatic.
linhagemgeek You can add additional ad positions with our Chrome Extension, here's a guide on how to do that: https://support.ezoic.com/kb/article/using-the-ezoic-chrome-extension
Bear in mind though that you aren't guaranteed to see an ad in the 'reserved space' on every visit. Our AI will determine where to place ads based on your user's preferences, which'll ensure better revenue performance on the site.
Ethan Thanks for the answer! I tried to remove 1 ads, but it didn't work. It is a video, how do I remove it?
linhagemgeek That is our universal player, you can make changes to the UP here: https://pubdash.ezoic.com/ezoicads/adtypes
Please note that turning the universal player off entirely will negatively impact your revenue.
Imogen And how do I remove him from that ad position? This is a Humix video
linhagemgeek If you would like more control over the universal player and where it appears, the suggestion would be to edit it here - https://pubdash.ezoic.com/humix/site/monetization
Under advanced settings you are able to adjust what viewport that the player will appear in to something other than 2nd viewport.
Jan Thanks! I am going to try.
Hello, my ads have stopped running, can you help me?
This message appears on my dashboard:
It looks like your site got disconnected, and as a result, Ezoic ads have stopped serving and your revenue has declined. If that was not intended, please click here to chat privately with a member of our team
Where are you seeing this messaging exactly?
We're not seeing any issues with ad service to the site and no warning messages in the dashboard either.
I saw this message on the panel and the site was also not opening the ads, only blank spaces were showing.
You can click the 'x' at the right hand side and that warning will no longer show.
As noted earlier, there was no indication of an interruption in the metrics necessarily, so it may have been sent in error or extremely brief.