The following list contains the most common reasons that I found when analyzing your pages. Please check this list before contacting me for support.

If you are not experienced with any of these methods then you can always ask me for a custom quote to help you out.

Please keep in mind that if there is a bug that is not caused by something mentioned here then I am eager to learn about it. Bugs within Advanced Ads will be solved as soon as possible.

Quick actions:

  • Disable any ad blockers (also check your anti virus software for such an option)
  • Update to the latest version of Advanced Ads, its add-ons and WordPress.
  • Enable the ad debug mode.
  • Test if dummy ads are showing
  • Test in another / real browser, not through web services that just simulate browsers, devices or geo locations
  • Check if the ad code is at least showing in the source code of your page.
  • Refresh Cache or try with cache disabled.
  • Refresh the ad block disguise folder in the general settings (especially after plugin update).
  • Set up AdSense Publisher ID (if using AdSense ads)

Please also check the most common issues.

Disable ad blockers

Please disable ad blockers when working on your ads. Even with the ad block disguise enabled, it might block some resources.

Also check if your anti virus software has such an option. We know that Kaspersky Antivirus has an option called “Anti-banner”.

Refresh Cache

If you use caching then please refresh it or even disable it for admins to see if it works without caching.

Not every dynamic feature of ad plugins work well with enabled caching, but we are working on a solution for that.

Ads included in the frontend?

Just creating an ad doesn’t display it in the frontend. To make an ad visible for visitors you must somehow include it using any of the methods mentioned in the Displaying Ads section of the manual.

The same applies to layers and sticky ads.

Bugfix AdSense

New AdSense ad units tend to need a bit time before showing up. Depending on traffic you might give them a few hours.

With responsive ad units it is more complicated. The automatic sizing ad units aren’t always able to determine the available space. This is an AdSense problem you can address with different solutions. One is to set ad sizes manually as described here.

Also check if the AdSense Publisher ID is set up correctly in Advanced Ads > Settings > AdSense.

Ad visible in the source code?

Check if the ad code you injected with Advanced Ads is visible in the source code of your page. Just open the source code window of your browser as described here and use the search function to search for some of the strings you entered in the ad code.

If the ad code does show up there and is completely identical to the one you entered, then please move on with the other checks here on this page.

If the ad code doesn’t show up, please check your ad settings, that you included the ad and that display and visitor conditions are set up correct.

Also take a look at Disable code optimization features below. Some of them might alter the code before the output.

If your ad code is added, but the ad stays empty, try to use our dummy ads. If they show up then your ad code is broken. Please contact the ad provider regarding your problem or see below for possible issues with your setup.

On rare occasions, the wp_footer() function is missing in some themes. This is an important part of the WordPress API, so please check if it is working, mostly in the footer.php file of your theme.

Ad injection not working?

The ad injection placements (e.g. if you want to display an ad after the first paragraph of each post) injects ads only on the main content of single pages in order to not display ads on places like recommended posts or even for invisible meta descriptions.

However, some themes are using another than the common ways in order to load post content and the injection protected prevents ads from showing up then. To allow ad injection of any kind of post output, you can enable this option:

Advanced Ads > Settings > General > Unlimited ad injection.

If you set this option to -1 or higher than 0, you will see ads in posts on archive pages (unless you disable this on the display conditions screen). It might also cause conflicts of different kind, depending on the theme and plugins you are running.

the_content filter missing

Another possible reason for injected ads not showing up could be a missing the_content  filter. This filter is used by WordPress and many plugins to alter the post content before output. As it happens, some themes seem to forget about this. The most common mistake here is that themes uses get_the_content()  and not the_content()  in order to to output the content. If you are not sure about this, please ask your theme developer.

Be aware that 404 pages often don’t have a content filter at all.

broken HTML

The content injection can also break because of a malformated ad code or when the paragraphs can not be counted due to a broken tag. Such issues will be captured in the error log or displayed below the ad, when you have WP_DEBUG enabled in your wp-config.php.

Disable code optimization features

Some plugins, but also server settings or custom code, can optimize the output of the frontend code. The most common source of conflict here is if they move inline css code or scripts to another place. Since most ad codes can’t be “optimized” this way the features conflict by design.

With some plugins there are hooks one can use to exclude the ad from being “optimized”.

I still gather information about these issues, so let me know if you stumble upon one of them. Plugins or services that we already found moving (any) ad code from pages are: