This page contains short notes for features included in Advanced Ads Pro that don’t have their own documentation page.
Single request mode and Display once per page option
The single request mode is an automatic feature in Advanced Ads Pro. It optimizes the number of ad requests to the backend by grouping ajax calls. Ads without cache-busting are loaded first followed by passive ads and finally ajax ads. So, when you have an ad that can theoretically show up in multiple positions but is limited to show up only once per page, it would first show in the none-cache-busted placements.
How to display an ad only once per page
When using multiple ad groups, ad rotation or placement tests, a chance is that you are using the same ad in different positions, but prefer to show it only in one of them.
In Advanced Ads Pro you can activate the Display only once option in the Layout/Output meta box of the ad edit screen to prevent the ad to show up again, once it was already delivered to the frontend.
Using a custom content injection filter
Ads are typically injected into the post content using the the_content filter. Some themes are missing this hook or also display post-like content where ad injection might make sense.
If this content is running through a filter hook, you can apply all content injection placements to this hook, too.
Just define the ADVANCED_ADS_PRO_CUSTOM_CONTENT_FILTER constant in the wp-config.php file like below.
define( 'ADVANCED_ADS_PRO_CUSTOM_CONTENT_FILTER', 'widget_title' );
Displaying an ad from another blog in a network
Loading and displaying an ad from another blog in a multisite network is possible with an additional attribute in a shortcode.
You can add the blog_id attribute to any shortcode that displays a single ad, group or placement to load that resource from another blog.
The following shortcode would load the ad with the ID 12 from the blog with the ID 1.
[the_ad id="12" blog_id="1"]
Keep in mind, that Advanced Ads Pro needs to be activated on the blog where you use the shortcode, and the basic version of Advanced Ads needs to be activated on both blogs.
If you want to use Analytics tracking then the Tracking add-on needs to be enabled on both sites with the correct tracking method and Analytics ID selected.
Display and Visitor Conditions will either be ignored or broken. If you want to use these conditions, you should create a new ad on the displaying blog using the “rich media” ad type and put the shortcode from the other ad into the content field. You can assign conditions to that intermediate ad.
Ajax cache-busting is not working, but if you use the shortcode of a placement and have Advanced Ads Pro activated on both sites, passive cache-busting should work.