AdSense ad size settings for mobile don’t work as intended

Hi (salutări),

We’ve inserted an Adsense Ad on our website Overheat.ro, just below the header. The ad’s code is in the “Custom ad 1” slot in the theme.

In the “Advance usage” section of the slot, we’ve set an AdSense size of 320 x 50 for phones, but somehow this rule doesn’t get applied if the width of the screen is any less than 458 pixels (I checked with Chrome’s dev tools). It only works between 458 and 767px. Any less than 458 and it goes into auto mode and even stretches to full width.

Can you help me fix this?

Thanks,
Roberto

• This topic was modified 1 year by robertot.

Hi Anamaria,

Thank you for your answer. Not sure why you weren’t able to see the ad that is just below the header, it sometimes shows as a blank spot for me too. Anyway, the ad is not in the header per se – it’s just the first block of the homepage’s Content area.

You can see it in the screenshots below, along with the settings we use:
Our theme panel ad settings: https://imgur.com/a/h90vxYu
The ad in question, on screens < 458px wide: https://imgur.com/3yYFp78
The ad on screens 458px – 767px wide: https://imgur.com/jC8kRRC

Your solution of inserting the code again in the Mobile header *might* work, but as this ad placement is already showing in the correct spot for all devices, it would make more sense to use the AdSense code just once (like it is now) and work with the Theme Panel options to adjust the sizing to different devices. Duplicating the ad code in the mobile menu would prolong page load time for all devices and it would show this ad on the entire website instead of just on the homepage, which I don’t want.

The built-in Theme Panel options for different devices should be exactly what I need and they should work. They already seem to work fine for screens 458px-767px wide. The quirky behavior that happens below 458px width is what breaks this feature for our site.

So I would just like to fix the erratic behavior at <458px, because that’s the real problem and I’d really like to understand it and fix it while keeping a clean code&structure.

Thanks a lot, Tagdiv team! Here’s hoping we can find out what’s happening here :).